Skip to content
#

stream-processing

Here are 708 public repositories matching this topic...

pkaske
pkaske commented Dec 29, 2020

I figured out a way to get the (x,y,z) data points for each frame from one hand previously. but im not sure how to do that for the new holistic model that they released. I am trying to get the all landmark data points for both hands as well as parts of the chest and face. does anyone know how to extract the holistic landmark data/print it to a text file? or at least give me some directions as to h

flink-learning

flink learning blog. http://www.54tianzhisheng.cn/ 含 Flink 入门、概念、原理、实战、性能调优、源码解析等内容。涉及 Flink Connector、Metrics、Library、DataStream API、Table API & SQL 等内容的学习案例,还有 Flink 落地应用的大型项目案例(PVUV、日志存储、百亿数据实时去重、监控告警)分享。欢迎大家支持我的专栏《大数据实时计算引擎 Flink 实战与性能优化》

  • Updated Jun 24, 2021
  • Java
agavra
agavra commented Jul 15, 2021

Describe the bug

Table scans should support the full suite of operations in the WHERE clause, however LIKE is not supported:

To Reproduce

Issue any query with WHERE key LIKE '%foo%';

Expected behavior

Query works

Actual behaviour

ksql> set 'ksql.query.pull.table.scan.enabled'='true';
Successfully changed local property 'ksql.query.pull.table.scan.en
watermill
breml
breml commented Mar 10, 2021

For an implementation of #126 (PostgreSQL driver with SKIP LOCKED), I create a SQL table for each consumer group containing the offsets ready to be consumed. The name for these tables is build by concatenating some prefix, the name of the topic and the name of the consumer group. In some of the test cases in the test suite, UUID are used for both, the topic and the consumer group. Each UUID has

nisanharamati
nisanharamati commented Jul 24, 2018

It can be very difficult to piece together a reasonably estimate of a history of events from the current workers logs because none of them have timestamps.

So for that end, I think we should add timestamps to the logs.

This has some cons:

  1. We can't just use @printf like we have been until now. We need to either include a timestamp in every @printf call (laborious and error prone) or c
hazelcast-jet

Improve this page

Add a description, image, and links to the stream-processing topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the stream-processing topic, visit your repo's landing page and select "manage topics."

Learn more