[jira] [Created] (FLINK-10079) Automatically resolve and register sink table name from external catalogs

[Jun Zhang (JIRA)]

Jun Zhang created FLINK-10079:
-

 Summary: Automatically resolve and register sink table name from 
external catalogs
 Key: FLINK-10079
 URL: https://issues.apache.org/jira/browse/FLINK-10079
 Project: Flink
  Issue Type: Improvement
  Components: Table API & SQL
Affects Versions: 1.6.0
Reporter: Jun Zhang
Assignee: Jun Zhang
 Fix For: 1.6.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[VOTE] Release 1.6.0, release candidate #3

[Till Rohrmann]

Hi everyone,
Please review and vote on the release candidate #3 for the version 1.6.0,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)


The complete staging area is available for your review, which includes:
* JIRA release notes [1],
* the official Apache source release and binary convenience releases to be
deployed to dist.apache.org [2], which are signed with the key with
fingerprint 1F302569A96CFFD5 [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "release-1.6.0-rc3" [5],

Please use this document for coordinating testing efforts: [6]

The vote will be shortened since we only added minor fixes on top of the RC
2. It will close on Wednesday 6:30pm CET. It is adopted by majority
approval, with at least 3 PMC affirmative votes.

Thanks,
Your friendly Release Manager

[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12342760
[2] https://dist.apache.org/repos/dist/dev/flink/flink-1.6.0/
[3] https://dist.apache.org/repos/dist/release/flink/KEYS
[4] https://repository.apache.org/content/repositories/orgapacheflink-1177
[5] https://github.com/apache/flink/tree/release-1.6.0-rc3
[6]
https://docs.google.com/document/d/18rsgMQdT2OhpwdQOjb7WTuJlWdCi58N-lzdhELLBBsE/edit?usp=sharing

Pro-tip: you can create a settings.xml file with these contents:



  flink-1.6.0


  
flink-1.6.0

  
flink-1.6.0


https://repository.apache.org/content/repositories/orgapacheflink-1177/

  
  
archetype


https://repository.apache.org/content/repositories/orgapacheflink-1177/

  

  



And reference that in you maven commands via --settings
path/to/settings.xml. This is useful for creating a quickstart based on the
staged release and for building against the staged jars.

[jira] [Created] (FLINK-10080) Add support for processing time to interval join

[Florian Schmidt (JIRA)]

Florian Schmidt created FLINK-10080:
---

 Summary: Add support for processing time to interval join
 Key: FLINK-10080
 URL: https://issues.apache.org/jira/browse/FLINK-10080
 Project: Flink
  Issue Type: Sub-task
  Components: DataStream API
Reporter: Florian Schmidt






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FLINK-10081) Asynchronous (un)registration of metrics

[Chesnay Schepler (JIRA)]

Chesnay Schepler created FLINK-10081:


 Summary: Asynchronous (un)registration of metrics
 Key: FLINK-10081
 URL: https://issues.apache.org/jira/browse/FLINK-10081
 Project: Flink
  Issue Type: Improvement
  Components: Metrics
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler


Currently, whenever a metric is (un)registered the calling thread iterates over 
all reporters and executes their registration logic, which may involve slow or 
even blocking operations depending on the reporter implementation. For 
scheduled reporters this also introduces concurrency as registration can occur 
while a report is being created, potentially causing exceptions as seen in 
FLINK-10035.

I propose to make the registration of metrics asynchronous, i.e. when a metric 
is registered it is simply put in a queue instead that the metrics thread (that 
is also doing the reporting) would pull from.
This further isolates jobmanager/taskmanager/task threads from user-code, 
should speed up deployment/shutdown of tasks and makes interactions with 
reporters single-threaded.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FLINK-10082) Initialize StringBuilder in Slf4jReporter with estimated size

[Chesnay Schepler (JIRA)]

Chesnay Schepler created FLINK-10082:


 Summary: Initialize StringBuilder in Slf4jReporter with estimated 
