Flink join operator after sorting seems to group fields (Scala)

Hi all, I have implemented a simple Scala object using Flink to play with joins operator. After that, I put the join operator show my results I decided to sort the output by the first field (.sortPartition(0, Order.ASCENDING)). It seems that the output is ordered by group. The output shows two

Re: Does Queryable State only support K/V queries not SQL?

Hi Fabian, Does it make sense to have it on the roadmap? that way external applications can do ad-hoc queries for the most recent stream data and avoid writing to any external database? Thanks! On Mon, Feb 26, 2018 at 12:14 AM, Fabian Hueske wrote: > Hi, > > Queryable

Re: Flink join operator after sorting seems to group fields (Scala)

Hi Felipe, the `sortPartition()` method just LOCALLY sorts each partition of a dataset. To achieve a global sorting, use this method after a `partitionByRange()` (e.g., `result.partitionByRange(0).sortPartition(0, Order.ASCENDING)`). Hope that helps, Xingcan > On 3 Mar 2018, at 9:33 PM,

Re: Does Queryable State only support K/V queries not SQL?

Hi kant, To avoid writing to external databases, some relevant issues are on the roadmap, see FLINK-6968[1]. When this issue is finished, you can store your updating tables in queryable state which is available to query(key point queries). Hope it helps you. Best, Hequn [1]

Re: Does Queryable State only support K/V queries not SQL?

Hi, kant: Full support for sql is not easy tuo support. A simple KV storage is not enough to build a RDBMS. On Sun, Mar 4, 2018 at 1:42 AM kant kodali wrote: > Hi Fabian, > > Does it make sense to have it on the roadmap? that way external > applications can do ad-hoc queries

Re: Watermark not worked as expected in TimeCharacteristic.EvenTime setting.

Hi Hequn Cheng, Finally I got the problem and find the way to define the correct WaterMark by your advice, thank you very much. The problem is that I set the watermark to the waterMark = maxEventTime - lag And the timeWindow is 10Seconds, But I generated the test records too quickly

Re: Watermark not worked as expected in TimeCharacteristic.EvenTime setting.

Hi sundy, It is strange that your configuration does not take effect. Do you set parallelism somewhere else? Maybe, you can refer to the kafka test case[1]. In this test case, line 229 set parallelism to 1 and works fine. Hope it helps you. [1]

Re: Watermark not worked as expected in TimeCharacteristic.EvenTime setting.

Thanks a lot, use env.setParallelism(1) before the source define works (I set it before the env.execute, so it did not take effect). > On 3 Mar 2018, at 16:02, sundy <543950...@qq.com> wrote: > > Hi Hequn Cheng, > > Finally I got the problem and find the way to define the correct WaterMark