Hi,
thanks for your comments and questions!
Actually, you are bringing up the points that Timo and I discussed the most
when designing the FLIP ;-)
- We also thought about the syntactic shortcut for running aggregates like
you proposed (table.groupBy(‘a).select(…)). Our motivation to not allow
th
Scala and Java mixed in the module. Some Flink API indeed make someone confused.
What is rule about the current Scala and Java API at the first implement time?
Thanks
Renkai Ge created FLINK-4587:
Summary: Yet another java.lang.NoSuchFieldError: INSTANCE
Key: FLINK-4587
URL: https://issues.apache.org/jira/browse/FLINK-4587
Project: Flink
Issue Type: Bug
Hi all,
I'm on vacation for about five days , sorry to have missed this great FLIP.
Yes, the non-windowed aggregates is a special case of row-window. And the
proposal looks really good. Can we have a simplified form for the special
case? Such as :
table.groupBy(‘a).rowWindow(SlideRows.unbound
Johannes created FLINK-4586:
---
Summary: NumberSequenceIterator and Accumulator threading issue
Key: FLINK-4586
URL: https://issues.apache.org/jira/browse/FLINK-4586
Project: Flink
Issue Type: Bug
Alexander Pivovarov created FLINK-4585:
--
Summary: Fix broken links on flink.apache.org
Key: FLINK-4585
URL: https://issues.apache.org/jira/browse/FLINK-4585
Project: Flink
Issue Type: Bu
Alexander Pivovarov created FLINK-4584:
--
Summary: Fix broken links on flink.apache.org
Key: FLINK-4584
URL: https://issues.apache.org/jira/browse/FLINK-4584
Project: Flink
Issue Type: Bu
Greg Hogan created FLINK-4583:
-
Summary: NullPointerException in CliFrontend
Key: FLINK-4583
URL: https://issues.apache.org/jira/browse/FLINK-4583
Project: Flink
Issue Type: Bug
Compone
Hi all,
I thought about the API of the FLIP again. If we allow the "systemtime"
attribute, we cannot implement a nice method chaining where the user can
define a "allowLateness" only on event time. So even if the user
expressed that "systemtime" is used we have to offer a "allowLateness"
meth
Tzu-Li (Gordon) Tai created FLINK-4582:
--
Summary: Allow FlinkKinesisConsumer to adapt for AWS DynamoDB
Streams
Key: FLINK-4582
URL: https://issues.apache.org/jira/browse/FLINK-4582
Project: Flink
Timo Walther created FLINK-4581:
---
Summary: Table API throws "No suitable driver found for
jdbc:calcite"
Key: FLINK-4581
URL: https://issues.apache.org/jira/browse/FLINK-4581
Project: Flink
Iss
Should be resolved now.
On Tue, Sep 6, 2016 at 11:21 AM, Maximilian Michels wrote:
> The testing code for Yarn is very fragile. Also, I'm puzzled why the
> code to test the VCores setting is in the TaskManagerFailure test.
> Running some more tests to fix the issue.
>
> On Tue, Sep 6, 2016 at 7:2
The testing code for Yarn is very fragile. Also, I'm puzzled why the
code to test the VCores setting is in the TaskManagerFailure test.
Running some more tests to fix the issue.
On Tue, Sep 6, 2016 at 7:28 AM, Vijay Srinivasaraghavan
wrote:
> Hi Max,
> I have pulled and tested with the latest mas
13 matches
Mail list logo