size
 Key: FLINK-10082
 URL: https://issues.apache.org/jira/browse/FLINK-10082
 Project: Flink
  Issue Type: Improvement
  Components: Metrics
Affects Versions: 1.5.2, 1.6.0
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler


The {{Slf4jReporter}} uses a StringBuilder to generate the report that is later 
logged. Currently we don't pass the initial size, which for large deployments 
can result in frequent resizing of the backing array.

We could either estimate the expected size based on the # of metrics, or store 
the size of the last report (given that the total metrics space is fairly 
constant).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FLINK-10083) Kafka08ITCase#testOneSourceMultiplePartitions failed on travis

[Chesnay Schepler (JIRA)]

Chesnay Schepler created FLINK-10083:


 Summary: Kafka08ITCase#testOneSourceMultiplePartitions failed on 
travis
 Key: FLINK-10083
 URL: https://issues.apache.org/jira/browse/FLINK-10083
 Project: Flink
  Issue Type: Improvement
  Components: Kafka Connector
Affects Versions: 1.6.0
Reporter: Chesnay Schepler


https://travis-ci.org/apache/flink/jobs/412870682
{code}
Tests run: 23, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 76.531 sec <<< 
FAILURE! - in org.apache.flink.streaming.connectors.kafka.Kafka08ITCase
testOneSourceMultiplePartitions(org.apache.flink.streaming.connectors.kafka.Kafka08ITCase)
  Time elapsed: 4.115 sec  <<< FAILURE!
java.lang.AssertionError: Test failed: java.lang.Exception: Failed to restore 
state to function: Test failed due to unexpected recovered state size 0
at org.junit.Assert.fail(Assert.java:88)
at org.apache.flink.test.util.TestUtils.tryExecute(TestUtils.java:45)
at 
org.apache.flink.streaming.connectors.kafka.KafkaConsumerTestBase.runOneSourceMultiplePartitionsExactlyOnceTest(KafkaConsumerTestBase.java:927)
at 
org.apache.flink.streaming.connectors.kafka.Kafka08ITCase.testOneSourceMultiplePartitions(Kafka08ITCase.java:111)
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FLINK-10084) Migration tests weren't updated for 1.5 & 1.6

[Chesnay Schepler (JIRA)]

Chesnay Schepler created FLINK-10084:


 Summary: Migration tests weren't updated for 1.5 & 1.6
 Key: FLINK-10084
 URL: https://issues.apache.org/jira/browse/FLINK-10084
 Project: Flink
  Issue Type: Bug
  Components: State Backends, Checkpointing, Streaming, Streaming 
Connectors, Tests
Affects Versions: 1.5.0, 1.6.0
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler
 Fix For: 1.5.3, 1.6.1


We have several tests to verify that state taken in previous versions can be 
properly restored in the current one.

Most of these tests were not updated to cover the migration to 1.5 and 1.6.

Below are all the migration tests I could find:
* AbstractOperatorRestoreTestBase
* CEPMigrationTest
* BucketingSinkMigrationTest
* FlinkKafkaConsumerBaseMigrationTest
* ContinuousFileProcessingMigrationTest
* WindowOperatorMigrationTest
* StatefulJobSavepointMigrationITCase
* StatefulJobWBroadcastStateMigrationITCase



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FLINK-10085) Update AbstractOperatorRestoreTestBase

[Chesnay Schepler (JIRA)]

Chesnay Schepler created FLINK-10085:


 Summary: Update AbstractOperatorRestoreTestBase
 Key: FLINK-10085
 URL: https://issues.apache.org/jira/browse/FLINK-10085
 Project: Flink
  Issue Type: Sub-task
  Components: State Backends, Checkpointing, Streaming, Tests
Affects Versions: 1.5.0, 1.6.0
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler
 Fix For: 1.5.3, 1.6.1






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FLINK-10086) Update CEPMigrationTest

[Chesnay Schepler (JIRA)]

