Yang Wang created FLINK-17648:
-
Summary: YarnApplicationClusterEntryPoint should override
getRPCPortRange
Key: FLINK-17648
URL: https://issues.apache.org/jira/browse/FLINK-17648
Project: Flink
Hi Dhurandar:
Currently StreamingFileSink should be able to change the prefix and suffix
of the filename[1], it could be changed to something like -0-0.
Could this solve your problem ?
Best,
Yun
[1]
Jark Wu created FLINK-17647:
---
Summary: Improve new connector options exception in old planner
Key: FLINK-17647
URL: https://issues.apache.org/jira/browse/FLINK-17647
Project: Flink
Issue Type:
Wei Zhong created FLINK-17646:
-
Summary: Reduce the python package size of PyFlink
Key: FLINK-17646
URL: https://issues.apache.org/jira/browse/FLINK-17646
Project: Flink
Issue Type: Improvement
Zakelly Lan created FLINK-17645:
---
Summary: REAPER_THREAD in SafetyNetCloseableRegistry start()
failed, causing the repeated failover.
Key: FLINK-17645
URL: https://issues.apache.org/jira/browse/FLINK-17645
We want to change the name of the file being generated as the output of our
StreamFileSink.
, when files are generated they are named part-00*, is there a way that we
can change the name.
In Hadoop, we can change RecordWriters and MultipleOutputs. May I please
some help in this regard. This is
Igal Shilman created FLINK-17644:
Summary: Add support for state TTL.
Key: FLINK-17644
URL: https://issues.apache.org/jira/browse/FLINK-17644
Project: Flink
Issue Type: Improvement
Arvid Heise created FLINK-17643:
---
Summary: LaunchCoordinatorTest fails
Key: FLINK-17643
URL: https://issues.apache.org/jira/browse/FLINK-17643
Project: Flink
Issue Type: Bug
Nikola created FLINK-17642:
--
Summary: Exception while reading broken ORC file is hidden
Key: FLINK-17642
URL: https://issues.apache.org/jira/browse/FLINK-17642
Project: Flink
Issue Type: Bug
Ethan Li created FLINK-17641:
Summary: How to secure flink applications on yarn on multi-tenant
environment
Key: FLINK-17641
URL: https://issues.apache.org/jira/browse/FLINK-17641
Project: Flink
We also noticed that and had to make an adjustment downstream.
It would be good to mention this in the release notes (if that's not
already the case).
Thomas
On Tue, May 12, 2020 at 10:06 AM Seth Wiesman wrote:
> Hi Everyone,
>
> I realize I'm about 7 hours late but I just realized there is
Hi Everyone,
I realize I'm about 7 hours late but I just realized there is a breaking
API change in 1.10.1. FLINK-16684 changes the API of the streaming file
sink in a binary incompatible way. Since the release has been approved I'm
not sure the correct course of action but I wanted to bring this
Arvid Heise created FLINK-17640:
---
Summary:
RecoveredInputChannelTest.testConcurrentReadStateAndProcessAndRelease() failed
Key: FLINK-17640
URL: https://issues.apache.org/jira/browse/FLINK-17640
+1 from me
Best,
Dawid
On 12/05/2020 15:49, Stephan Ewen wrote:
> +1 from me
>
> There are discussions about minor changes (names and serializability)
> pending, but these should not conflict with the design here.
>
> On Tue, May 12, 2020 at 10:01 AM Aljoscha Krettek
> wrote:
>
>> Hi all,
>>
Thank you for the update and sorry again for chiming in so late...
Best,
Dawid
On 12/05/2020 18:21, Aljoscha Krettek wrote:
> Yes, I am also ok with a SerializableTimestampAssigner. This only
> looks a bit clumsy in the API but as a user (that uses lambdas) you
> should not see this. I pushed
Yes, I am also ok with a SerializableTimestampAssigner. This only looks
a bit clumsy in the API but as a user (that uses lambdas) you should not
see this. I pushed changes for this to my branch:
https://github.com/aljoscha/flink/tree/flink-xxx-wm-generators-rebased
And yes, recordTimestamp
Kostas Kloudas created FLINK-17639:
--
Summary: Document which FileSystems are supported by the
StreamingFileSink
Key: FLINK-17639
URL: https://issues.apache.org/jira/browse/FLINK-17639
Project: Flink
I have similar thoughts to @Stephan
Ad. 1 I tried something like this on your branch:
/**
* Adds the given {@link TimestampAssigner} to this {@link
WatermarkStrategies}. For top-level classes that implement both
Serializable and TimestampAssigner
*/
public & Serializable>
@Aljoscha
About (1) could we have an interface SerializableTimestampAssigner that
simply mixes in the java.io.Serializable interface? Or will this be too
clumsy?
About (3) RecordTimeStamp seems to fit both cases (in-source-record
timestamp, in stream-record timestamp).
On Tue, May 12, 2020 at
chenchuangchuang created FLINK-17638:
Summary: FlinkKafkaConsumerBase restore from empty state will be
set consum from earliest forced
Key: FLINK-17638
URL: https://issues.apache.org/jira/browse/FLINK-17638
Definitely +1 to point 2) raised by Dawid. I'm not sure on points 1) and 3).
1) I can see the benefit of that but in reality most timestamp assigners
will probably need to be Serializable. If you look at my (updated) POC
branch [1] you can see how a TimestampAssigner would be specified on the
+1 from me
There are discussions about minor changes (names and serializability)
pending, but these should not conflict with the design here.
On Tue, May 12, 2020 at 10:01 AM Aljoscha Krettek
wrote:
> Hi all,
>
> I would like to start the vote for FLIP-126 [1], which is discussed and
> reached
+1 to all of Dawid's suggestions, makes a lot of sense to me
On Tue, May 12, 2020 at 2:32 PM Dawid Wysakowicz
wrote:
> Hi Aljoscha,
>
> Sorry for adding comments during the vote, but I have some really minor
> suggestions that should not influence the voting thread imo.
>
> 1) Does it make
Robert Metzger created FLINK-17637:
--
Summary: HadoopS3RecoverableWriterITCase fails with Expected
exception: java.io.FileNotFoundException
Key: FLINK-17637
URL: https://issues.apache.org/jira/browse/FLINK-17637
Robert Metzger created FLINK-17636:
--
Summary:
SingleInputGateTest.testConcurrentReadStateAndProcessAndClose: Trying to read
from released RecoveredInputChannel
Key: FLINK-17636
URL:
Kurt Young created FLINK-17635:
--
Summary: Add documentation about view support
Key: FLINK-17635
URL: https://issues.apache.org/jira/browse/FLINK-17635
Project: Flink
Issue Type: Sub-task
Hi Aljoscha,
Sorry for adding comments during the vote, but I have some really minor
suggestions that should not influence the voting thread imo.
1) Does it make sense to have the TimestampAssigner extend from Flink's
Function? This implies it has to be serializable which with the factory
Chesnay Schepler created FLINK-17634:
Summary: Reject multiple handler registrations under the same URL
Key: FLINK-17634
URL: https://issues.apache.org/jira/browse/FLINK-17634
Project: Flink
Jark Wu created FLINK-17633:
---
Summary: Improve FactoryUtil to align with new format options keys
Key: FLINK-17633
URL: https://issues.apache.org/jira/browse/FLINK-17633
Project: Flink
Issue Type:
Yang Wang created FLINK-17632:
-
Summary: Support to specify a remote path for job jar
Key: FLINK-17632
URL: https://issues.apache.org/jira/browse/FLINK-17632
Project: Flink
Issue Type: Sub-task
Hi everyone,
I'm happy to announce that we have unanimously approved this release.
There are 11 approving votes, 6 of which are binding:
* Robert Metzger (binding)
* Thomas Weise (binding)
* Tzu-Li (Gordon) Tai (binding)
* Ufuk Celebi (binding)
* Hequn Cheng (binding)
* Jincheng Sun (binding)
*
For that attached YARN per-job mode, the cluster should wait until the
result of the job has been fetched. Can't this be used to report the final
status of the job?
Cheers,
Till
On Tue, May 12, 2020 at 9:52 AM Aljoscha Krettek
wrote:
> Hi,
>
> The problem is that the JobClient is talking to
I think this is a very good idea. With a team committed to keep the site up
to date the main concern should also be resolved.
Cheers,
Till
On Mon, May 11, 2020 at 5:25 PM Yuan Mei wrote:
> Yep, Marta's concern is definitely a great point in terms of maintenance
> costs.
>
> What I would like
This is great newst :-) Thanks Marta for driving this effort!
On Mon, May 11, 2020 at 4:22 PM Sivaprasanna
wrote:
> Awesome. Great job.
>
> On Mon, 11 May 2020 at 7:22 PM, Seth Wiesman wrote:
>
> > Thank you for putting this together Marta!
> >
> > On Mon, May 11, 2020 at 8:35 AM Fabian Hueske
A bit late but also +1 for the proposal to return an empty
iterator/collection.
Cheers,
Till
On Mon, May 11, 2020 at 11:17 AM SteNicholas wrote:
> Hi Tang Yun,
> I have already created new issue for FLINK-17610 to align the behavior
> of result of internal map state to return empty
Thanks all for checking and voting for the release!
With 11 +1 (6 binding) and no -1 votes, this vote has passed. Will
officially conclude the vote in another thread.
Best Regards,
Yu
On Tue, 12 May 2020 at 17:02, Wei Zhong wrote:
> +1 (non-binding)
>
> - checked signatures
> - the python
+1 (non-binding)
- checked signatures
- the python package looks good
- the python shell looks good
- submitted a python job on local cluster
Best,
Wei
> 在 2020年5月12日，11:42，Zhu Zhu 写道：
>
> +1 (non-binding)
>
> - checked release notes
> - checked signatures
> - built from source
> - submitted
Danny Chen created FLINK-17631:
--
Summary: Supports char type for ConfigOption
Key: FLINK-17631
URL: https://issues.apache.org/jira/browse/FLINK-17631
Project: Flink
Issue Type: Improvement
Thanks for your discussion.
Sorry to start discussing another thing:
The biggest problem I see is the variety of problems caused by users' lack
of format dependency.
As Aljoscha said, these three formats are very small and no third party
dependence, and they are widely used by table users.
Hi all,
I would like to start the vote for FLIP-126 [1], which is discussed and reached
a consensus in the discussion thread [2].
The vote will be open until May 15th (72h), unless there is an objection or not
enough votes.
Best,
Aljoscha
[1]
Jark Wu created FLINK-17630:
---
Summary: Implement format factory for Avro serialization and
deserialization schema
Key: FLINK-17630
URL: https://issues.apache.org/jira/browse/FLINK-17630
Project: Flink
Jark Wu created FLINK-17629:
---
Summary: Implement format factory for JSON serialization and
deserialization schema
Key: FLINK-17629
URL: https://issues.apache.org/jira/browse/FLINK-17629
Project: Flink
Hi,
The problem is that the JobClient is talking to the wrong system. In YARN
per-job mode the cluster will only run as long as the job runs so there will be
no-one there to respond with the job status after the job is finished.
I think the solution is that the JobClient should talk to the
Wei Zhong created FLINK-17628:
-
Summary: Remove the unnecessary py4j log information
Key: FLINK-17628
URL: https://issues.apache.org/jira/browse/FLINK-17628
Project: Flink
Issue Type:
Robert Metzger created FLINK-17627:
--
Summary: Add support for writing _SUCCESS file with
StreamingFileSink
Key: FLINK-17627
URL: https://issues.apache.org/jira/browse/FLINK-17627
Project: Flink
Jingsong Lee created FLINK-17626:
Summary: Migrate format properties to new FLIP-122
Key: FLINK-17626
URL: https://issues.apache.org/jira/browse/FLINK-17626
Project: Flink
Issue Type:
46 matches
Mail list logo
