+1 to have a minimal 1.3.3 release with the listed issues. I can also help
manage this release.
It seems like we don't have any objections with Aljoscha's proposal so far.
Will wait a little bit more for any other opinions, and try to open a RC by
the end of the week.
Cheers,
Gordon
Hi,
Anyway, the line of cd build-target below confused me for a while at the first
time since there is not a folder called build-target. So I would suggest change
this stuff to a more reasonable representation for the beginner to flink.
What do you think of that ?
Like
cd
Hi, Stefano:
I agree with Febian that it's not a good idea to expose internal state as
queryable to users for the reasons listed by Fabian.
As you pointed out with current QueryableStateSink's design, duplicating
internal state is inefficient. But this is limited by the api of table sink
since
I want to use the BucketingSink in the hadoop-free Flink system (i.e. 1.4.0)
but currently I am kind of blocked because of its dependency on the Hadoop file
system.
1. Is this something that's going to be fixed in the next version of Flink?
2. In the meantime, to unblock myself, what is the
Ping :)
On Wed, Feb 21, 2018 at 7:16 PM, Shuyi Chen wrote:
> Hi Eron, thanks a lot for taking a look at the proposal, the comments are
> very useful. I've updated the document to address your concerns. Could you
> please help take another look, and suggest what the next step
+1
2018-03-08 10:20 GMT-08:00 Ted Yu :
> +1 to Aljoscha's proposal.
>
Approximately when is the release of Flink 1.5 planned?
Best,
2018-03-01 11:20 GMT+02:00 Till Rohrmann :
> Thanks for bringing this issue up Shashank. I think Aljoscha is taking a
> look at the issue. It looks like a serious bug which we should definitely
> fix. What I've
+1 to Aljoscha's proposal.
+1
On Thu, Mar 8, 2018 at 7:36 AM, Aljoscha Krettek
wrote:
> Hi,
>
> We fixed a critical bug in the ZooKeeper checkpoint store but never
> released a 1.3.x version of Flink with the fix. I'm proposing to release
> 1.3.3 with only fixes for this issue so that users can
I don't think it is a good idea to expose the internal state of a query as
queryable state for the following reasons:
1. plan generation: the streaming programs and operators are created based
on the optimized plan. A user cannot know which operators a query will run
on. Naming the queryable
Gary Yao created FLINK-8902:
---
Summary: Re-scaling job sporadically fails with KeeperException
Key: FLINK-8902
URL: https://issues.apache.org/jira/browse/FLINK-8902
Project: Flink
Issue Type: Bug
Nico Kruber created FLINK-8901:
--
Summary: YARN application name for Flink (per-job) submissions
claims it is using only 1 TaskManager
Key: FLINK-8901
URL: https://issues.apache.org/jira/browse/FLINK-8901
Nico Kruber created FLINK-8900:
--
Summary: YARN FinalStatus always shows as KILLED with Flip-6
Key: FLINK-8900
URL: https://issues.apache.org/jira/browse/FLINK-8900
Project: Flink
Issue Type:
Nico Kruber created FLINK-8899:
--
Summary: Submitting YARN job with FLIP-6 may lead to
ApplicationAttemptNotFoundException
Key: FLINK-8899
URL: https://issues.apache.org/jira/browse/FLINK-8899
Project:
Hequn Cheng created FLINK-8898:
--
Summary: Materialize time indicators in conditions of LogicalFilter
Key: FLINK-8898
URL: https://issues.apache.org/jira/browse/FLINK-8898
Project: Flink
Issue
Xingcan Cui created FLINK-8897:
--
Summary: Rowtime materialization causes "mismatched type"
AssertionError
Key: FLINK-8897
URL: https://issues.apache.org/jira/browse/FLINK-8897
Project: Flink
Hi,
We fixed a critical bug in the ZooKeeper checkpoint store but never released a
1.3.x version of Flink with the fix. I'm proposing to release 1.3.3 with only
fixes for this issue so that users can benefit from the fix and we have the
least amount of overhead in release verification as
Hi Timo, Renjie,
Well, the idea is that stream processing could become a complex pipeline of
multiple queries and sinking data on a separate sink for monitoring does not
seem efficient. In fact, pulling state value on demand would allow to monitor
the values of different parts of the stream
Nico Kruber created FLINK-8896:
--
Summary: Kafka08Fetcher trying to look up topic "n/a" on partiton
"-1"
Key: FLINK-8896
URL: https://issues.apache.org/jira/browse/FLINK-8896
Project: Flink
@Thomas: The test failure on MacOS seems to be related to an update to high
sierra that introduced AFS for system partitions. For some reason AFS seems
is not strictly POSIX compliant when it comes to error codes (possible a
bug/mixup in the error codes). A "file not found" situation returns a
I can get the value with /joboverview under the 1.3.2. Thanks ~
At 2018-03-08 16:29:34, "Gary Yao" wrote:
>Hi Minglei,
>
>What Flink version are you using? The path was only recently changed to
>/jobs/overview [1], and you linked to the documentation of the
Hello, Gary.
Sorry, I forget tell you the flink version i used. The version i have been
using is 1.3.2. I didnt watch the url that under 1.3.2.
By the way, I will take a look on the new bug.
Best
Minglei
At 2018-03-08 16:29:34, "Gary Yao" wrote:
>Hi
Hi Minglei,
What Flink version are you using? The path was only recently changed to
/jobs/overview [1], and you linked to the documentation of the snapshot
version.
While I tested the feature, I discovered another bug in 1.5, though [2].
Best,
Gary
[1]
godfrey johnson created FLINK-8895:
--
Summary: Job failed when one kafka broker shutdown
Key: FLINK-8895
URL: https://issues.apache.org/jira/browse/FLINK-8895
Project: Flink
Issue Type: Bug
Gary Yao created FLINK-8894:
---
Summary: CurrentJobIdsHandler fails to serialize response
Key: FLINK-8894
URL: https://issues.apache.org/jira/browse/FLINK-8894
Project: Flink
Issue Type: Bug
25 matches
Mail list logo