Chesnay Schepler created FLINK-10086:


 Summary: Update CEPMigrationTest
 Key: FLINK-10086
 URL: https://issues.apache.org/jira/browse/FLINK-10086
 Project: Flink
  Issue Type: Sub-task
  Components: CEP
Affects Versions: 1.6.0
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler
 Fix For: 1.6.1, 1.7.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FLINK-10087) Update BucketingSinkMigrationTest

[Chesnay Schepler (JIRA)]

Chesnay Schepler created FLINK-10087:


 Summary: Update BucketingSinkMigrationTest
 Key: FLINK-10087
 URL: https://issues.apache.org/jira/browse/FLINK-10087
 Project: Flink
  Issue Type: Sub-task
  Components: filesystem-connector
Affects Versions: 1.6.0
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler
 Fix For: 1.6.1, 1.7.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FLINK-10088) error when trying to run flink-sql-client on windows

[anubhav tarar (JIRA)]

anubhav tarar created FLINK-10088:
-

 Summary: error when trying to run flink-sql-client on windows
 Key: FLINK-10088
 URL: https://issues.apache.org/jira/browse/FLINK-10088
 Project: Flink
  Issue Type: Bug
  Components: Client
Affects Versions: 1.5.2
Reporter: anubhav tarar


When trying to run flink on windows it is giving me error

 

./config.sh: line 32: syntax error near unexpected token `<'
./config.sh: line 32: `    done < <(find "$FLINK_LIB_DIR" ! -type d -name 
'*.jar' -print0 | sort -z)'



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FLINK-10089) Update FlinkKafkaConsumerBaseMigrationTest

[Chesnay Schepler (JIRA)]

Chesnay Schepler created FLINK-10089:


 Summary: Update FlinkKafkaConsumerBaseMigrationTest
 Key: FLINK-10089
 URL: https://issues.apache.org/jira/browse/FLINK-10089
 Project: Flink
  Issue Type: Sub-task
  Components: Kafka Connector
Affects Versions: 1.6.0
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler
 Fix For: 1.6.1, 1.7.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FLINK-10090) Update ContinuousFileProcessingMigrationTest

[Chesnay Schepler (JIRA)]

Chesnay Schepler created FLINK-10090:


 Summary: Update ContinuousFileProcessingMigrationTest
 Key: FLINK-10090
 URL: https://issues.apache.org/jira/browse/FLINK-10090
 Project: Flink
  Issue Type: Sub-task
  Components: filesystem-connector
Affects Versions: 1.6.0
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler
 Fix For: 1.6.1, 1.7.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FLINK-10091) Update WindowOperatorMigrationTest

[Chesnay Schepler (JIRA)]

Chesnay Schepler created FLINK-10091:


 Summary: Update WindowOperatorMigrationTest
 Key: FLINK-10091
 URL: https://issues.apache.org/jira/browse/FLINK-10091
 Project: Flink
  Issue Type: Sub-task
  Components: Streaming
Affects Versions: 1.6.0
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler
 Fix For: 1.6.1, 1.7.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FLINK-10092) Update StatefulJobSavepointMigrationITCase

[Chesnay Schepler (JIRA)]

Chesnay Schepler created FLINK-10092:


 Summary: Update StatefulJobSavepointMigrationITCase
 Key: FLINK-10092
 URL: https://issues.apache.org/jira/browse/FLINK-10092
 Project: Flink
  Issue Type: Sub-task
  Components: State Backends, Checkpointing
Affects Versions: 1.6.0
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler
 Fix For: 1.6.1, 1.7.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FLINK-10093) Update StatefulJobWBroadcastStateMigrationITCase

[Chesnay Schepler (JIRA)]

Chesnay Schepler created FLINK-10093:


 Summary: Update StatefulJobWBroadcastStateMigrationITCase
 Key: FLINK-10093
 URL: https://issues.apache.org/jira/browse/FLINK-10093
 Project: Flink
  Issue Type: Sub-task
  Components: State Backends, Checkpointing
Affects Versions: 1.6.0
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler
 Fix For: 1.6.1, 1.7.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] Release 1.6.0, release candidate #3

[Andrey Zagrebin]

Hi everyone,

After careful consideration, I think that it makes sense to change the order of 
serialisation for state values with TTL. It will simplify further optimisations 
and feature improvements.

If it is still possible, I would ask to include this PR to the release 
candidate:
https://github.com/apache/flink/pull/6510 

This change will help to avoid compatibility issues in future.

Sorry for the short notice.

Thanks,
Andrey

> On 7 Aug 2018, at 10:01, Till Rohrmann  wrote:
> 
> Hi everyone,
> Please review and vote on the release candidate #3 for the version 1.6.0,
> as follows:
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
> 
> 
> The complete staging area is available for your review, which includes:
> * JIRA release notes [1],
> * the official Apache source release and binary convenience releases to be
> deployed to dist.apache.org [2], which are signed with the key with
> fingerprint 1F302569A96CFFD5 [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "release-1.6.0-rc3" [5],
> 
> Please use this document for coordinating testing efforts: [6]
> 
> The vote will be shortened since we only added minor fixes on top of the RC
> 2. It will close on Wednesday 6:30pm CET. It is adopted by majority
> approval, with at least 3 PMC affirmative votes.
> 
> Thanks,
> Your friendly Release Manager
> 
> [1]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12342760
> [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.6.0/
> [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> [4] https://repository.apache.org/content/repositories/orgapacheflink-1177
> [5] https://github.com/apache/flink/tree/release-1.6.0-rc3
> [6]
> https://docs.google.com/document/d/18rsgMQdT2OhpwdQOjb7WTuJlWdCi58N-lzdhELLBBsE/edit?usp=sharing
> 
> Pro-tip: you can create a settings.xml file with these contents:
> 
> 
> 
>  flink-1.6.0
> 
> 
>  
>flink-1.6.0
>
>  
>flink-1.6.0
>
> 
> https://repository.apache.org/content/repositories/orgapacheflink-1177/
>
>  
>  
>archetype
>
> 
> https://repository.apache.org/content/repositories/orgapacheflink-1177/
>
>  
>
>  
> 
> 
> 
> And reference that in you maven commands via --settings
> path/to/settings.xml. This is useful for creating a quickstart based on the
> staged release and for building against the staged jars.

[jira] [Created] (FLINK-10094) Always backup default config for end-to-end tests

[Chesnay Schepler (JIRA)]

Chesnay Schepler created FLINK-10094:


 Summary: Always backup default config for end-to-end tests
 Key: FLINK-10094
 URL: https://issues.apache.org/jira/browse/FLINK-10094
 Project: Flink
  Issue Type: Improvement
  Components: Tests
Affects Versions: 1.6.0
Reporter: Chesnay Schepler
Assignee: Chesnay Schepler
 Fix For: 1.6.1, 1.7.0


end-to-end tests frequently modify the configuration before running a test; to 
set state backends, # of task slots, reporters, etc.

Currently it is the responsibility of the test to create a backup of the config 
before doing any modifications, which is then restored by the runner after the 
test.

Instead we can have the test runner always create a backup before running the 
test.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FLINK-10095) Change the serialisation order in TTL value wrapper

[Andrey Zagrebin (JIRA)]

Andrey Zagrebin created FLINK-10095:
---

 Summary: Change the serialisation order in TTL value wrapper
 Key: FLINK-10095
 URL: https://issues.apache.org/jira/browse/FLINK-10095
 Project: Flink
  Issue Type: Improvement
  Components: State Backends, Checkpointing
Reporter: Andrey Zagrebin
Assignee: Andrey Zagrebin


The first implementation of TTL value wrapper has the following serialisation 
order: first user value, then last modification timestamp.

This was planned for potential optimisation where we could peek at the last 
bytes of last element of list to check whether the whole list expired or not. 
After careful consideration, it is not the frequent case and the list is 
handled per entry mostly.

Having the fixed part (the timestamp) at the beginning looks more promising in 
future as we can skip looking into the rest of bytes if needed when working 
directly with serialised value.

This issue suggests to change the serialisation order.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] Release 1.6.0, release candidate #3

[Till Rohrmann]

Thanks for reporting this issue Andrey. I think it would be good to include
this change into the 1.6 release in order to avoid additional backwards
compatibility work in the future. Therefore, I cancel this RC and will
publish a new RC as soon as we have merged the pull request #6510.

Cheers,
Till

On Tue, Aug 7, 2018 at 2:28 PM Andrey Zagrebin 
wrote:

> Hi everyone,
>
> After careful consideration, I think that it makes sense to change the
> order of serialisation for state values with TTL. It will simplify further
> optimisations and feature improvements.
>
> If it is still possible, I would ask to include this PR to the release
> candidate:
> https://github.com/apache/flink/pull/6510 <
> https://github.com/apache/flink/pull/6510>
> This change will help to avoid compatibility issues in future.
>
> Sorry for the short notice.
>
> Thanks,
> Andrey
>
> > On 7 Aug 2018, at 10:01, Till Rohrmann  wrote:
> >
> > Hi everyone,
> > Please review and vote on the release candidate #3 for the version 1.6.0,
> > as follows:
> > [ ] +1, Approve the release
> > [ ] -1, Do not approve the release (please provide specific comments)
> >
> >
> > The complete staging area is available for your review, which includes:
> > * JIRA release notes [1],
> > * the official Apache source release and binary convenience releases to
> be
> > deployed to dist.apache.org [2], which are signed with the key with
> > fingerprint 1F302569A96CFFD5 [3],
> > * all artifacts to be deployed to the Maven Central Repository [4],
> > * source code tag "release-1.6.0-rc3" [5],
> >
> > Please use this document for coordinating testing efforts: [6]
> >
> > The vote will be shortened since we only added minor fixes on top of the
> RC
> > 2. It will close on Wednesday 6:30pm CET. It is adopted by majority
> > approval, with at least 3 PMC affirmative votes.
> >
> > Thanks,
> > Your friendly Release Manager
> >
> > [1]
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12342760
> > [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.6.0/
> > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > [4]
> https://repository.apache.org/content/repositories/orgapacheflink-1177
> > [5] https://github.com/apache/flink/tree/release-1.6.0-rc3
> > [6]
> >
> https://docs.google.com/document/d/18rsgMQdT2OhpwdQOjb7WTuJlWdCi58N-lzdhELLBBsE/edit?usp=sharing
> >
> > Pro-tip: you can create a settings.xml file with these contents:
> >
> > 
> > 
> >  flink-1.6.0
> > 
> > 
> >  
> >flink-1.6.0
> >
> >  
> >flink-1.6.0
> >
> >
> > https://repository.apache.org/content/repositories/orgapacheflink-1177/
> >
> >  
> >  
> >archetype
> >
> >
> > https://repository.apache.org/content/repositories/orgapacheflink-1177/
> >
> >  
> >
> >  
> > 
> > 
> >
> > And reference that in you maven commands via --settings
> > path/to/settings.xml. This is useful for creating a quickstart based on
> the
> > staged release and for building against the staged jars.
>
>

Re: [VOTE] Release 1.6.0, release candidate #3

[Till Rohrmann]

FYI: The issue belonging to PR #6510 is
https://issues.apache.org/jira/browse/FLINK-10095.

On Tue, Aug 7, 2018 at 2:51 PM Till Rohrmann  wrote:

> Thanks for reporting this issue Andrey. I think it would be good to
> include this change into the 1.6 release in order to avoid additional
> backwards compatibility work in the future. Therefore, I cancel this RC and
> will publish a new RC as soon as we have merged the pull request #6510.
>
> Cheers,
> Till
>
> On Tue, Aug 7, 2018 at 2:28 PM Andrey Zagrebin 
> wrote:
>
>> Hi everyone,
>>
>> After careful consideration, I think that it makes sense to change the
>> order of serialisation for state values with TTL. It will simplify further
>> optimisations and feature improvements.
>>
>> If it is still possible, I would ask to include this PR to the release
>> candidate:
>> https://github.com/apache/flink/pull/6510 <
>> https://github.com/apache/flink/pull/6510>
>> This change will help to avoid compatibility issues in future.
>>
>> Sorry for the short notice.
>>
>> Thanks,
>> Andrey
>>
>> > On 7 Aug 2018, at 10:01, Till Rohrmann  wrote:
>> >
>> > Hi everyone,
>> > Please review and vote on the release candidate #3 for the version
>> 1.6.0,
>> > as follows:
>> > [ ] +1, Approve the release
>> > [ ] -1, Do not approve the release (please provide specific comments)
>> >
>> >
>> > The complete staging area is available for your review, which includes:
>> > * JIRA release notes [1],
>> > * the official Apache source release and binary convenience releases to
>> be
>> > deployed to dist.apache.org [2], which are signed with the key with
>> > fingerprint 1F302569A96CFFD5 [3],
>> > * all artifacts to be deployed to the Maven Central Repository [4],
>> > * source code tag "release-1.6.0-rc3" [5],
>> >
>> > Please use this document for coordinating testing efforts: [6]
>> >
>> > The vote will be shortened since we only added minor fixes on top of
>> the RC
>> > 2. It will close on Wednesday 6:30pm CET. It is adopted by majority
>> > approval, with at least 3 PMC affirmative votes.
>> >
>> > Thanks,
>> > Your friendly Release Manager
>> >
>> > [1]
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12342760
>> > [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.6.0/
>> > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
>> > [4]
>> https://repository.apache.org/content/repositories/orgapacheflink-1177
>> > [5] https://github.com/apache/flink/tree/release-1.6.0-rc3
>> > [6]
>> >
>> https://docs.google.com/document/d/18rsgMQdT2OhpwdQOjb7WTuJlWdCi58N-lzdhELLBBsE/edit?usp=sharing
>> >
>> > Pro-tip: you can create a settings.xml file with these contents:
>> >
>> > 
>> > 
>> >  flink-1.6.0
>> > 
>> > 
>> >  
>> >flink-1.6.0
>> >
>> >  
>> >flink-1.6.0
>> >
>> >
>> > https://repository.apache.org/content/repositories/orgapacheflink-1177/
>> >
>> >  
>> >  
>> >archetype
>> >
>> >
>> > https://repository.apache.org/content/repositories/orgapacheflink-1177/
>> >
>> >  
>> >
>> >  
>> > 
>> > 
>> >
>> > And reference that in you maven commands via --settings
>> > path/to/settings.xml. This is useful for creating a quickstart based on
>> the
>> > staged release and for building against the staged jars.
>>
>>

[jira] [Created] (FLINK-10096) Metrics report incorrect subtask ids

[Piotr Nowojski (JIRA)]

Piotr Nowojski created FLINK-10096:
--

 Summary: Metrics report incorrect subtask ids
 Key: FLINK-10096
 URL: https://issues.apache.org/jira/browse/FLINK-10096
 Project: Flink
  Issue Type: Bug
  Components: Metrics
Affects Versions: 1.6.0
Reporter: Piotr Nowojski


Subtask id is of by one when it's being reported by metrics compared to what is 
printed by {{StreamTask.toString()}}. For example metrics line:

Initial sorter.137.buffers.inputQueueLength: 392

vs actual name of this subtask:

Initial sorter (138/192)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[VOTE] Release 1.6.0, release candidate #4

[Till Rohrmann]

Hi everyone,
Please review and vote on the release candidate #4 for the version 1.6.0,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)


The complete staging area is available for your review, which includes:
* JIRA release notes [1],
* the official Apache source release and binary convenience releases to be
deployed to dist.apache.org [2], which are signed with the key with
fingerprint 1F302569A96CFFD5 [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "release-1.6.0-rc4" [5],
* website pull request listing the new release and adding announcement blog
post [6].

Please use this document for coordinating testing efforts: [7]

The vote will be shortened since we only adde a minor fix on top of the RC
3. It will close on Wednesday 6:30pm CET. It is adopted by majority
approval, with at least 3 PMC affirmative votes.

Thanks,
Your friendly Release Manager

[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12342760
[2] https://dist.apache.org/repos/dist/dev/flink/flink-1.6.0/
[3] https://dist.apache.org/repos/dist/release/flink/KEYS
[4] https://repository.apache.org/content/repositories/orgapacheflink-1178
[5] https://github.com/apache/flink/tree/release-1.6.0-rc4
[6] https://github.com/apache/flink-web/pull/117
[7]
https://docs.google.com/document/d/1upBFZQ7tbaSkYvDiLqfUFXKg8Xxs-lVheEfb66e4jpo/edit?usp=sharing

Pro-tip: you can create a settings.xml file with these contents:



  flink-1.6.0


  
flink-1.6.0

  
flink-1.6.0


https://repository.apache.org/content/repositories/orgapacheflink-1178/

  
  
archetype


https://repository.apache.org/content/repositories/orgapacheflink-1178/

  

  



And reference that in you maven commands via --settings
path/to/settings.xml. This is useful for creating a quickstart based on the
staged release and for building against the staged jars.

[ANNOUNCE] Weekly community update #32

[Till Rohrmann]

Dear community,

this is the weekly community update thread #32. Please post any news and
updates you want to share with the community to this thread.

# Flink 1.6.0 voting period about to end

The voting period for the 4th RC of Flink 1.6.0 will end Wednesday 6:30pm
CET [1]. So far there seem to be no release blockers. If it stays like
this, then the community will be able to release Flink 1.6.0 very soon :-)
If you want to test out the latest RC please use the following binaries [2].

[1]
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/VOTE-Release-1-6-0-release-candidate-4-td23723.html
[2] https://dist.apache.org/repos/dist/dev/flink/flink-1.6.0/

Cheers,
Till

[jira] [Created] (FLINK-10097) More tests to increase StreamingFileSink test coverage

[Kostas Kloudas (JIRA)]

Kostas Kloudas created FLINK-10097:
--

 Summary: More tests to increase StreamingFileSink test coverage
 Key: FLINK-10097
 URL: https://issues.apache.org/jira/browse/FLINK-10097
 Project: Flink
  Issue Type: Sub-task
  Components: filesystem-connector
Affects Versions: 1.6.0
Reporter: Kostas Kloudas
Assignee: Kostas Kloudas
 Fix For: 1.6.1






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FLINK-10098) Programmatically select timer storage backend

[Elias Levy (JIRA)]

Elias Levy created FLINK-10098:
--

 Summary: Programmatically select timer storage backend
 Key: FLINK-10098
 URL: https://issues.apache.org/jira/browse/FLINK-10098
 Project: Flink
  Issue Type: Improvement
  Components: State Backends, Checkpointing, Streaming, TaskManager
Affects Versions: 1.6.0, 1.7.0
Reporter: Elias Levy


FLINK-9486 introduced timer storage on the RocksDB storage backend.  Right now 
it is only possible to configure RocksDB as the storage for timers by settings 
the {{state.backend.rocksdb.timer-service.factory}} value in the configuration 
file for Flink.

As the state storage backend can be programmatically selected by by jobs via  
{{env.setStateBackend(...)}}, the timer backend should also be configurable 
programmatically.

Different jobs should be able to store their timers in different storage 
backends.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (FLINK-10099) Rework YarnResourceManagerTest

[JIRA]

陈梓立 created FLINK-10099:
---

 Summary: Rework YarnResourceManagerTest
 Key: FLINK-10099
 URL: https://issues.apache.org/jira/browse/FLINK-10099
 Project: Flink
  Issue Type: Improvement
  Components: Tests
Affects Versions: 1.6.0
Reporter: 陈梓立
Assignee: 陈梓立
 Fix For: 1.6.0


To avoid OOM and gather mock stuff for replacing them once we could.

also structure the test.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)