[GitHub] [flink] flinkbot edited a comment on issue #9637: [FLINK-13884] Set default delay for restart strategies to 1s
flinkbot edited a comment on issue #9637: [FLINK-13884] Set default delay for restart strategies to 1s URL: https://github.com/apache/flink/pull/9637#issuecomment-528794398 Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community to review your pull request. We will use this comment to track the progress of the review. ## Automated Checks Last check on commit 9b959c0ad2d1c401459d4dd3e3152f9189cca7c2 (Tue Sep 10 06:50:02 UTC 2019) **Warnings:** * No documentation files were touched! Remember to keep the Flink docs up to date! Mention the bot in a comment to re-run the automated checks. ## Review Progress * ❓ 1. The [description] looks good. * ❓ 2. There is [consensus] that the contribution should go into to Flink. * ❓ 3. Needs [attention] from. * ❓ 4. The change fits into the overall [architecture]. * ❓ 5. Overall code [quality] is good. Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands The @flinkbot bot supports the following commands: - `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`) - `@flinkbot approve all` to approve all aspects - `@flinkbot approve-until architecture` to approve everything until `architecture` - `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention - `@flinkbot disapprove architecture` to remove an approval you gave earlier This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] GJL commented on a change in pull request #9637: [FLINK-13884] Set default delay for restart strategies to 1s
GJL commented on a change in pull request #9637: [FLINK-13884] Set default
delay for restart strategies to 1s
URL: https://github.com/apache/flink/pull/9637#discussion_r322576564
##
File path:
flink-runtime/src/main/java/org/apache/flink/runtime/executiongraph/restart/FailureRateRestartStrategy.java
##
@@ -92,12 +91,9 @@ public String toString() {
public static FailureRateRestartStrategyFactory
createFactory(Configuration configuration) throws Exception {
int maxFailuresPerInterval =
configuration.getInteger(RestartStrategyOptions.RESTART_STRATEGY_FAILURE_RATE_MAX_FAILURES_PER_INTERVAL);
- String failuresIntervalString =
configuration.getString(RestartStrategyOptions.RESTART_STRATEGY_FAILURE_RATE_FAILURE_RATE_INTERVAL);
- String timeoutString =
configuration.getString(AkkaOptions.WATCH_HEARTBEAT_INTERVAL);
Review comment:
ok
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] flinkbot commented on issue #9657: [FLINK-14000] [runtime] Remove legacy ProcessShutDownThread
flinkbot commented on issue #9657: [FLINK-14000] [runtime] Remove legacy ProcessShutDownThread URL: https://github.com/apache/flink/pull/9657#issuecomment-529796840 Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community to review your pull request. We will use this comment to track the progress of the review. ## Automated Checks Last check on commit d0fa39605e35940d8f36c5296627c4e3825867dd (Tue Sep 10 06:48:04 UTC 2019) **Warnings:** * No documentation files were touched! Remember to keep the Flink docs up to date! Mention the bot in a comment to re-run the automated checks. ## Review Progress * ❓ 1. The [description] looks good. * ❓ 2. There is [consensus] that the contribution should go into to Flink. * ❓ 3. Needs [attention] from. * ❓ 4. The change fits into the overall [architecture]. * ❓ 5. Overall code [quality] is good. Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands The @flinkbot bot supports the following commands: - `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`) - `@flinkbot approve all` to approve all aspects - `@flinkbot approve-until architecture` to approve everything until `architecture` - `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention - `@flinkbot disapprove architecture` to remove an approval you gave earlier This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (FLINK-14000) Remove legacy ProcessShutDownThread
[ https://issues.apache.org/jira/browse/FLINK-14000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated FLINK-14000: --- Labels: pull-request-available (was: ) > Remove legacy ProcessShutDownThread > --- > > Key: FLINK-14000 > URL: https://issues.apache.org/jira/browse/FLINK-14000 > Project: Flink > Issue Type: Sub-task > Components: Runtime / Coordination >Affects Versions: 1.10.0 >Reporter: Zhu Zhu >Assignee: Zhu Zhu >Priority: Major > Labels: pull-request-available > Fix For: 1.10.0 > > > The class _org.apache.flink.runtime.util.ProcessShutDownThread_ is not > referenced by any other classes/configs/scripts any more. > I think it's dead code and we can remove it. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (FLINK-14000) Remove legacy ProcessShutDownThread
[ https://issues.apache.org/jira/browse/FLINK-14000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhu Zhu updated FLINK-14000: Fix Version/s: 1.10.0 > Remove legacy ProcessShutDownThread > --- > > Key: FLINK-14000 > URL: https://issues.apache.org/jira/browse/FLINK-14000 > Project: Flink > Issue Type: Sub-task > Components: Runtime / Coordination >Affects Versions: 1.10.0 >Reporter: Zhu Zhu >Assignee: Zhu Zhu >Priority: Major > Fix For: 1.10.0 > > > The class _org.apache.flink.runtime.util.ProcessShutDownThread_ is not > referenced by any other classes/configs/scripts any more. > I think it's dead code and we can remove it. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[GitHub] [flink] zhuzhurk opened a new pull request #9657: [FLINK-14000] [runtime] Remove legacy ProcessShutDownThread
zhuzhurk opened a new pull request #9657: [FLINK-14000] [runtime] Remove legacy ProcessShutDownThread URL: https://github.com/apache/flink/pull/9657 ## What is the purpose of the change *This PR is to remove class org.apache.flink.runtime.util.ProcessShutDownThread which is not referenced by any other classes/configs/scripts any more.* ## Brief change log *Removed class org.apache.flink.runtime.util.ProcessShutDownThread* ## Verifying this change This change is a trivial rework / code cleanup without any test coverage. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (yes / **no**) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / **no**) - The serializers: (yes / **no** / don't know) - The runtime per-record code paths (performance sensitive): (yes / **no** / don't know) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / **no** / don't know) - The S3 file system connector: (yes / **no** / don't know) ## Documentation - Does this pull request introduce a new feature? (yes / **no**) - If yes, how is the feature documented? (**not applicable** / docs / JavaDocs / not documented) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9587: [FLINK-13685][yarn] Validate YARN deployment against YARN scheduler maximum vcore size
flinkbot edited a comment on issue #9587: [FLINK-13685][yarn] Validate YARN deployment against YARN scheduler maximum vcore size URL: https://github.com/apache/flink/pull/9587#issuecomment-526997659 ## CI report: * 667c738c79302b11cad210edbfb007866be29fdf : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/125383021) * 6198adda939d2fa12aeb3d1287b55e0c9412fafb : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/125498979) * 304769da1c49df00319b8c047259d5bfd961ef03 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/126537027) * 08d07d015e9d1daf990d83eaf2f4278bae2d504e : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/126539177) * 8cabaf4de3b4a16c154842a280fbf8eeb3f06fce : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/126550642) * 210c928f02a02675dfd9c8d4d384eba57652717d : UNKNOWN This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9587: [FLINK-13685][yarn] Validate YARN deployment against YARN scheduler maximum vcore size
flinkbot edited a comment on issue #9587: [FLINK-13685][yarn] Validate YARN deployment against YARN scheduler maximum vcore size URL: https://github.com/apache/flink/pull/9587#issuecomment-526995997 Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community to review your pull request. We will use this comment to track the progress of the review. ## Automated Checks Last check on commit 210c928f02a02675dfd9c8d4d384eba57652717d (Tue Sep 10 06:25:36 UTC 2019) **Warnings:** * No documentation files were touched! Remember to keep the Flink docs up to date! Mention the bot in a comment to re-run the automated checks. ## Review Progress * ❓ 1. The [description] looks good. * ❓ 2. There is [consensus] that the contribution should go into to Flink. * ❓ 3. Needs [attention] from. * ❓ 4. The change fits into the overall [architecture]. * ❓ 5. Overall code [quality] is good. Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands The @flinkbot bot supports the following commands: - `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`) - `@flinkbot approve all` to approve all aspects - `@flinkbot approve-until architecture` to approve everything until `architecture` - `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention - `@flinkbot disapprove architecture` to remove an approval you gave earlier This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #7942: [FLINK-11696][checkpoint] Avoid to send mkdir requests to DFS from task side
flinkbot edited a comment on issue #7942: [FLINK-11696][checkpoint] Avoid to send mkdir requests to DFS from task side URL: https://github.com/apache/flink/pull/7942#issuecomment-470819951 Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community to review your pull request. We will use this comment to track the progress of the review. ## Automated Checks Last check on commit 0c9299f1ac0102c17941c7b0635005b48af2c243 (Tue Sep 10 06:20:31 UTC 2019) **Warnings:** * No documentation files were touched! Remember to keep the Flink docs up to date! Mention the bot in a comment to re-run the automated checks. ## Review Progress * ❓ 1. The [description] looks good. * ❓ 2. There is [consensus] that the contribution should go into to Flink. * ❓ 3. Needs [attention] from. * ❓ 4. The change fits into the overall [architecture]. * ❓ 5. Overall code [quality] is good. Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands The @flinkbot bot supports the following commands: - `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`) - `@flinkbot approve all` to approve all aspects - `@flinkbot approve-until architecture` to approve everything until `architecture` - `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention - `@flinkbot disapprove architecture` to remove an approval you gave earlier This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] Myasuka commented on issue #7942: [FLINK-11696][checkpoint] Avoid to send mkdir requests to DFS from task side
Myasuka commented on issue #7942: [FLINK-11696][checkpoint] Avoid to send mkdir requests to DFS from task side URL: https://github.com/apache/flink/pull/7942#issuecomment-529788177 @AHeise thanks for your reply, but from my mind, you could directly review my code at `Files changed` tab which includes all changes. Since you don't want to see the outdated discussion, I think you could start review on the 74 lines directly as a totally new PR instead of taking account of previous discussion. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9478: [FLINK-13766][task] Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext
flinkbot edited a comment on issue #9478: [FLINK-13766][task] Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext URL: https://github.com/apache/flink/pull/9478#issuecomment-522374042 ## CI report: * 1530600eaf36324966f343c277437e48c2416dc2 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/123653758) * 8d08aaa1fedf7338ef3de48991e841f9baf7018b : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/123700944) * 9791697c559fa39cd9f7a1c574420d62a1193545 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124210361) * fbd14e2320371a3cd6615deee0498d477644b954 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124297960) * 04f75585056f083e57aa036d5fccf14286c073ee : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124687473) * cc68c22f6cba85de6ef7babad5a42b9bf187e59f : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124691082) * 6a276b78132bf3de6691a073134865e9c7632fcf : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124692424) * 84806d71cfe3ba5d2f0c1fc8136dcd1fd64251cf : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124693853) * b74f4e456ccad744aedff59da951bfc099ce13c8 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124700117) * f84935334f191b73b5766550743de3193ccb1ada : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124701767) * 61e0d65b905bc86dda95b8d81e9163177434adce : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124706860) * 9cdfb712682d5f07c0249bebc873ebd5879d1ec1 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124712485) * e1ab467f585b289eb02c6bcf206b6f73d71d1c51 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124714601) * 2da198414e1421f855d035741207c0d00aa946f3 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124718316) * 4aba3ff64ff2a4f2518150bc7d4ca37f42adf1fb : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124726416) * 53fbb0b3e1b094ef82b8f3192146aeb4a915dda7 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124845339) * eec2a79613ec30b174e2e133c4e3844c5e27f443 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124857651) * 27f1c1d0224a43754beee2e6d4637de8d942db16 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/125408360) * 2225da63d943df06eacceb57c7d77de7aa90dfc1 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/125527049) * d99301f4c6704710c479647a14d170080cea79b2 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/125545740) * 52ec180a141ebc5d26519f8bc3ac4892ad054f8a : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/125550692) * 96d5c224e6a3258a84b9e943a93bb12dff93253f : CANCELED [Build](https://travis-ci.com/flink-ci/flink/builds/126558705) * a3e09500022ee31f5f1fb8c406a8f939a2d5f87c : PENDING [Build](https://travis-ci.com/flink-ci/flink/builds/126559774) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (FLINK-13748) Streaming File Sink s3 end-to-end test failed on Travis
[
https://issues.apache.org/jira/browse/FLINK-13748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926353#comment-16926353
]
Till Rohrmann commented on FLINK-13748:
---
[~kkl0u] could you take a look at this issue in order to find out what the
problem could be?
> Streaming File Sink s3 end-to-end test failed on Travis
> ---
>
> Key: FLINK-13748
> URL: https://issues.apache.org/jira/browse/FLINK-13748
> Project: Flink
> Issue Type: Bug
> Components: Connectors / FileSystem, Tests
>Affects Versions: 1.10.0
>Reporter: Till Rohrmann
>Priority: Critical
> Labels: test-stability
> Fix For: 1.10.0
>
>
> The {{Streaming File Sink s3 end-to-end test}} failed on Travis because it
> did not produce any output for 10 minutes.
> https://api.travis-ci.org/v3/job/572255913/log.txt
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[GitHub] [flink] flinkbot edited a comment on issue #9637: [FLINK-13884] Set default delay for restart strategies to 1s
flinkbot edited a comment on issue #9637: [FLINK-13884] Set default delay for restart strategies to 1s URL: https://github.com/apache/flink/pull/9637#issuecomment-528794398 Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community to review your pull request. We will use this comment to track the progress of the review. ## Automated Checks Last check on commit 9b959c0ad2d1c401459d4dd3e3152f9189cca7c2 (Tue Sep 10 06:12:23 UTC 2019) **Warnings:** * No documentation files were touched! Remember to keep the Flink docs up to date! Mention the bot in a comment to re-run the automated checks. ## Review Progress * ❓ 1. The [description] looks good. * ❓ 2. There is [consensus] that the contribution should go into to Flink. * ❓ 3. Needs [attention] from. * ❓ 4. The change fits into the overall [architecture]. * ❓ 5. Overall code [quality] is good. Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands The @flinkbot bot supports the following commands: - `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`) - `@flinkbot approve all` to approve all aspects - `@flinkbot approve-until architecture` to approve everything until `architecture` - `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention - `@flinkbot disapprove architecture` to remove an approval you gave earlier This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (FLINK-13748) Streaming File Sink s3 end-to-end test failed on Travis
[
https://issues.apache.org/jira/browse/FLINK-13748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926352#comment-16926352
]
Till Rohrmann commented on FLINK-13748:
---
Another instance: https://api.travis-ci.org/v3/job/582875585/log.txt
> Streaming File Sink s3 end-to-end test failed on Travis
> ---
>
> Key: FLINK-13748
> URL: https://issues.apache.org/jira/browse/FLINK-13748
> Project: Flink
> Issue Type: Bug
> Components: Connectors / FileSystem, Tests
>Affects Versions: 1.10.0
>Reporter: Till Rohrmann
>Priority: Critical
> Labels: test-stability
> Fix For: 1.10.0
>
>
> The {{Streaming File Sink s3 end-to-end test}} failed on Travis because it
> did not produce any output for 10 minutes.
> https://api.travis-ci.org/v3/job/572255913/log.txt
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[GitHub] [flink] zhuzhurk commented on issue #9637: [FLINK-13884] Set default delay for restart strategies to 1s
zhuzhurk commented on issue #9637: [FLINK-13884] Set default delay for restart strategies to 1s URL: https://github.com/apache/flink/pull/9637#issuecomment-529786124 The build breaks due to the default values of for "restart-strategy.failure-rate.delay" and "restart-strategy.fixed-delay.delay" are not updated in generated docs. I think we can merge this PR once the docs are regenerated. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9478: [FLINK-13766][task] Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext
flinkbot edited a comment on issue #9478: [FLINK-13766][task] Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext URL: https://github.com/apache/flink/pull/9478#issuecomment-522374042 ## CI report: * 1530600eaf36324966f343c277437e48c2416dc2 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/123653758) * 8d08aaa1fedf7338ef3de48991e841f9baf7018b : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/123700944) * 9791697c559fa39cd9f7a1c574420d62a1193545 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124210361) * fbd14e2320371a3cd6615deee0498d477644b954 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124297960) * 04f75585056f083e57aa036d5fccf14286c073ee : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124687473) * cc68c22f6cba85de6ef7babad5a42b9bf187e59f : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124691082) * 6a276b78132bf3de6691a073134865e9c7632fcf : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124692424) * 84806d71cfe3ba5d2f0c1fc8136dcd1fd64251cf : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124693853) * b74f4e456ccad744aedff59da951bfc099ce13c8 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124700117) * f84935334f191b73b5766550743de3193ccb1ada : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124701767) * 61e0d65b905bc86dda95b8d81e9163177434adce : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124706860) * 9cdfb712682d5f07c0249bebc873ebd5879d1ec1 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124712485) * e1ab467f585b289eb02c6bcf206b6f73d71d1c51 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124714601) * 2da198414e1421f855d035741207c0d00aa946f3 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124718316) * 4aba3ff64ff2a4f2518150bc7d4ca37f42adf1fb : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124726416) * 53fbb0b3e1b094ef82b8f3192146aeb4a915dda7 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124845339) * eec2a79613ec30b174e2e133c4e3844c5e27f443 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124857651) * 27f1c1d0224a43754beee2e6d4637de8d942db16 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/125408360) * 2225da63d943df06eacceb57c7d77de7aa90dfc1 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/125527049) * d99301f4c6704710c479647a14d170080cea79b2 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/125545740) * 52ec180a141ebc5d26519f8bc3ac4892ad054f8a : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/125550692) * 96d5c224e6a3258a84b9e943a93bb12dff93253f : PENDING [Build](https://travis-ci.com/flink-ci/flink/builds/126558705) * a3e09500022ee31f5f1fb8c406a8f939a2d5f87c : UNKNOWN This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9478: [FLINK-13766][task] Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext
flinkbot edited a comment on issue #9478: [FLINK-13766][task] Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext URL: https://github.com/apache/flink/pull/9478#issuecomment-522373234 Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community to review your pull request. We will use this comment to track the progress of the review. ## Automated Checks Last check on commit a3e09500022ee31f5f1fb8c406a8f939a2d5f87c (Tue Sep 10 05:56:07 UTC 2019) **Warnings:** * No documentation files were touched! Remember to keep the Flink docs up to date! Mention the bot in a comment to re-run the automated checks. ## Review Progress * ❓ 1. The [description] looks good. * ❓ 2. There is [consensus] that the contribution should go into to Flink. * ❓ 3. Needs [attention] from. * ❓ 4. The change fits into the overall [architecture]. * ❓ 5. Overall code [quality] is good. Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands The @flinkbot bot supports the following commands: - `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`) - `@flinkbot approve all` to approve all aspects - `@flinkbot approve-until architecture` to approve everything until `architecture` - `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention - `@flinkbot disapprove architecture` to remove an approval you gave earlier This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (FLINK-14031) flink-examples-table should add the blink planner dependency
[
https://issues.apache.org/jira/browse/FLINK-14031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kurt Young updated FLINK-14031:
---
Fix Version/s: (was: 1.9.0)
> flink-examples-table should add the blink planner dependency
>
>
> Key: FLINK-14031
> URL: https://issues.apache.org/jira/browse/FLINK-14031
> Project: Flink
> Issue Type: Bug
> Components: Examples
>Affects Versions: 1.9.0
>Reporter: Jimmy Wong
>Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The flink-examples-table module is missing blink planner dependency. If I run
> a blink example with Intellij IDEA, have error:
>
> {code:java}
> Exception in thread "main" org.apache.flink.table.api.TableException: Could
> not instantiate the executor. Make sure a planner module is on the
> classpathException in thread "main"
> org.apache.flink.table.api.TableException: Could not instantiate the
> executor. Make sure a planner module is on the classpath at
> org.apache.flink.table.api.java.internal.StreamTableEnvironmentImpl.lookupExecutor(StreamTableEnvironmentImpl.java:140)
> at
> org.apache.flink.table.api.java.internal.StreamTableEnvironmentImpl.create(StreamTableEnvironmentImpl.java:110)
> at
> org.apache.flink.table.api.java.StreamTableEnvironment.create(StreamTableEnvironment.java:112)
> at
> org.apache.flink.table.examples.java.BlinkStreamSQL.main(BlinkStreamSQL.java:19)Caused
> by: org.apache.flink.table.api.NoMatchingTableFactoryException: Could not
> find a suitable table factory for
> 'org.apache.flink.table.delegation.ExecutorFactory' inthe classpath.
> {code}
> *But*, once I add blink planner dependency, it'll work well.
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[GitHub] [flink] flinkbot edited a comment on issue #9478: [FLINK-13766][task] Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext
flinkbot edited a comment on issue #9478: [FLINK-13766][task] Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext URL: https://github.com/apache/flink/pull/9478#issuecomment-522373234 Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community to review your pull request. We will use this comment to track the progress of the review. ## Automated Checks Last check on commit f79af1ba3dcb1878316a9851cf07ccedd0a0e762 (Tue Sep 10 05:48:58 UTC 2019) **Warnings:** * No documentation files were touched! Remember to keep the Flink docs up to date! Mention the bot in a comment to re-run the automated checks. ## Review Progress * ❓ 1. The [description] looks good. * ❓ 2. There is [consensus] that the contribution should go into to Flink. * ❓ 3. Needs [attention] from. * ❓ 4. The change fits into the overall [architecture]. * ❓ 5. Overall code [quality] is good. Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands The @flinkbot bot supports the following commands: - `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`) - `@flinkbot approve all` to approve all aspects - `@flinkbot approve-until architecture` to approve everything until `architecture` - `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention - `@flinkbot disapprove architecture` to remove an approval you gave earlier This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9478: [FLINK-13766][task] Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext
flinkbot edited a comment on issue #9478: [FLINK-13766][task] Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext URL: https://github.com/apache/flink/pull/9478#issuecomment-522374042 ## CI report: * 1530600eaf36324966f343c277437e48c2416dc2 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/123653758) * 8d08aaa1fedf7338ef3de48991e841f9baf7018b : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/123700944) * 9791697c559fa39cd9f7a1c574420d62a1193545 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124210361) * fbd14e2320371a3cd6615deee0498d477644b954 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124297960) * 04f75585056f083e57aa036d5fccf14286c073ee : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124687473) * cc68c22f6cba85de6ef7babad5a42b9bf187e59f : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124691082) * 6a276b78132bf3de6691a073134865e9c7632fcf : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124692424) * 84806d71cfe3ba5d2f0c1fc8136dcd1fd64251cf : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124693853) * b74f4e456ccad744aedff59da951bfc099ce13c8 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124700117) * f84935334f191b73b5766550743de3193ccb1ada : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124701767) * 61e0d65b905bc86dda95b8d81e9163177434adce : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124706860) * 9cdfb712682d5f07c0249bebc873ebd5879d1ec1 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124712485) * e1ab467f585b289eb02c6bcf206b6f73d71d1c51 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124714601) * 2da198414e1421f855d035741207c0d00aa946f3 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124718316) * 4aba3ff64ff2a4f2518150bc7d4ca37f42adf1fb : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124726416) * 53fbb0b3e1b094ef82b8f3192146aeb4a915dda7 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124845339) * eec2a79613ec30b174e2e133c4e3844c5e27f443 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/124857651) * 27f1c1d0224a43754beee2e6d4637de8d942db16 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/125408360) * 2225da63d943df06eacceb57c7d77de7aa90dfc1 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/125527049) * d99301f4c6704710c479647a14d170080cea79b2 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/125545740) * 52ec180a141ebc5d26519f8bc3ac4892ad054f8a : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/125550692) * 96d5c224e6a3258a84b9e943a93bb12dff93253f : UNKNOWN This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9478: [FLINK-13766][task] Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext
flinkbot edited a comment on issue #9478: [FLINK-13766][task] Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext URL: https://github.com/apache/flink/pull/9478#issuecomment-522373234 Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community to review your pull request. We will use this comment to track the progress of the review. ## Automated Checks Last check on commit 96d5c224e6a3258a84b9e943a93bb12dff93253f (Tue Sep 10 05:25:34 UTC 2019) **Warnings:** * No documentation files were touched! Remember to keep the Flink docs up to date! Mention the bot in a comment to re-run the automated checks. ## Review Progress * ❓ 1. The [description] looks good. * ❓ 2. There is [consensus] that the contribution should go into to Flink. * ❓ 3. Needs [attention] from. * ❓ 4. The change fits into the overall [architecture]. * ❓ 5. Overall code [quality] is good. Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands The @flinkbot bot supports the following commands: - `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`) - `@flinkbot approve all` to approve all aspects - `@flinkbot approve-until architecture` to approve everything until `architecture` - `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention - `@flinkbot disapprove architecture` to remove an approval you gave earlier This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9656: [FLINK-14031][examples][table]Added the blink planner dependency and a example which use blink planner to flink-examples-table.
flinkbot edited a comment on issue #9656: [FLINK-14031][examples][table]Added the blink planner dependency and a example which use blink planner to flink-examples-table. URL: https://github.com/apache/flink/pull/9656#issuecomment-529769037 ## CI report: * cdfb2bf661da8fd51ce52843a0a8d3bac8b78170 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/126555210) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9655: [FLINK-14017][python] Support to start up Python worker in process mode.
flinkbot edited a comment on issue #9655: [FLINK-14017][python] Support to start up Python worker in process mode. URL: https://github.com/apache/flink/pull/9655#issuecomment-529754597 ## CI report: * e02c8a291f5c82505750e200dda9b07d5e8b2fca : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/126550624) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot commented on issue #9656: [FLINK-14031][examples][table]Added the blink planner dependency and a example which use blink planner to flink-examples-table.
flinkbot commented on issue #9656: [FLINK-14031][examples][table]Added the blink planner dependency and a example which use blink planner to flink-examples-table. URL: https://github.com/apache/flink/pull/9656#issuecomment-529769037 ## CI report: * cdfb2bf661da8fd51ce52843a0a8d3bac8b78170 : UNKNOWN This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot commented on issue #9656: [FLINK-14031][examples][table]Added the blink planner dependency and a example which use blink planner to flink-examples-table.
flinkbot commented on issue #9656: [FLINK-14031][examples][table]Added the blink planner dependency and a example which use blink planner to flink-examples-table. URL: https://github.com/apache/flink/pull/9656#issuecomment-529768266 Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community to review your pull request. We will use this comment to track the progress of the review. ## Automated Checks Last check on commit cdfb2bf661da8fd51ce52843a0a8d3bac8b78170 (Tue Sep 10 04:50:36 UTC 2019) **Warnings:** * **1 pom.xml files were touched**: Check for build and licensing issues. * No documentation files were touched! Remember to keep the Flink docs up to date! * **This pull request references an unassigned [Jira ticket](https://issues.apache.org/jira/browse/FLINK-14031).** According to the [code contribution guide](https://flink.apache.org/contributing/contribute-code.html), tickets need to be assigned before starting with the implementation work. Mention the bot in a comment to re-run the automated checks. ## Review Progress * ❓ 1. The [description] looks good. * ❓ 2. There is [consensus] that the contribution should go into to Flink. * ❓ 3. Needs [attention] from. * ❓ 4. The change fits into the overall [architecture]. * ❓ 5. Overall code [quality] is good. Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands The @flinkbot bot supports the following commands: - `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`) - `@flinkbot approve all` to approve all aspects - `@flinkbot approve-until architecture` to approve everything until `architecture` - `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention - `@flinkbot disapprove architecture` to remove an approval you gave earlier This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (FLINK-14031) flink-examples-table should add the blink planner dependency
[
https://issues.apache.org/jira/browse/FLINK-14031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-14031:
---
Labels: pull-request-available (was: )
> flink-examples-table should add the blink planner dependency
>
>
> Key: FLINK-14031
> URL: https://issues.apache.org/jira/browse/FLINK-14031
> Project: Flink
> Issue Type: Bug
> Components: Examples
>Affects Versions: 1.9.0
>Reporter: Jimmy Wong
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.9.0
>
>
> The flink-examples-table module is missing blink planner dependency. If I run
> a blink example with Intellij IDEA, have error:
>
> {code:java}
> Exception in thread "main" org.apache.flink.table.api.TableException: Could
> not instantiate the executor. Make sure a planner module is on the
> classpathException in thread "main"
> org.apache.flink.table.api.TableException: Could not instantiate the
> executor. Make sure a planner module is on the classpath at
> org.apache.flink.table.api.java.internal.StreamTableEnvironmentImpl.lookupExecutor(StreamTableEnvironmentImpl.java:140)
> at
> org.apache.flink.table.api.java.internal.StreamTableEnvironmentImpl.create(StreamTableEnvironmentImpl.java:110)
> at
> org.apache.flink.table.api.java.StreamTableEnvironment.create(StreamTableEnvironment.java:112)
> at
> org.apache.flink.table.examples.java.BlinkStreamSQL.main(BlinkStreamSQL.java:19)Caused
> by: org.apache.flink.table.api.NoMatchingTableFactoryException: Could not
> find a suitable table factory for
> 'org.apache.flink.table.delegation.ExecutorFactory' inthe classpath.
> {code}
> *But*, once I add blink planner dependency, it'll work well.
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[GitHub] [flink] GatsbyNewton opened a new pull request #9656: [FLINK-14031][examples][table]Added the blink planner dependency and a example which use blink planner to flink-examples-table.
GatsbyNewton opened a new pull request #9656: [FLINK-14031][examples][table]Added the blink planner dependency and a example which use blink planner to flink-examples-table. URL: https://github.com/apache/flink/pull/9656 ## What is the purpose of the change Added the blink planner dependency and a example which use blink planner to flink-examples-table. ## Brief change log - Add the blink planner dependency. - Add a example which use blink planner. ## Verifying this change Manually verified. Ran examples on idea and a local cluster. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (yes) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (no) - The serializers: (no) - The runtime per-record code paths (performance sensitive): (no) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no) - The S3 file system connector: (no) ## Documentation - Does this pull request introduce a new feature? (no) - If yes, how is the feature documented? (not applicable) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (FLINK-14031) flink-examples-table should add the blink planner dependency
[
https://issues.apache.org/jira/browse/FLINK-14031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jimmy Wong updated FLINK-14031:
---
Fix Version/s: 1.9.0
> flink-examples-table should add the blink planner dependency
>
>
> Key: FLINK-14031
> URL: https://issues.apache.org/jira/browse/FLINK-14031
> Project: Flink
> Issue Type: Bug
> Components: Examples
>Affects Versions: 1.9.0
>Reporter: Jimmy Wong
>Priority: Major
> Fix For: 1.9.0
>
>
> The flink-examples-table module is missing blink planner dependency. If I run
> a blink example with Intellij IDEA, have error:
>
> {code:java}
> Exception in thread "main" org.apache.flink.table.api.TableException: Could
> not instantiate the executor. Make sure a planner module is on the
> classpathException in thread "main"
> org.apache.flink.table.api.TableException: Could not instantiate the
> executor. Make sure a planner module is on the classpath at
> org.apache.flink.table.api.java.internal.StreamTableEnvironmentImpl.lookupExecutor(StreamTableEnvironmentImpl.java:140)
> at
> org.apache.flink.table.api.java.internal.StreamTableEnvironmentImpl.create(StreamTableEnvironmentImpl.java:110)
> at
> org.apache.flink.table.api.java.StreamTableEnvironment.create(StreamTableEnvironment.java:112)
> at
> org.apache.flink.table.examples.java.BlinkStreamSQL.main(BlinkStreamSQL.java:19)Caused
> by: org.apache.flink.table.api.NoMatchingTableFactoryException: Could not
> find a suitable table factory for
> 'org.apache.flink.table.delegation.ExecutorFactory' inthe classpath.
> {code}
> *But*, once I add blink planner dependency, it'll work well.
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[GitHub] [flink] flinkbot edited a comment on issue #9648: [FLINK-13872] [docs-zh] Translate Operations Playground to Chinese
flinkbot edited a comment on issue #9648: [FLINK-13872] [docs-zh] Translate Operations Playground to Chinese URL: https://github.com/apache/flink/pull/9648#issuecomment-529346361 ## CI report: * 6def0e035c5e7f442e45a00f1f7628726aef42eb : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/126406386) * 333097ea0e09e61f359eac193e94fb8b1ee588ef : CANCELED [Build](https://travis-ci.com/flink-ci/flink/builds/126544954) * 97eb081dbc374c19066b87406ed654c8f3b7665a : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/126546917) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Comment Edited] (FLINK-14037) Deserializing the input/output formats failed: unread block data
[
https://issues.apache.org/jira/browse/FLINK-14037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926317#comment-16926317
]
Zhu Zhu edited comment on FLINK-14037 at 9/10/19 4:16 AM:
--
Hi [~liupengcheng], the _flink-hadoop-compatibility_ artifact should be used by
your app in a compile scope so it is part of the user code and no need to be in
_flink-dis_t.
The root cause of this issue is that some user defined objects failed to be
deserialized, which may be caused by some class version mismatch. (I suspect
it's hadoop classes.)
Would you try deploying pre-bundled Hadoop jar
[e.g.|https://repo.maven.apache.org/maven2/org/apache/flink/flink-shaded-hadoop-2-uber/2.8.3-7.0/flink-shaded-hadoop-2-uber-2.8.3-7.0.jar]
to your flink-dist/lib to see if it solves your problem?
[Ref|https://flink.apache.org/downloads.html]
was (Author: zhuzh):
Hi [~liupengcheng], the _flink-hadoop-compatibility_ artifact should be used by
your app in a compile scope so it is part of the user code and no need to be in
_flink-dis_t.
The root cause of this issue is that some user defined objects failed to be
deserialized, which may be caused by some class version mismatch.
Would you try deploying pre-bundled Hadoop jar
[e.g.|https://repo.maven.apache.org/maven2/org/apache/flink/flink-shaded-hadoop-2-uber/2.8.3-7.0/flink-shaded-hadoop-2-uber-2.8.3-7.0.jar]
to your flink-dist/lib to see if it solves your problem?
[Ref|[https://flink.apache.org/downloads.html]]
> Deserializing the input/output formats failed: unread block data
>
>
> Key: FLINK-14037
> URL: https://issues.apache.org/jira/browse/FLINK-14037
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Task
>Affects Versions: 1.9.0
> Environment: flink 1.9.0
> app jar use `flink-shaded-hadoop-2` dependencies to avoid some confilicts
>
>Reporter: liupengcheng
>Priority: Major
>
> Recently, we encountered the following issue when testing flink 1.9.0:
> {code:java}
> org.apache.flink.client.program.ProgramInvocationException: Could not
> retrieve the execution result. (JobID: 8ffbc071dda81d6f8005c02be8adde6b)
> at
> org.apache.flink.client.program.rest.RestClusterClient.submitJob(RestClusterClient.java:255)
> at
> org.apache.flink.client.program.ClusterClient.run(ClusterClient.java:338)
> at
> org.apache.flink.client.program.ClusterClient.run(ClusterClient.java:326)
> at
> org.apache.flink.client.program.ContextEnvironment.execute(ContextEnvironment.java:62)
> at
> org.apache.flink.api.scala.ExecutionEnvironment.execute(ExecutionEnvironment.scala:539)
> at
> com.github.ehiggs.spark.terasort.FlinkTeraSort$.main(FlinkTeraSort.scala:89)
> at
> com.github.ehiggs.spark.terasort.FlinkTeraSort.main(FlinkTeraSort.scala)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.flink.client.program.PackagedProgram.callMainMethod(PackagedProgram.java:576)
> at
> org.apache.flink.client.program.PackagedProgram.invokeInteractiveModeForExecution(PackagedProgram.java:438)
> at
> org.apache.flink.client.program.ClusterClient.run(ClusterClient.java:274)
> at
> org.apache.flink.client.cli.CliFrontend.executeProgram(CliFrontend.java:746)
> at
> org.apache.flink.client.cli.CliFrontend.runProgram(CliFrontend.java:273)
> at org.apache.flink.client.cli.CliFrontend.run(CliFrontend.java:205)
> at
> org.apache.flink.client.cli.CliFrontend.parseParameters(CliFrontend.java:1010)
> at
> org.apache.flink.client.cli.CliFrontend.lambda$main$10(CliFrontend.java:1083)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1886)
> at
> org.apache.flink.runtime.security.HadoopSecurityContext.runSecured(HadoopSecurityContext.java:41)
> at org.apache.flink.client.cli.CliFrontend.main(CliFrontend.java:1083)
> Caused by: org.apache.flink.runtime.client.JobSubmissionException: Failed to
> submit JobGraph.
> at
> org.apache.flink.client.program.rest.RestClusterClient.lambda$submitJob$8(RestClusterClient.java:382)
> at
> java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:870)
> at
> java.util.concurrent.CompletableFuture$UniExceptionally.tryFire(CompletableFuture.java:852)
> at
> java.util.concurrent.Comple
[jira] [Commented] (FLINK-14037) Deserializing the input/output formats failed: unread block data
[
https://issues.apache.org/jira/browse/FLINK-14037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926317#comment-16926317
]
Zhu Zhu commented on FLINK-14037:
-
Hi [~liupengcheng], the _flink-hadoop-compatibility_ artifact should be used by
your app in a compile scope so it is part of the user code and no need to be in
_flink-dis_t.
The root cause of this issue is that some user defined objects failed to be
deserialized, which may be caused by some class version mismatch.
Would you try deploying pre-bundled Hadoop jar
[e.g.|https://repo.maven.apache.org/maven2/org/apache/flink/flink-shaded-hadoop-2-uber/2.8.3-7.0/flink-shaded-hadoop-2-uber-2.8.3-7.0.jar]
to your flink-dist/lib to see if it solves your problem?
[Ref|[https://flink.apache.org/downloads.html]]
> Deserializing the input/output formats failed: unread block data
>
>
> Key: FLINK-14037
> URL: https://issues.apache.org/jira/browse/FLINK-14037
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Task
>Affects Versions: 1.9.0
> Environment: flink 1.9.0
> app jar use `flink-shaded-hadoop-2` dependencies to avoid some confilicts
>
>Reporter: liupengcheng
>Priority: Major
>
> Recently, we encountered the following issue when testing flink 1.9.0:
> {code:java}
> org.apache.flink.client.program.ProgramInvocationException: Could not
> retrieve the execution result. (JobID: 8ffbc071dda81d6f8005c02be8adde6b)
> at
> org.apache.flink.client.program.rest.RestClusterClient.submitJob(RestClusterClient.java:255)
> at
> org.apache.flink.client.program.ClusterClient.run(ClusterClient.java:338)
> at
> org.apache.flink.client.program.ClusterClient.run(ClusterClient.java:326)
> at
> org.apache.flink.client.program.ContextEnvironment.execute(ContextEnvironment.java:62)
> at
> org.apache.flink.api.scala.ExecutionEnvironment.execute(ExecutionEnvironment.scala:539)
> at
> com.github.ehiggs.spark.terasort.FlinkTeraSort$.main(FlinkTeraSort.scala:89)
> at
> com.github.ehiggs.spark.terasort.FlinkTeraSort.main(FlinkTeraSort.scala)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.flink.client.program.PackagedProgram.callMainMethod(PackagedProgram.java:576)
> at
> org.apache.flink.client.program.PackagedProgram.invokeInteractiveModeForExecution(PackagedProgram.java:438)
> at
> org.apache.flink.client.program.ClusterClient.run(ClusterClient.java:274)
> at
> org.apache.flink.client.cli.CliFrontend.executeProgram(CliFrontend.java:746)
> at
> org.apache.flink.client.cli.CliFrontend.runProgram(CliFrontend.java:273)
> at org.apache.flink.client.cli.CliFrontend.run(CliFrontend.java:205)
> at
> org.apache.flink.client.cli.CliFrontend.parseParameters(CliFrontend.java:1010)
> at
> org.apache.flink.client.cli.CliFrontend.lambda$main$10(CliFrontend.java:1083)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1886)
> at
> org.apache.flink.runtime.security.HadoopSecurityContext.runSecured(HadoopSecurityContext.java:41)
> at org.apache.flink.client.cli.CliFrontend.main(CliFrontend.java:1083)
> Caused by: org.apache.flink.runtime.client.JobSubmissionException: Failed to
> submit JobGraph.
> at
> org.apache.flink.client.program.rest.RestClusterClient.lambda$submitJob$8(RestClusterClient.java:382)
> at
> java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:870)
> at
> java.util.concurrent.CompletableFuture$UniExceptionally.tryFire(CompletableFuture.java:852)
> at
> java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
> at
> java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977)
> at
> org.apache.flink.runtime.concurrent.FutureUtils.lambda$retryOperationWithDelay$8(FutureUtils.java:263)
> at
> java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:760)
> at
> java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:736)
> at
> java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
> at
> java.util.concurrent.CompletableFuture.postFire(CompletableFuture.java:561)
> at
> java.util.concurrent.CompletableFuture$UniCompose.t
[GitHub] [flink] flinkbot edited a comment on issue #9587: [FLINK-13685][yarn] Validate YARN deployment against YARN scheduler maximum vcore size
flinkbot edited a comment on issue #9587: [FLINK-13685][yarn] Validate YARN deployment against YARN scheduler maximum vcore size URL: https://github.com/apache/flink/pull/9587#issuecomment-526997659 ## CI report: * 667c738c79302b11cad210edbfb007866be29fdf : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/125383021) * 6198adda939d2fa12aeb3d1287b55e0c9412fafb : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/125498979) * 304769da1c49df00319b8c047259d5bfd961ef03 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/126537027) * 08d07d015e9d1daf990d83eaf2f4278bae2d504e : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/126539177) * 8cabaf4de3b4a16c154842a280fbf8eeb3f06fce : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/126550642) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (FLINK-13979) Translate new streamfilesink docs to chinese
[ https://issues.apache.org/jira/browse/FLINK-13979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926315#comment-16926315 ] rdyang commented on FLINK-13979: ok, thank you > Translate new streamfilesink docs to chinese > > > Key: FLINK-13979 > URL: https://issues.apache.org/jira/browse/FLINK-13979 > Project: Flink > Issue Type: New Feature > Components: chinese-translation, Documentation >Reporter: Gyula Fora >Assignee: rdyang >Priority: Major > > The StreamFileSink docs have been reworked as part of FLINK-13842 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[GitHub] [flink] flinkbot edited a comment on issue #9587: [FLINK-13685][yarn] Validate YARN deployment against YARN scheduler maximum vcore size
flinkbot edited a comment on issue #9587: [FLINK-13685][yarn] Validate YARN deployment against YARN scheduler maximum vcore size URL: https://github.com/apache/flink/pull/9587#issuecomment-526997659 ## CI report: * 667c738c79302b11cad210edbfb007866be29fdf : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/125383021) * 6198adda939d2fa12aeb3d1287b55e0c9412fafb : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/125498979) * 304769da1c49df00319b8c047259d5bfd961ef03 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/126537027) * 08d07d015e9d1daf990d83eaf2f4278bae2d504e : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/126539177) * 8cabaf4de3b4a16c154842a280fbf8eeb3f06fce : PENDING [Build](https://travis-ci.com/flink-ci/flink/builds/126550642) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9655: [FLINK-14017][python] Support to start up Python worker in process mode.
flinkbot edited a comment on issue #9655: [FLINK-14017][python] Support to start up Python worker in process mode. URL: https://github.com/apache/flink/pull/9655#issuecomment-529754597 ## CI report: * e02c8a291f5c82505750e200dda9b07d5e8b2fca : PENDING [Build](https://travis-ci.com/flink-ci/flink/builds/126550624) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9587: [FLINK-13685][yarn] Validate YARN deployment against YARN scheduler maximum vcore size
flinkbot edited a comment on issue #9587: [FLINK-13685][yarn] Validate YARN deployment against YARN scheduler maximum vcore size URL: https://github.com/apache/flink/pull/9587#issuecomment-526997659 ## CI report: * 667c738c79302b11cad210edbfb007866be29fdf : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/125383021) * 6198adda939d2fa12aeb3d1287b55e0c9412fafb : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/125498979) * 304769da1c49df00319b8c047259d5bfd961ef03 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/126537027) * 08d07d015e9d1daf990d83eaf2f4278bae2d504e : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/126539177) * 8cabaf4de3b4a16c154842a280fbf8eeb3f06fce : UNKNOWN This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9478: [FLINK-13766][task] Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext
flinkbot edited a comment on issue #9478: [FLINK-13766][task] Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext URL: https://github.com/apache/flink/pull/9478#issuecomment-522373234 Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community to review your pull request. We will use this comment to track the progress of the review. ## Automated Checks Last check on commit 52ec180a141ebc5d26519f8bc3ac4892ad054f8a (Tue Sep 10 03:36:35 UTC 2019) **Warnings:** * No documentation files were touched! Remember to keep the Flink docs up to date! Mention the bot in a comment to re-run the automated checks. ## Review Progress * ❓ 1. The [description] looks good. * ❓ 2. There is [consensus] that the contribution should go into to Flink. * ❓ 3. Needs [attention] from. * ❓ 4. The change fits into the overall [architecture]. * ❓ 5. Overall code [quality] is good. Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands The @flinkbot bot supports the following commands: - `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`) - `@flinkbot approve all` to approve all aspects - `@flinkbot approve-until architecture` to approve everything until `architecture` - `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention - `@flinkbot disapprove architecture` to remove an approval you gave earlier This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot commented on issue #9655: [FLINK-14017][python] Support to start up Python worker in process mode.
flinkbot commented on issue #9655: [FLINK-14017][python] Support to start up Python worker in process mode. URL: https://github.com/apache/flink/pull/9655#issuecomment-529754597 ## CI report: * e02c8a291f5c82505750e200dda9b07d5e8b2fca : UNKNOWN This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9653: [FLINK-14014][python] Introduce PythonScalarFunctionRunner to handle the communication with Python worker for Python ScalarFunction execution
flinkbot edited a comment on issue #9653: [FLINK-14014][python] Introduce PythonScalarFunctionRunner to handle the communication with Python worker for Python ScalarFunction execution URL: https://github.com/apache/flink/pull/9653#issuecomment-529525552 ## CI report: * 852555dbd31eb4e36009c99a22771a28544a0d5e : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/126471470) * 9b9156b15508efd40c5a8e5427a8cddb469913f9 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/126547856) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9654: [FLINK-13997][coordination] Remove legacy LeaderAddressAndId
flinkbot edited a comment on issue #9654: [FLINK-13997][coordination] Remove legacy LeaderAddressAndId URL: https://github.com/apache/flink/pull/9654#issuecomment-529732738 ## CI report: * c34ea9703f66f705323d8720d4fe2d1de0ee799a : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/126543893) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] zhijiangW commented on issue #9478: [FLINK-13766][task] Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext
zhijiangW commented on issue #9478: [FLINK-13766][task] Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext URL: https://github.com/apache/flink/pull/9478#issuecomment-529754407 Thanks for the review and good suggestions @1u0 ! I agree that `pull` seems more precise than `poll` as opposite to `push`, and I would submit a separate hotfix commit for renaming the previous class. Could you help point out the code formatting issue inline codes then I could double confirm easily. :) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot commented on issue #9655: [FLINK-14017][python] Support to start up Python worker in process mode.
flinkbot commented on issue #9655: [FLINK-14017][python] Support to start up Python worker in process mode. URL: https://github.com/apache/flink/pull/9655#issuecomment-529753707 Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community to review your pull request. We will use this comment to track the progress of the review. ## Automated Checks Last check on commit e02c8a291f5c82505750e200dda9b07d5e8b2fca (Tue Sep 10 03:31:07 UTC 2019) **Warnings:** * No documentation files were touched! Remember to keep the Flink docs up to date! Mention the bot in a comment to re-run the automated checks. ## Review Progress * ❓ 1. The [description] looks good. * ❓ 2. There is [consensus] that the contribution should go into to Flink. * ❓ 3. Needs [attention] from. * ❓ 4. The change fits into the overall [architecture]. * ❓ 5. Overall code [quality] is good. Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands The @flinkbot bot supports the following commands: - `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`) - `@flinkbot approve all` to approve all aspects - `@flinkbot approve-until architecture` to approve everything until `architecture` - `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention - `@flinkbot disapprove architecture` to remove an approval you gave earlier This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (FLINK-14017) Support to start up Python worker in process mode
[ https://issues.apache.org/jira/browse/FLINK-14017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated FLINK-14017: --- Labels: pull-request-available (was: ) > Support to start up Python worker in process mode > - > > Key: FLINK-14017 > URL: https://issues.apache.org/jira/browse/FLINK-14017 > Project: Flink > Issue Type: Sub-task > Components: API / Python >Reporter: Dian Fu >Assignee: Wei Zhong >Priority: Major > Labels: pull-request-available > Fix For: 1.10.0 > > > We employ Apache Beam's portability frameowork for the Python UDF execution. > However, there is only a golang implementation for the boot script to start > up SDK harness in Beam. It’s used by both the Python SDK harness and the Go > SDK harness. This is not a problem for Beam. However, it’s indeed a problem > for Flink as it indicates that the whole stack of Beam’s Go SDK harness will > be depended if we use the golang implementation of the boot script. We want > to avoid this by adding a Python boot script. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[GitHub] [flink] WeiZhong94 opened a new pull request #9655: [FLINK-14017][python] Support to start up Python worker in process mode.
WeiZhong94 opened a new pull request #9655: [FLINK-14017][python] Support to start up Python worker in process mode. URL: https://github.com/apache/flink/pull/9655 ## What is the purpose of the change *This pull request reimplements the apache-beam container script `boot.go` in python with some minor changes to support the beam python worker running in process mode and avoid introducing go-lang dependencies to Flink.* ## Brief change log - *Add `boot.py`, a python implementation of `boot.go` in "beam-sdks-python-container" project of Apache Beam for launching the python worker.* - *Different from `boot.go` of Apache Beam, `boot.py` supports specify the path of python executable file, and the default pip command is `python -m pip` instead of `/usr/local/bin/pip`.* - *Different from `boot.go` of Apache Beam, `boot.py` does not restrict the platform of user-specified apache beam sdk package to `linux`.* ## Verifying this change This change added tests and can be verified by running `flink/flink-python/pyflink/fn_execution/tests/test_process_mode_boot.py`. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (yes) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (no) - The serializers: (no) - The runtime per-record code paths (performance sensitive): (no) - Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no) - The S3 file system connector: (no) ## Documentation - Does this pull request introduce a new feature? (no) - If yes, how is the feature documented? (PythonDocs) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9587: [FLINK-13685][yarn] Validate YARN deployment against YARN scheduler maximum vcore size
flinkbot edited a comment on issue #9587: [FLINK-13685][yarn] Validate YARN deployment against YARN scheduler maximum vcore size URL: https://github.com/apache/flink/pull/9587#issuecomment-526995997 Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community to review your pull request. We will use this comment to track the progress of the review. ## Automated Checks Last check on commit 8cabaf4de3b4a16c154842a280fbf8eeb3f06fce (Tue Sep 10 03:29:28 UTC 2019) **Warnings:** * No documentation files were touched! Remember to keep the Flink docs up to date! Mention the bot in a comment to re-run the automated checks. ## Review Progress * ❓ 1. The [description] looks good. * ❓ 2. There is [consensus] that the contribution should go into to Flink. * ❓ 3. Needs [attention] from. * ❓ 4. The change fits into the overall [architecture]. * ❓ 5. Overall code [quality] is good. Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands The @flinkbot bot supports the following commands: - `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`) - `@flinkbot approve all` to approve all aspects - `@flinkbot approve-until architecture` to approve everything until `architecture` - `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention - `@flinkbot disapprove architecture` to remove an approval you gave earlier This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9478: [FLINK-13766][task] Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext
flinkbot edited a comment on issue #9478: [FLINK-13766][task] Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext URL: https://github.com/apache/flink/pull/9478#issuecomment-522373234 Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community to review your pull request. We will use this comment to track the progress of the review. ## Automated Checks Last check on commit 52ec180a141ebc5d26519f8bc3ac4892ad054f8a (Tue Sep 10 03:24:23 UTC 2019) **Warnings:** * No documentation files were touched! Remember to keep the Flink docs up to date! Mention the bot in a comment to re-run the automated checks. ## Review Progress * ❓ 1. The [description] looks good. * ❓ 2. There is [consensus] that the contribution should go into to Flink. * ❓ 3. Needs [attention] from. * ❓ 4. The change fits into the overall [architecture]. * ❓ 5. Overall code [quality] is good. Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands The @flinkbot bot supports the following commands: - `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`) - `@flinkbot approve all` to approve all aspects - `@flinkbot approve-until architecture` to approve everything until `architecture` - `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention - `@flinkbot disapprove architecture` to remove an approval you gave earlier This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9583: [hotfix][configuration] Remove usages of deprecated options TASK_MANAGER_HEAP_MEMORY_MB and JOB_MANAGER_HEAP_MEMORY_MB
flinkbot edited a comment on issue #9583: [hotfix][configuration] Remove usages of deprecated options TASK_MANAGER_HEAP_MEMORY_MB and JOB_MANAGER_HEAP_MEMORY_MB URL: https://github.com/apache/flink/pull/9583#issuecomment-526715510 ## CI report: * 6e904b5c61931e1cc84215ac297d1f3254b8 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/125277398) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] zhijiangW commented on a change in pull request #9478: [FLINK-13766][task] Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext
zhijiangW commented on a change in pull request #9478: [FLINK-13766][task]
Refactor the implementation of StreamInputProcessor based on
StreamTaskInput#emitNext
URL: https://github.com/apache/flink/pull/9478#discussion_r322537457
##
File path:
flink-streaming-java/src/main/java/org/apache/flink/streaming/runtime/streamstatus/StatusWatermarkValve.java
##
@@ -29,24 +30,13 @@
/**
* A {@code StatusWatermarkValve} embodies the logic of how {@link Watermark}
and {@link StreamStatus} are propagated to
* downstream outputs, given a set of one or multiple input channels that
continuously receive them. Usages of this
- * class need to define the number of input channels that the valve needs to
handle, as well as provide a customized
- * implementation of {@link ValveOutputHandler}, which is called by the valve
only when it determines a new watermark or
- * stream status can be propagated.
+ * class need to define the number of input channels that the valve needs to
handle, as well as provide a implementation of
+ * {@link DataOutput}, which is called by the valve only when it determines a
new watermark or stream status can be propagated.
*/
@Internal
public class StatusWatermarkValve {
- /**
-* Usages of {@code StatusWatermarkValve} should implement a {@code
ValveOutputHandler}
-* to handle watermark and stream status outputs from the valve.
-*/
- public interface ValveOutputHandler {
- void handleWatermark(Watermark watermark) throws Exception;
-
- void handleStreamStatus(StreamStatus streamStatus) throws
Exception;
- }
-
- private final ValveOutputHandler outputHandler;
+ private final DataOutput output;
Review comment:
Thanks for this concern. I actually also hesitated to this issue before and
passed the `output` in specific methods in `StatusWatermarkValve` instead of
constructor in previous version.
I think there are two different possibilities here:
- Make `StatusWatermarkValve` completely coupled with
`StreamTaskNetworkInput`, then we could even construct `StatusWatermarkValve`
inside constructor of `StreamTaskNetworkInput`. This is a positive point. And
we assume that the `output` is same for both `emitNext` and
`StatusWatermarkValve` now. But if the `output` instances are different in
future as you mentioned, then we need to pass another `output` into
`StreamTaskNetworkInput` for `StatusWatermarkValve`. Especially it would cause
many changes in `StatusWatermarkValve` because there are four internal methods
involved in passing `output` argument in `StatusWatermarkValve`.
- Construct the different `output` instances in the upper layer of
`StreamInputProcessor` for both `StreamTaskNetworkInput` and
`StatusWatermarkValve` as the current implementation in this PR. In other words
`StatusWatermarkValve` could be regarded as a `output` wrapper which is
actually used in `StatusWatermarkValve`, and the wrapped `output` inside
`StatusWatermarkValve` could be anything else different from the `output` in
`emitNext`. If it changes we only need to construct a different `output`
instance in `StreamInputProcessor` and pass it into `StatusWatermarkValve`, no
need to touch four internal methods inside it.
I have no obvious preference for above two ways, because we could think of
side effects for any way.
For the alternative of encapsulating `StatusWatermarkValve` behind `output`,
I wonder it is not good to let `output` see any channel index concept,
especially considering the source output future. And the current
`StatusWatermarkValve` is a bit heavy-weight, so encapsulating it into `output`
would complicate `output` implementation. In contrast, making `output` as an
field of `StatusWatermarkValve` seems more light-weight.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[jira] [Commented] (FLINK-14038) ExecutionGraph deploy failed due to akka timeout
[
https://issues.apache.org/jira/browse/FLINK-14038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926291#comment-16926291
]
Zhu Zhu commented on FLINK-14038:
-
Hi [~liupengcheng], would you check the TM GC log to see whether the TM was
stuck in GC when this error happens?
GC problem is the most common cause for late response from TM.
You can also increase the config "akka.ask.timeout" (by default it is 10 s) to
make the job more robust for late response cases.
> ExecutionGraph deploy failed due to akka timeout
>
>
> Key: FLINK-14038
> URL: https://issues.apache.org/jira/browse/FLINK-14038
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Task
>Affects Versions: 1.9.0
> Environment: Flink on yarn
> Flink 1.9.0
>Reporter: liupengcheng
>Priority: Major
>
> When launching the flink application, the following error was reported, I
> downloaded the operator logs, but still have no clue. The operator logs
> provided no useful information and was cancelled directly.
> JobManager logs:
> {code:java}
> java.lang.IllegalStateException: Update task on TaskManager
> container_e860_1567429198842_571077_01_06 @ zjy-hadoop-prc-st320.bj
> (dataPort=50990) failed due to:
> at
> org.apache.flink.runtime.executiongraph.Execution.lambda$sendUpdatePartitionInfoRpcCall$14(Execution.java:1395)
> at
> java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:760)
> at
> java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:736)
> at
> java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:442)
> at
> org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleRunAsync(AkkaRpcActor.java:397)
> at
> org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleRpcMessage(AkkaRpcActor.java:190)
> at
> org.apache.flink.runtime.rpc.akka.FencedAkkaRpcActor.handleRpcMessage(FencedAkkaRpcActor.java:74)
> at
> org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleMessage(AkkaRpcActor.java:152)
> at akka.japi.pf.UnitCaseStatement.apply(CaseStatements.scala:26)
> at akka.japi.pf.UnitCaseStatement.apply(CaseStatements.scala:21)
> at scala.PartialFunction$class.applyOrElse(PartialFunction.scala:123)
> at akka.japi.pf.UnitCaseStatement.applyOrElse(CaseStatements.scala:21)
> at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:170)
> at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:171)
> at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:171)
> at akka.actor.Actor$class.aroundReceive(Actor.scala:517)
> at akka.actor.AbstractActor.aroundReceive(AbstractActor.scala:225)
> at akka.actor.ActorCell.receiveMessage(ActorCell.scala:592)
> at akka.actor.ActorCell.invoke(ActorCell.scala:561)
> at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:258)
> at akka.dispatch.Mailbox.run(Mailbox.scala:225)
> at akka.dispatch.Mailbox.exec(Mailbox.scala:235)
> at akka.dispatch.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
> at
> akka.dispatch.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
> at akka.dispatch.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
> at
> akka.dispatch.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
> Caused by: java.util.concurrent.CompletionException:
> akka.pattern.AskTimeoutException: Ask timed out on
> [Actor[akka.tcp://fl...@zjy-hadoop-prc-st320.bj:62051/user/taskmanager_0#-171547157]]
> after [1 ms]. Message of type
> [org.apache.flink.runtime.rpc.messages.RemoteRpcInvocation]. A typical reason
> for `AskTimeoutException` is that the recipient actor didn't send a reply.
> at
> java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:292)
> at
> java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:308)
> at
> java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:593)
> at
> java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577)
> at
> java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
> at
> java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977)
> at
> org.apache.flink.runtime.concurrent.FutureUtils$1.onComplete(FutureUtils.java:871)
> at akka.dispatch.OnComplete.internal(Future.scala:263)
> at akka.dispatch.OnComplete.internal(Future.scala:261)
> at akka.dispatch.japi$CallbackBridge.apply(Future.scala:191)
> at akka.dispatch.japi$CallbackBridge.apply(Future.scala:188)
> at scala.concurrent.impl.CallbackRunnable.run(Promise.scala
[GitHub] [flink] flinkbot edited a comment on issue #9653: [FLINK-14014][python] Introduce PythonScalarFunctionRunner to handle the communication with Python worker for Python ScalarFunction execution
flinkbot edited a comment on issue #9653: [FLINK-14014][python] Introduce PythonScalarFunctionRunner to handle the communication with Python worker for Python ScalarFunction execution URL: https://github.com/apache/flink/pull/9653#issuecomment-529525552 ## CI report: * 852555dbd31eb4e36009c99a22771a28544a0d5e : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/126471470) * 9b9156b15508efd40c5a8e5427a8cddb469913f9 : PENDING [Build](https://travis-ci.com/flink-ci/flink/builds/126547856) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (FLINK-12749) Getting Started - Docker Playgrounds - Flink Cluster Playground
[
https://issues.apache.org/jira/browse/FLINK-12749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kurt Young updated FLINK-12749:
---
Fix Version/s: 1.9.1
1.8.2
> Getting Started - Docker Playgrounds - Flink Cluster Playground
> ---
>
> Key: FLINK-12749
> URL: https://issues.apache.org/jira/browse/FLINK-12749
> Project: Flink
> Issue Type: Sub-task
> Components: Documentation
>Reporter: Konstantin Knauf
>Assignee: Konstantin Knauf
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.2, 1.10.0, 1.9.1
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> The planned structure for the new Getting Started Guide is
> * Flink Overview (~ two pages)
> * Project Setup
> ** Java
> ** Scala
> ** Python
> * Quickstarts
> ** Example Walkthrough - Table API / SQL
> ** Example Walkthrough - DataStream API
> * Docker Playgrounds
> ** Flink Cluster Playground
> ** Flink Interactive SQL Playground
> In this ticket we add the Flink Cluster Playground, a docker-compose based
> setup consisting of Apache Kafka and Apache Flink (Flink Session Cluster),
> including a step-by-step guide for some common commands (job submission,
> savepoints, etc).
> *Some Open Questions:*
> * Which Flink images to use? `library/flink` with dynamic properties would be
> the most maintainable, I think. It would be preferable, if we don't need to
> host any custom images for this, but can rely on the existing plain Flink
> images.
> * Which Flink jobs to use? An updated version
> {{org.apache.flink.streaming.examples.statemachine.StateMachineExample}}
> might be a good option as it can with or without Kafka and contains a data
> generator writing to Kafka already (see next questions).
> * How to get data into Kafka? Maybe just provide a small bash
> script/one-liner to produce into Kafka topic or see question above.
> * Which Kafka Images to use? https://hub.docker.com/r/wurstmeister/kafka/
> seems to be well-maintained and is openly available.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (FLINK-13488) flink-python fails to build on Travis due to PackagesNotFoundError
[
https://issues.apache.org/jira/browse/FLINK-13488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kurt Young updated FLINK-13488:
---
Fix Version/s: (was: 1.8.2)
> flink-python fails to build on Travis due to PackagesNotFoundError
> --
>
> Key: FLINK-13488
> URL: https://issues.apache.org/jira/browse/FLINK-13488
> Project: Flink
> Issue Type: Bug
> Components: API / Python, Test Infrastructure
>Reporter: Tzu-Li (Gordon) Tai
>Assignee: sunjincheng
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.9.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> https://api.travis-ci.org/v3/job/564925115/log.txt
> {code}
> install conda ... [SUCCESS]
> install miniconda... [SUCCESS]
> installing python environment...
> installing python2.7...
> install python2.7... [SUCCESS]
> installing python3.3...
> PackagesNotFoundError: The following packages are not available from current
> channels:
> - python=3.3
> Current channels:
> - https://repo.anaconda.com/pkgs/main/linux-64
> - https://repo.anaconda.com/pkgs/main/noarch
> - https://repo.anaconda.com/pkgs/r/linux-64
> - https://repo.anaconda.com/pkgs/r/noarch
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Updated] (FLINK-13488) flink-python fails to build on Travis due to PackagesNotFoundError
[
https://issues.apache.org/jira/browse/FLINK-13488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kurt Young updated FLINK-13488:
---
Fix Version/s: 1.8.2
> flink-python fails to build on Travis due to PackagesNotFoundError
> --
>
> Key: FLINK-13488
> URL: https://issues.apache.org/jira/browse/FLINK-13488
> Project: Flink
> Issue Type: Bug
> Components: API / Python, Test Infrastructure
>Reporter: Tzu-Li (Gordon) Tai
>Assignee: sunjincheng
>Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.8.2, 1.9.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> https://api.travis-ci.org/v3/job/564925115/log.txt
> {code}
> install conda ... [SUCCESS]
> install miniconda... [SUCCESS]
> installing python environment...
> installing python2.7...
> install python2.7... [SUCCESS]
> installing python3.3...
> PackagesNotFoundError: The following packages are not available from current
> channels:
> - python=3.3
> Current channels:
> - https://repo.anaconda.com/pkgs/main/linux-64
> - https://repo.anaconda.com/pkgs/main/noarch
> - https://repo.anaconda.com/pkgs/r/linux-64
> - https://repo.anaconda.com/pkgs/r/noarch
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (FLINK-14038) ExecutionGraph deploy failed due to akka timeout
liupengcheng created FLINK-14038:
Summary: ExecutionGraph deploy failed due to akka timeout
Key: FLINK-14038
URL: https://issues.apache.org/jira/browse/FLINK-14038
Project: Flink
Issue Type: Bug
Components: Runtime / Task
Affects Versions: 1.9.0
Environment: Flink on yarn
Flink 1.9.0
Reporter: liupengcheng
When launching the flink application, the following error was reported, I
downloaded the operator logs, but still have no clue. The operator logs
provided no useful information and was cancelled directly.
JobManager logs:
{code:java}
java.lang.IllegalStateException: Update task on TaskManager
container_e860_1567429198842_571077_01_06 @ zjy-hadoop-prc-st320.bj
(dataPort=50990) failed due to:
at
org.apache.flink.runtime.executiongraph.Execution.lambda$sendUpdatePartitionInfoRpcCall$14(Execution.java:1395)
at
java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:760)
at
java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:736)
at
java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:442)
at
org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleRunAsync(AkkaRpcActor.java:397)
at
org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleRpcMessage(AkkaRpcActor.java:190)
at
org.apache.flink.runtime.rpc.akka.FencedAkkaRpcActor.handleRpcMessage(FencedAkkaRpcActor.java:74)
at
org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleMessage(AkkaRpcActor.java:152)
at akka.japi.pf.UnitCaseStatement.apply(CaseStatements.scala:26)
at akka.japi.pf.UnitCaseStatement.apply(CaseStatements.scala:21)
at scala.PartialFunction$class.applyOrElse(PartialFunction.scala:123)
at akka.japi.pf.UnitCaseStatement.applyOrElse(CaseStatements.scala:21)
at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:170)
at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:171)
at scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:171)
at akka.actor.Actor$class.aroundReceive(Actor.scala:517)
at akka.actor.AbstractActor.aroundReceive(AbstractActor.scala:225)
at akka.actor.ActorCell.receiveMessage(ActorCell.scala:592)
at akka.actor.ActorCell.invoke(ActorCell.scala:561)
at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:258)
at akka.dispatch.Mailbox.run(Mailbox.scala:225)
at akka.dispatch.Mailbox.exec(Mailbox.scala:235)
at akka.dispatch.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
at
akka.dispatch.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
at akka.dispatch.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
at
akka.dispatch.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
Caused by: java.util.concurrent.CompletionException:
akka.pattern.AskTimeoutException: Ask timed out on
[Actor[akka.tcp://fl...@zjy-hadoop-prc-st320.bj:62051/user/taskmanager_0#-171547157]]
after [1 ms]. Message of type
[org.apache.flink.runtime.rpc.messages.RemoteRpcInvocation]. A typical reason
for `AskTimeoutException` is that the recipient actor didn't send a reply.
at
java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:292)
at
java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:308)
at
java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:593)
at
java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577)
at
java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
at
java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977)
at
org.apache.flink.runtime.concurrent.FutureUtils$1.onComplete(FutureUtils.java:871)
at akka.dispatch.OnComplete.internal(Future.scala:263)
at akka.dispatch.OnComplete.internal(Future.scala:261)
at akka.dispatch.japi$CallbackBridge.apply(Future.scala:191)
at akka.dispatch.japi$CallbackBridge.apply(Future.scala:188)
at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:36)
at
org.apache.flink.runtime.concurrent.Executors$DirectExecutionContext.execute(Executors.java:74)
at
scala.concurrent.impl.CallbackRunnable.executeWithValue(Promise.scala:44)
at
scala.concurrent.impl.Promise$DefaultPromise.tryComplete(Promise.scala:252)
at
akka.pattern.PromiseActorRef$$anonfun$1.apply$mcV$sp(AskSupport.scala:644)
at akka.actor.Scheduler$$anon$4.run(Scheduler.scala:205)
at
scala.concurrent.Future$InternalCallbackExecutor$.unbatchedExecute(Future.scala:601)
at
scala.concurrent.BatchingExecutor$class.execute(BatchingExecutor.scala:
[jira] [Commented] (FLINK-13499) Remove dependency on MapR artifact repository
[ https://issues.apache.org/jira/browse/FLINK-13499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926280#comment-16926280 ] Kurt Young commented on FLINK-13499: also in 1.8: 80452f19e1712fd09d3b6b9a99c82d954f471a88 > Remove dependency on MapR artifact repository > - > > Key: FLINK-13499 > URL: https://issues.apache.org/jira/browse/FLINK-13499 > Project: Flink > Issue Type: Bug > Components: Build System >Affects Versions: 1.9.0 >Reporter: Stephan Ewen >Assignee: Stephan Ewen >Priority: Blocker > Labels: pull-request-available > Fix For: 1.8.2, 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The MapR artifact repository causes some problems. It does not reliably offer > a secure (https://) access. > We should change the MapR FS connector to work based on reflection and avoid > a hard dependency on any of the MapR vendor-specific artifacts. That should > allow us to get rid of the dependency without regressing on the support for > the file system. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (FLINK-13499) Remove dependency on MapR artifact repository
[ https://issues.apache.org/jira/browse/FLINK-13499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt Young updated FLINK-13499: --- Fix Version/s: 1.8.2 > Remove dependency on MapR artifact repository > - > > Key: FLINK-13499 > URL: https://issues.apache.org/jira/browse/FLINK-13499 > Project: Flink > Issue Type: Bug > Components: Build System >Affects Versions: 1.9.0 >Reporter: Stephan Ewen >Assignee: Stephan Ewen >Priority: Blocker > Labels: pull-request-available > Fix For: 1.8.2, 1.9.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The MapR artifact repository causes some problems. It does not reliably offer > a secure (https://) access. > We should change the MapR FS connector to work based on reflection and avoid > a hard dependency on any of the MapR vendor-specific artifacts. That should > allow us to get rid of the dependency without regressing on the support for > the file system. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Updated] (FLINK-9526) BucketingSink end-to-end test failed on Travis
[ https://issues.apache.org/jira/browse/FLINK-9526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kurt Young updated FLINK-9526: -- Fix Version/s: 1.8.2 > BucketingSink end-to-end test failed on Travis > -- > > Key: FLINK-9526 > URL: https://issues.apache.org/jira/browse/FLINK-9526 > Project: Flink > Issue Type: Bug > Components: Connectors / Common, Tests >Affects Versions: 1.6.0 >Reporter: Chesnay Schepler >Assignee: Biao Liu >Priority: Critical > Labels: pull-request-available, test-stability > Fix For: 1.8.2, 1.9.0 > > Attachments: image-2019-07-23-20-50-07-058.png > > Time Spent: 20m > Remaining Estimate: 0h > > https://travis-ci.org/zentol/flink-ci/builds/388130914 -- This message was sent by Atlassian Jira (v8.3.2#803003)
[GitHub] [flink] flinkbot edited a comment on issue #9653: [FLINK-14014][python] Introduce PythonScalarFunctionRunner to handle the communication with Python worker for Python ScalarFunction execution
flinkbot edited a comment on issue #9653: [FLINK-14014][python] Introduce PythonScalarFunctionRunner to handle the communication with Python worker for Python ScalarFunction execution URL: https://github.com/apache/flink/pull/9653#issuecomment-529525552 ## CI report: * 852555dbd31eb4e36009c99a22771a28544a0d5e : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/126471470) * 9b9156b15508efd40c5a8e5427a8cddb469913f9 : UNKNOWN This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9648: [FLINK-13872] [docs-zh] Translate Operations Playground to Chinese
flinkbot edited a comment on issue #9648: [FLINK-13872] [docs-zh] Translate Operations Playground to Chinese URL: https://github.com/apache/flink/pull/9648#issuecomment-529346361 ## CI report: * 6def0e035c5e7f442e45a00f1f7628726aef42eb : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/126406386) * 333097ea0e09e61f359eac193e94fb8b1ee588ef : CANCELED [Build](https://travis-ci.com/flink-ci/flink/builds/126544954) * 97eb081dbc374c19066b87406ed654c8f3b7665a : PENDING [Build](https://travis-ci.com/flink-ci/flink/builds/126546917) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (FLINK-14031) flink-examples-table should add the blink planner dependency
[
https://issues.apache.org/jira/browse/FLINK-14031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926276#comment-16926276
]
Jimmy Wong commented on FLINK-14031:
Hi [~Leonard Xu], Thanks you and I want to fix it by myself.
> flink-examples-table should add the blink planner dependency
>
>
> Key: FLINK-14031
> URL: https://issues.apache.org/jira/browse/FLINK-14031
> Project: Flink
> Issue Type: Bug
> Components: Examples
>Affects Versions: 1.9.0
>Reporter: Jimmy Wong
>Priority: Major
>
> The flink-examples-table module is missing blink planner dependency. If I run
> a blink example with Intellij IDEA, have error:
>
> {code:java}
> Exception in thread "main" org.apache.flink.table.api.TableException: Could
> not instantiate the executor. Make sure a planner module is on the
> classpathException in thread "main"
> org.apache.flink.table.api.TableException: Could not instantiate the
> executor. Make sure a planner module is on the classpath at
> org.apache.flink.table.api.java.internal.StreamTableEnvironmentImpl.lookupExecutor(StreamTableEnvironmentImpl.java:140)
> at
> org.apache.flink.table.api.java.internal.StreamTableEnvironmentImpl.create(StreamTableEnvironmentImpl.java:110)
> at
> org.apache.flink.table.api.java.StreamTableEnvironment.create(StreamTableEnvironment.java:112)
> at
> org.apache.flink.table.examples.java.BlinkStreamSQL.main(BlinkStreamSQL.java:19)Caused
> by: org.apache.flink.table.api.NoMatchingTableFactoryException: Could not
> find a suitable table factory for
> 'org.apache.flink.table.delegation.ExecutorFactory' inthe classpath.
> {code}
> *But*, once I add blink planner dependency, it'll work well.
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Issue Comment Deleted] (FLINK-14031) flink-examples-table should add the blink planner dependency
[
https://issues.apache.org/jira/browse/FLINK-14031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jimmy Wong updated FLINK-14031:
---
Comment: was deleted
(was: Hi, Leonard. Thanks you and I want to fix it by myself.)
> flink-examples-table should add the blink planner dependency
>
>
> Key: FLINK-14031
> URL: https://issues.apache.org/jira/browse/FLINK-14031
> Project: Flink
> Issue Type: Bug
> Components: Examples
>Affects Versions: 1.9.0
>Reporter: Jimmy Wong
>Priority: Major
>
> The flink-examples-table module is missing blink planner dependency. If I run
> a blink example with Intellij IDEA, have error:
>
> {code:java}
> Exception in thread "main" org.apache.flink.table.api.TableException: Could
> not instantiate the executor. Make sure a planner module is on the
> classpathException in thread "main"
> org.apache.flink.table.api.TableException: Could not instantiate the
> executor. Make sure a planner module is on the classpath at
> org.apache.flink.table.api.java.internal.StreamTableEnvironmentImpl.lookupExecutor(StreamTableEnvironmentImpl.java:140)
> at
> org.apache.flink.table.api.java.internal.StreamTableEnvironmentImpl.create(StreamTableEnvironmentImpl.java:110)
> at
> org.apache.flink.table.api.java.StreamTableEnvironment.create(StreamTableEnvironment.java:112)
> at
> org.apache.flink.table.examples.java.BlinkStreamSQL.main(BlinkStreamSQL.java:19)Caused
> by: org.apache.flink.table.api.NoMatchingTableFactoryException: Could not
> find a suitable table factory for
> 'org.apache.flink.table.delegation.ExecutorFactory' inthe classpath.
> {code}
> *But*, once I add blink planner dependency, it'll work well.
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[GitHub] [flink] flinkbot edited a comment on issue #9648: [FLINK-13872] [docs-zh] Translate Operations Playground to Chinese
flinkbot edited a comment on issue #9648: [FLINK-13872] [docs-zh] Translate Operations Playground to Chinese URL: https://github.com/apache/flink/pull/9648#issuecomment-529346361 ## CI report: * 6def0e035c5e7f442e45a00f1f7628726aef42eb : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/126406386) * 333097ea0e09e61f359eac193e94fb8b1ee588ef : PENDING [Build](https://travis-ci.com/flink-ci/flink/builds/126544954) * 97eb081dbc374c19066b87406ed654c8f3b7665a : UNKNOWN This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9478: [FLINK-13766][task] Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext
flinkbot edited a comment on issue #9478: [FLINK-13766][task] Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext URL: https://github.com/apache/flink/pull/9478#issuecomment-522373234 Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community to review your pull request. We will use this comment to track the progress of the review. ## Automated Checks Last check on commit 52ec180a141ebc5d26519f8bc3ac4892ad054f8a (Tue Sep 10 02:32:28 UTC 2019) **Warnings:** * No documentation files were touched! Remember to keep the Flink docs up to date! Mention the bot in a comment to re-run the automated checks. ## Review Progress * ❓ 1. The [description] looks good. * ❓ 2. There is [consensus] that the contribution should go into to Flink. * ❓ 3. Needs [attention] from. * ❓ 4. The change fits into the overall [architecture]. * ❓ 5. Overall code [quality] is good. Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands The @flinkbot bot supports the following commands: - `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`) - `@flinkbot approve all` to approve all aspects - `@flinkbot approve-until architecture` to approve everything until `architecture` - `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention - `@flinkbot disapprove architecture` to remove an approval you gave earlier This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] zhijiangW commented on a change in pull request #9478: [FLINK-13766][task] Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext
zhijiangW commented on a change in pull request #9478: [FLINK-13766][task]
Refactor the implementation of StreamInputProcessor based on
StreamTaskInput#emitNext
URL: https://github.com/apache/flink/pull/9478#discussion_r322529299
##
File path:
flink-streaming-java/src/main/java/org/apache/flink/streaming/runtime/io/StreamTwoInputProcessor.java
##
@@ -171,30 +193,23 @@ public boolean processInput() throws Exception {
}
lastReadInputIndex = readingInputIndex;
- StreamElement recordOrMark;
+ InputStatus status;
if (readingInputIndex == 0) {
- recordOrMark = input1.pollNextNullable();
- if (recordOrMark != null) {
- processElement1(recordOrMark,
input1.getLastChannel());
- }
- checkFinished(input1, lastReadInputIndex);
+ status = input1.emitNext(output1);
} else {
- recordOrMark = input2.pollNextNullable();
- if (recordOrMark != null) {
- processElement2(recordOrMark,
input2.getLastChannel());
- }
- checkFinished(input2, lastReadInputIndex);
+ status = input2.emitNext(output2);
}
+ checkFinished(status, lastReadInputIndex);
- if (recordOrMark == null) {
+ if (status != InputStatus.MORE_AVAILABLE) {
inputSelectionHandler.setUnavailableInput(readingInputIndex);
}
- return recordOrMark != null;
+ return status == InputStatus.MORE_AVAILABLE;
}
- private void checkFinished(StreamTaskInput input, int inputIndex)
throws Exception {
- if (input.isFinished()) {
+ private void checkFinished(InputStatus status, int inputIndex) throws
Exception {
+ if (status == InputStatus.END_OF_INPUT) {
Review comment:
Actually I did that in first version to rename the `checkFinished` as
`checkStatus` which also covers the
```
if (status != InputStatus.MORE_AVAILABLE) {
inputSelectionHandler.setUnavailableInput(readingInputIndex);
}
```
But in #9483 I integrated the above `if (status !=
InputStatus.MORE_AVAILABLE)` with other processes. So in this PR I kept the
previous way to avoid repeated changes. :)
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[jira] [Commented] (FLINK-14036) function log(f0,f1) in Table API do not support decimal type
[
https://issues.apache.org/jira/browse/FLINK-14036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926269#comment-16926269
]
Jingsong Lee commented on FLINK-14036:
--
Thanks [~Leonard Xu] for report this.
Now *org.apache.flink.table.planner.typeutils.TypeCoercion* can cast Decimal
type to Double type. I think the reason is that table api is more strict than
sql. You can see detail in org.apache.flink.table.planner.expressions.Log, it
require double expectedTypes.
> function log(f0,f1) in Table API do not support decimal type
> ---
>
> Key: FLINK-14036
> URL: https://issues.apache.org/jira/browse/FLINK-14036
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / API, Table SQL / Planner
>Affects Versions: 1.9.0
>Reporter: Leonard Xu
>Priority: Major
> Fix For: 1.10.0
>
>
> function log(f0,f1) in Table API module do not support decimal type, but it
> works in Table SQL module. The following code will run fail:
>
> {code:java}
> testTableApi(
> 'f0.log(f1),
> "log(f0,f1)",
> "2.0")
> override def testData: Row = {
> val testData = new Row(2)
> testData.setField(0, BigDecimal("3").bigDecimal)
> testData.setField(1, 9)
> testData
> }
>
> override def typeInfo: RowTypeInfo = {
> new RowTypeInfo(
> /* 0 */ fromLogicalTypeToTypeInfo(DECIMAL(1, 0)),
> /* 1 */ Types.INT
> )
> }{code}
>
> The real cause is that the return type of *log()* function must be Double
> type，planner will cast all oprands' type to Double Type before function
> execution, however *org.apache.flink.table.planner.typeutils.TypeCoercion*
> can not yet cast Decimal type to Double type。
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (FLINK-14031) flink-examples-table should add the blink planner dependency
[
https://issues.apache.org/jira/browse/FLINK-14031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926268#comment-16926268
]
Jimmy Wong commented on FLINK-14031:
Hi, Leonard. Thanks you and I want to fix it by myself.
> flink-examples-table should add the blink planner dependency
>
>
> Key: FLINK-14031
> URL: https://issues.apache.org/jira/browse/FLINK-14031
> Project: Flink
> Issue Type: Bug
> Components: Examples
>Affects Versions: 1.9.0
>Reporter: Jimmy Wong
>Priority: Major
>
> The flink-examples-table module is missing blink planner dependency. If I run
> a blink example with Intellij IDEA, have error:
>
> {code:java}
> Exception in thread "main" org.apache.flink.table.api.TableException: Could
> not instantiate the executor. Make sure a planner module is on the
> classpathException in thread "main"
> org.apache.flink.table.api.TableException: Could not instantiate the
> executor. Make sure a planner module is on the classpath at
> org.apache.flink.table.api.java.internal.StreamTableEnvironmentImpl.lookupExecutor(StreamTableEnvironmentImpl.java:140)
> at
> org.apache.flink.table.api.java.internal.StreamTableEnvironmentImpl.create(StreamTableEnvironmentImpl.java:110)
> at
> org.apache.flink.table.api.java.StreamTableEnvironment.create(StreamTableEnvironment.java:112)
> at
> org.apache.flink.table.examples.java.BlinkStreamSQL.main(BlinkStreamSQL.java:19)Caused
> by: org.apache.flink.table.api.NoMatchingTableFactoryException: Could not
> find a suitable table factory for
> 'org.apache.flink.table.delegation.ExecutorFactory' inthe classpath.
> {code}
> *But*, once I add blink planner dependency, it'll work well.
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Created] (FLINK-14037) Deserializing the input/output formats failed: unread block data
liupengcheng created FLINK-14037:
Summary: Deserializing the input/output formats failed: unread
block data
Key: FLINK-14037
URL: https://issues.apache.org/jira/browse/FLINK-14037
Project: Flink
Issue Type: Bug
Components: Runtime / Task
Affects Versions: 1.9.0
Environment: flink 1.9.0
app jar use `flink-shaded-hadoop-2` dependencies to avoid some confilicts
Reporter: liupengcheng
Recently, we encountered the following issue when testing flink 1.9.0:
{code:java}
org.apache.flink.client.program.ProgramInvocationException: Could not retrieve
the execution result. (JobID: 8ffbc071dda81d6f8005c02be8adde6b)
at
org.apache.flink.client.program.rest.RestClusterClient.submitJob(RestClusterClient.java:255)
at
org.apache.flink.client.program.ClusterClient.run(ClusterClient.java:338)
at
org.apache.flink.client.program.ClusterClient.run(ClusterClient.java:326)
at
org.apache.flink.client.program.ContextEnvironment.execute(ContextEnvironment.java:62)
at
org.apache.flink.api.scala.ExecutionEnvironment.execute(ExecutionEnvironment.scala:539)
at
com.github.ehiggs.spark.terasort.FlinkTeraSort$.main(FlinkTeraSort.scala:89)
at
com.github.ehiggs.spark.terasort.FlinkTeraSort.main(FlinkTeraSort.scala)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.flink.client.program.PackagedProgram.callMainMethod(PackagedProgram.java:576)
at
org.apache.flink.client.program.PackagedProgram.invokeInteractiveModeForExecution(PackagedProgram.java:438)
at
org.apache.flink.client.program.ClusterClient.run(ClusterClient.java:274)
at
org.apache.flink.client.cli.CliFrontend.executeProgram(CliFrontend.java:746)
at
org.apache.flink.client.cli.CliFrontend.runProgram(CliFrontend.java:273)
at org.apache.flink.client.cli.CliFrontend.run(CliFrontend.java:205)
at
org.apache.flink.client.cli.CliFrontend.parseParameters(CliFrontend.java:1010)
at
org.apache.flink.client.cli.CliFrontend.lambda$main$10(CliFrontend.java:1083)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1886)
at
org.apache.flink.runtime.security.HadoopSecurityContext.runSecured(HadoopSecurityContext.java:41)
at org.apache.flink.client.cli.CliFrontend.main(CliFrontend.java:1083)
Caused by: org.apache.flink.runtime.client.JobSubmissionException: Failed to
submit JobGraph.
at
org.apache.flink.client.program.rest.RestClusterClient.lambda$submitJob$8(RestClusterClient.java:382)
at
java.util.concurrent.CompletableFuture.uniExceptionally(CompletableFuture.java:870)
at
java.util.concurrent.CompletableFuture$UniExceptionally.tryFire(CompletableFuture.java:852)
at
java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
at
java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977)
at
org.apache.flink.runtime.concurrent.FutureUtils.lambda$retryOperationWithDelay$8(FutureUtils.java:263)
at
java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:760)
at
java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:736)
at
java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
at
java.util.concurrent.CompletableFuture.postFire(CompletableFuture.java:561)
at
java.util.concurrent.CompletableFuture$UniCompose.tryFire(CompletableFuture.java:929)
at
java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:442)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.flink.runtime.rest.util.RestClientException: [Internal
server error., (JobManagerRunner.java:152)
at
org.apache.flink.runtime.dispatcher.DefaultJobManagerRunnerFactory.createJobManagerRunner(DefaultJobManagerRunnerFactory.java:83)
at
org.apache.flink.runtime.dispatcher.Dispatcher.lambda$createJobManagerRunner$5(Dispatcher.java:375)
at
org.apache.flink.util.function.CheckedSupplier.lambda$unchecked$0(CheckedSupplier.java:34)
... 7 more
Caused by: org.apache.flink.runtime.client.JobExecutionException: Cannot
initialize task 'Dat
[GitHub] [flink] flinkbot edited a comment on issue #9478: [FLINK-13766][task] Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext
flinkbot edited a comment on issue #9478: [FLINK-13766][task] Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext URL: https://github.com/apache/flink/pull/9478#issuecomment-522373234 Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community to review your pull request. We will use this comment to track the progress of the review. ## Automated Checks Last check on commit 52ec180a141ebc5d26519f8bc3ac4892ad054f8a (Tue Sep 10 02:21:15 UTC 2019) **Warnings:** * No documentation files were touched! Remember to keep the Flink docs up to date! Mention the bot in a comment to re-run the automated checks. ## Review Progress * ❓ 1. The [description] looks good. * ❓ 2. There is [consensus] that the contribution should go into to Flink. * ❓ 3. Needs [attention] from. * ❓ 4. The change fits into the overall [architecture]. * ❓ 5. Overall code [quality] is good. Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands The @flinkbot bot supports the following commands: - `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`) - `@flinkbot approve all` to approve all aspects - `@flinkbot approve-until architecture` to approve everything until `architecture` - `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention - `@flinkbot disapprove architecture` to remove an approval you gave earlier This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (FLINK-14036) function log(f0,f1) in Table API do not support decimal type
[
https://issues.apache.org/jira/browse/FLINK-14036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonard Xu updated FLINK-14036:
---
Fix Version/s: (was: 2.0.0)
1.10.0
> function log(f0,f1) in Table API do not support decimal type
> ---
>
> Key: FLINK-14036
> URL: https://issues.apache.org/jira/browse/FLINK-14036
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / API, Table SQL / Planner
>Affects Versions: 1.9.0
>Reporter: Leonard Xu
>Priority: Major
> Fix For: 1.10.0
>
>
> function log(f0,f1) in Table API module do not support decimal type, but it
> works in Table SQL module. The following code will run fail:
>
> {code:java}
> testTableApi(
> 'f0.log(f1),
> "log(f0,f1)",
> "2.0")
> override def testData: Row = {
> val testData = new Row(2)
> testData.setField(0, BigDecimal("3").bigDecimal)
> testData.setField(1, 9)
> testData
> }
>
> override def typeInfo: RowTypeInfo = {
> new RowTypeInfo(
> /* 0 */ fromLogicalTypeToTypeInfo(DECIMAL(1, 0)),
> /* 1 */ Types.INT
> )
> }{code}
>
> The real cause is that the return type of *log()* function must be Double
> type，planner will cast all oprands' type to Double Type before function
> execution, however *org.apache.flink.table.planner.typeutils.TypeCoercion*
> can not yet cast Decimal type to Double type。
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[GitHub] [flink] zhijiangW commented on a change in pull request #9478: [FLINK-13766][task] Refactor the implementation of StreamInputProcessor based on StreamTaskInput#emitNext
zhijiangW commented on a change in pull request #9478: [FLINK-13766][task]
Refactor the implementation of StreamInputProcessor based on
StreamTaskInput#emitNext
URL: https://github.com/apache/flink/pull/9478#discussion_r322527758
##
File path:
flink-streaming-java/src/main/java/org/apache/flink/streaming/runtime/io/StreamTaskNetworkInput.java
##
@@ -111,7 +127,8 @@ public StreamElement pollNextNullable() throws Exception {
}
if (result.isFullRecord()) {
- return
deserializationDelegate.getInstance();
+
processElement(deserializationDelegate.getInstance(), output);
Review comment:
It should never be null because of above condition of
`result.isFullRecord()`.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9648: [FLINK-13872] [docs-zh] Translate Operations Playground to Chinese
flinkbot edited a comment on issue #9648: [FLINK-13872] [docs-zh] Translate Operations Playground to Chinese URL: https://github.com/apache/flink/pull/9648#issuecomment-529343948 Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community to review your pull request. We will use this comment to track the progress of the review. ## Automated Checks Last check on commit 97eb081dbc374c19066b87406ed654c8f3b7665a (Tue Sep 10 02:17:12 UTC 2019) ✅no warnings Mention the bot in a comment to re-run the automated checks. ## Review Progress * ❓ 1. The [description] looks good. * ❓ 2. There is [consensus] that the contribution should go into to Flink. * ❓ 3. Needs [attention] from. * ❓ 4. The change fits into the overall [architecture]. * ❓ 5. Overall code [quality] is good. Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands The @flinkbot bot supports the following commands: - `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`) - `@flinkbot approve all` to approve all aspects - `@flinkbot approve-until architecture` to approve everything until `architecture` - `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention - `@flinkbot disapprove architecture` to remove an approval you gave earlier This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (FLINK-13682) Translate "Code Style - Scala Guide" page into Chinese
[ https://issues.apache.org/jira/browse/FLINK-13682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926263#comment-16926263 ] gaofeilong commented on FLINK-13682: I can do this, would mind to assign this issue to me? [~jark] > Translate "Code Style - Scala Guide" page into Chinese > -- > > Key: FLINK-13682 > URL: https://issues.apache.org/jira/browse/FLINK-13682 > Project: Flink > Issue Type: Sub-task > Components: chinese-translation, Project Website >Reporter: Jark Wu >Priority: Major > > Translate page > https://flink.apache.org/zh/contributing/code-style-and-quality-scala.html > into Chinese. The page is located in > https://github.com/apache/flink-web/blob/asf-site/contributing/code-style-and-quality-scala.zh.md. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[GitHub] [flink] flinkbot edited a comment on issue #9648: [FLINK-13872] [docs-zh] Translate Operations Playground to Chinese
flinkbot edited a comment on issue #9648: [FLINK-13872] [docs-zh] Translate Operations Playground to Chinese URL: https://github.com/apache/flink/pull/9648#issuecomment-529346361 ## CI report: * 6def0e035c5e7f442e45a00f1f7628726aef42eb : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/126406386) * 333097ea0e09e61f359eac193e94fb8b1ee588ef : PENDING [Build](https://travis-ci.com/flink-ci/flink/builds/126544954) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (FLINK-13680) Translate "Code Style - Common Rules" page into Chinese
[ https://issues.apache.org/jira/browse/FLINK-13680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926262#comment-16926262 ] gaofeilong commented on FLINK-13680: I can do this, would mind to assign this issue to me? [~jark] > Translate "Code Style - Common Rules" page into Chinese > --- > > Key: FLINK-13680 > URL: https://issues.apache.org/jira/browse/FLINK-13680 > Project: Flink > Issue Type: Sub-task > Components: chinese-translation, Project Website >Reporter: Jark Wu >Priority: Major > > Translate page > https://flink.apache.org/zh/contributing/code-style-and-quality-common.html > into Chinese. The page is located in > https://github.com/apache/flink-web/blob/asf-site/contributing/code-style-and-quality-common.zh.md. -- This message was sent by Atlassian Jira (v8.3.2#803003)
[jira] [Created] (FLINK-14036) function log(f0,f1) in Table API do not support decimal type
Leonard Xu created FLINK-14036:
--
Summary: function log(f0,f1) in Table API do not support decimal
type
Key: FLINK-14036
URL: https://issues.apache.org/jira/browse/FLINK-14036
Project: Flink
Issue Type: Bug
Components: Table SQL / API, Table SQL / Planner
Affects Versions: 1.9.0
Reporter: Leonard Xu
Fix For: 2.0.0
function log(f0,f1) in Table API module do not support decimal type, but it
works in Table SQL module. The following code will run fail:
{code:java}
testTableApi(
'f0.log(f1),
"log(f0,f1)",
"2.0")
override def testData: Row = {
val testData = new Row(2)
testData.setField(0, BigDecimal("3").bigDecimal)
testData.setField(1, 9)
testData
}
override def typeInfo: RowTypeInfo = {
new RowTypeInfo(
/* 0 */ fromLogicalTypeToTypeInfo(DECIMAL(1, 0)),
/* 1 */ Types.INT
)
}{code}
The real cause is that the return type of *log()* function must be Double
type，planner will cast all oprands' type to Double Type before function
execution, however *org.apache.flink.table.planner.typeutils.TypeCoercion* can
not yet cast Decimal type to Double type。
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[GitHub] [flink] flinkbot edited a comment on issue #9587: [FLINK-13685][yarn] Validate YARN deployment against YARN scheduler maximum vcore size
flinkbot edited a comment on issue #9587: [FLINK-13685][yarn] Validate YARN deployment against YARN scheduler maximum vcore size URL: https://github.com/apache/flink/pull/9587#issuecomment-526997659 ## CI report: * 667c738c79302b11cad210edbfb007866be29fdf : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/125383021) * 6198adda939d2fa12aeb3d1287b55e0c9412fafb : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/125498979) * 304769da1c49df00319b8c047259d5bfd961ef03 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/126537027) * 08d07d015e9d1daf990d83eaf2f4278bae2d504e : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/126539177) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9654: [FLINK-13997][coordination] Remove legacy LeaderAddressAndId
flinkbot edited a comment on issue #9654: [FLINK-13997][coordination] Remove legacy LeaderAddressAndId URL: https://github.com/apache/flink/pull/9654#issuecomment-529732738 ## CI report: * c34ea9703f66f705323d8720d4fe2d1de0ee799a : PENDING [Build](https://travis-ci.com/flink-ci/flink/builds/126543893) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9648: [FLINK-13872] [docs-zh] Translate Operations Playground to Chinese
flinkbot edited a comment on issue #9648: [FLINK-13872] [docs-zh] Translate Operations Playground to Chinese URL: https://github.com/apache/flink/pull/9648#issuecomment-529346361 ## CI report: * 6def0e035c5e7f442e45a00f1f7628726aef42eb : SUCCESS [Build](https://travis-ci.com/flink-ci/flink/builds/126406386) * 333097ea0e09e61f359eac193e94fb8b1ee588ef : UNKNOWN This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9643: [FLINK-13961][client] Remove obsolete abstraction JobExecutor(Service)
flinkbot edited a comment on issue #9643: [FLINK-13961][client] Remove obsolete abstraction JobExecutor(Service) URL: https://github.com/apache/flink/pull/9643#issuecomment-528868823 ## CI report: * 0f85333e5d275aedc4560241bf9a268d887bb5e7 : FAILURE [Build](https://travis-ci.com/flink-ci/flink/builds/126235520) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9645: [FLINK-12584][connectors]Add Bucket File Syetem Table Sink
flinkbot edited a comment on issue #9645: [FLINK-12584][connectors]Add Bucket File Syetem Table Sink URL: https://github.com/apache/flink/pull/9645#issuecomment-529174106 Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community to review your pull request. We will use this comment to track the progress of the review. ## Automated Checks Last check on commit d7c56060a8dd37190f70e2bef40cf37d013c7a59 (Tue Sep 10 01:59:52 UTC 2019) **Warnings:** * **5 pom.xml files were touched**: Check for build and licensing issues. Mention the bot in a comment to re-run the automated checks. ## Review Progress * ❓ 1. The [description] looks good. * ❓ 2. There is [consensus] that the contribution should go into to Flink. * ❓ 3. Needs [attention] from. * ❓ 4. The change fits into the overall [architecture]. * ❓ 5. Overall code [quality] is good. Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands The @flinkbot bot supports the following commands: - `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`) - `@flinkbot approve all` to approve all aspects - `@flinkbot approve-until architecture` to approve everything until `architecture` - `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention - `@flinkbot disapprove architecture` to remove an approval you gave earlier This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] zhangjun888 commented on issue #9645: [FLINK-12584][connectors]Add Bucket File Syetem Table Sink
zhangjun888 commented on issue #9645: [FLINK-12584][connectors]Add Bucket File Syetem Table Sink URL: https://github.com/apache/flink/pull/9645#issuecomment-529735497 cc: @fhueske @twalthr thanks This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Resolved] (FLINK-13444) Translate English content of FLINK-13396 into Chinese
[
https://issues.apache.org/jira/browse/FLINK-13444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jark Wu resolved FLINK-13444.
-
Fix Version/s: 1.10.0
Resolution: Fixed
1.10.0: 6db11d05b5cb466692546d4eba7e93df3596c2d0
> Translate English content of FLINK-13396 into Chinese
> -
>
> Key: FLINK-13444
> URL: https://issues.apache.org/jira/browse/FLINK-13444
> Project: Flink
> Issue Type: Sub-task
> Components: chinese-translation, Documentation
>Reporter: Jark Wu
>Assignee: Ke Li
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Translate new added English content of FLINK-13396 to Chinese.
> The markdown file is located in {{docs/dev/connectors/filesystem_sink.zh.md}}.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[GitHub] [flink] flinkbot edited a comment on issue #9648: [FLINK-13872] [docs-zh] Translate Operations Playground to Chinese
flinkbot edited a comment on issue #9648: [FLINK-13872] [docs-zh] Translate Operations Playground to Chinese URL: https://github.com/apache/flink/pull/9648#issuecomment-529343948 Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community to review your pull request. We will use this comment to track the progress of the review. ## Automated Checks Last check on commit 333097ea0e09e61f359eac193e94fb8b1ee588ef (Tue Sep 10 01:55:48 UTC 2019) ✅no warnings Mention the bot in a comment to re-run the automated checks. ## Review Progress * ❓ 1. The [description] looks good. * ❓ 2. There is [consensus] that the contribution should go into to Flink. * ❓ 3. Needs [attention] from. * ❓ 4. The change fits into the overall [architecture]. * ❓ 5. Overall code [quality] is good. Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands The @flinkbot bot supports the following commands: - `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`) - `@flinkbot approve all` to approve all aspects - `@flinkbot approve-until architecture` to approve everything until `architecture` - `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention - `@flinkbot disapprove architecture` to remove an approval you gave earlier This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9420: [FLINK-13444][doc] Add BucketingSink deprecation note in Chinese doc
flinkbot edited a comment on issue #9420: [FLINK-13444][doc] Add BucketingSink deprecation note in Chinese doc URL: https://github.com/apache/flink/pull/9420#issuecomment-520398306 Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community to review your pull request. We will use this comment to track the progress of the review. ## Automated Checks Last check on commit bd7d3b7b96f659c18fff2d18cccdedec3e0789f6 (Tue Sep 10 01:55:52 UTC 2019) ✅no warnings Mention the bot in a comment to re-run the automated checks. ## Review Progress * ❓ 1. The [description] looks good. * ❓ 2. There is [consensus] that the contribution should go into to Flink. * ❓ 3. Needs [attention] from. * ❓ 4. The change fits into the overall [architecture]. * ❓ 5. Overall code [quality] is good. Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands The @flinkbot bot supports the following commands: - `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`) - `@flinkbot approve all` to approve all aspects - `@flinkbot approve-until architecture` to approve everything until `architecture` - `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention - `@flinkbot disapprove architecture` to remove an approval you gave earlier This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] wuchong commented on issue #9420: [FLINK-13444][doc] Add BucketingSink deprecation note in Chinese doc
wuchong commented on issue #9420: [FLINK-13444][doc] Add BucketingSink deprecation note in Chinese doc URL: https://github.com/apache/flink/pull/9420#issuecomment-529734792 Thanks @liketic for the translation . I have merged this PR. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] asfgit closed pull request #9420: [FLINK-13444][doc] Add BucketingSink deprecation note in Chinese doc
asfgit closed pull request #9420: [FLINK-13444][doc] Add BucketingSink deprecation note in Chinese doc URL: https://github.com/apache/flink/pull/9420 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] wuchong commented on issue #9648: [FLINK-13872] [docs-zh] Translate Operations Playground to Chinese
wuchong commented on issue #9648: [FLINK-13872] [docs-zh] Translate Operations Playground to Chinese URL: https://github.com/apache/flink/pull/9648#issuecomment-529734544 Thanks @lord-i-will for the updating. I will review this. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9606: [FLINK-13677][docs-zh] Translate "Monitoring Back Pressure" page into Chinese
flinkbot edited a comment on issue #9606: [FLINK-13677][docs-zh] Translate "Monitoring Back Pressure" page into Chinese URL: https://github.com/apache/flink/pull/9606#issuecomment-527738237 Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community to review your pull request. We will use this comment to track the progress of the review. ## Automated Checks Last check on commit 4965f91617e3c220a2cb3e422dc783a443d5a228 (Tue Sep 10 01:49:40 UTC 2019) ✅no warnings Mention the bot in a comment to re-run the automated checks. ## Review Progress * ❓ 1. The [description] looks good. * ❓ 2. There is [consensus] that the contribution should go into to Flink. * ❓ 3. Needs [attention] from. * ❓ 4. The change fits into the overall [architecture]. * ❓ 5. Overall code [quality] is good. Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands The @flinkbot bot supports the following commands: - `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`) - `@flinkbot approve all` to approve all aspects - `@flinkbot approve-until architecture` to approve everything until `architecture` - `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention - `@flinkbot disapprove architecture` to remove an approval you gave earlier This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Resolved] (FLINK-13677) Translate "Monitoring Back Pressure" page into Chinese
[ https://issues.apache.org/jira/browse/FLINK-13677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jark Wu resolved FLINK-13677. - Resolution: Fixed 1.10.0: 77d5999be6ffa547a40ecca28b76a8c83579f50f > Translate "Monitoring Back Pressure" page into Chinese > -- > > Key: FLINK-13677 > URL: https://issues.apache.org/jira/browse/FLINK-13677 > Project: Flink > Issue Type: Sub-task > Components: chinese-translation, Documentation >Affects Versions: 1.10.0 >Reporter: fanrui >Assignee: fanrui >Priority: Major > Labels: pull-request-available > Fix For: 1.10.0 > > Time Spent: 20m > Remaining Estimate: 0h > > The page url is > [https://ci.apache.org/projects/flink/flink-docs-master/zh/monitoring/back_pressure.html] > The markdown file is located in "docs/monitoring/back_pressure.zh.md" -- This message was sent by Atlassian Jira (v8.3.2#803003)
[GitHub] [flink] asfgit closed pull request #9606: [FLINK-13677][docs-zh] Translate "Monitoring Back Pressure" page into Chinese
asfgit closed pull request #9606: [FLINK-13677][docs-zh] Translate "Monitoring Back Pressure" page into Chinese URL: https://github.com/apache/flink/pull/9606 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9583: [hotfix][configuration] Remove usages of deprecated options TASK_MANAGER_HEAP_MEMORY_MB and JOB_MANAGER_HEAP_MEMORY_MB
flinkbot edited a comment on issue #9583: [hotfix][configuration] Remove usages of deprecated options TASK_MANAGER_HEAP_MEMORY_MB and JOB_MANAGER_HEAP_MEMORY_MB URL: https://github.com/apache/flink/pull/9583#issuecomment-526715510 ## CI report: * 6e904b5c61931e1cc84215ac297d1f3254b8 : PENDING [Build](https://travis-ci.com/flink-ci/flink/builds/125277398) This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot commented on issue #9654: [FLINK-13997][coordination] Remove legacy LeaderAddressAndId
flinkbot commented on issue #9654: [FLINK-13997][coordination] Remove legacy LeaderAddressAndId URL: https://github.com/apache/flink/pull/9654#issuecomment-529732738 ## CI report: * c34ea9703f66f705323d8720d4fe2d1de0ee799a : UNKNOWN This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9606: [FLINK-13677][docs-zh] Translate "Monitoring Back Pressure" page into Chinese
flinkbot edited a comment on issue #9606: [FLINK-13677][docs-zh] Translate "Monitoring Back Pressure" page into Chinese URL: https://github.com/apache/flink/pull/9606#issuecomment-527738237 Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community to review your pull request. We will use this comment to track the progress of the review. ## Automated Checks Last check on commit 4965f91617e3c220a2cb3e422dc783a443d5a228 (Tue Sep 10 01:44:35 UTC 2019) ✅no warnings Mention the bot in a comment to re-run the automated checks. ## Review Progress * ❓ 1. The [description] looks good. * ❓ 2. There is [consensus] that the contribution should go into to Flink. * ❓ 3. Needs [attention] from. * ❓ 4. The change fits into the overall [architecture]. * ❓ 5. Overall code [quality] is good. Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands The @flinkbot bot supports the following commands: - `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`) - `@flinkbot approve all` to approve all aspects - `@flinkbot approve-until architecture` to approve everything until `architecture` - `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention - `@flinkbot disapprove architecture` to remove an approval you gave earlier This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Comment Edited] (FLINK-14031) flink-examples-table should add the blink planner dependency
[
https://issues.apache.org/jira/browse/FLINK-14031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926240#comment-16926240
]
Leonard Xu edited comment on FLINK-14031 at 9/10/19 1:43 AM:
-
[~GatsbyNewton] good catch!
It looks like that we missed blink planner dependency here,
I'll fix it and add more related examples which use blink planner.
was (Author: leonard xu):
[~GatsbyNewton] good catch!
It looks like that we missed blink planner dependency here,
I'll fix it and add more related ** examples which use blink planner.
> flink-examples-table should add the blink planner dependency
>
>
> Key: FLINK-14031
> URL: https://issues.apache.org/jira/browse/FLINK-14031
> Project: Flink
> Issue Type: Bug
> Components: Examples
>Affects Versions: 1.9.0
>Reporter: Jimmy Wong
>Priority: Major
>
> The flink-examples-table module is missing blink planner dependency. If I run
> a blink example with Intellij IDEA, have error:
>
> {code:java}
> Exception in thread "main" org.apache.flink.table.api.TableException: Could
> not instantiate the executor. Make sure a planner module is on the
> classpathException in thread "main"
> org.apache.flink.table.api.TableException: Could not instantiate the
> executor. Make sure a planner module is on the classpath at
> org.apache.flink.table.api.java.internal.StreamTableEnvironmentImpl.lookupExecutor(StreamTableEnvironmentImpl.java:140)
> at
> org.apache.flink.table.api.java.internal.StreamTableEnvironmentImpl.create(StreamTableEnvironmentImpl.java:110)
> at
> org.apache.flink.table.api.java.StreamTableEnvironment.create(StreamTableEnvironment.java:112)
> at
> org.apache.flink.table.examples.java.BlinkStreamSQL.main(BlinkStreamSQL.java:19)Caused
> by: org.apache.flink.table.api.NoMatchingTableFactoryException: Could not
> find a suitable table factory for
> 'org.apache.flink.table.delegation.ExecutorFactory' inthe classpath.
> {code}
> *But*, once I add blink planner dependency, it'll work well.
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[jira] [Commented] (FLINK-14031) flink-examples-table should add the blink planner dependency
[
https://issues.apache.org/jira/browse/FLINK-14031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926240#comment-16926240
]
Leonard Xu commented on FLINK-14031:
[~GatsbyNewton] good catch!
It looks like that we missed blink planner dependency here,
I'll fix it and add more related ** examples which use blink planner.
> flink-examples-table should add the blink planner dependency
>
>
> Key: FLINK-14031
> URL: https://issues.apache.org/jira/browse/FLINK-14031
> Project: Flink
> Issue Type: Bug
> Components: Examples
>Affects Versions: 1.9.0
>Reporter: Jimmy Wong
>Priority: Major
>
> The flink-examples-table module is missing blink planner dependency. If I run
> a blink example with Intellij IDEA, have error:
>
> {code:java}
> Exception in thread "main" org.apache.flink.table.api.TableException: Could
> not instantiate the executor. Make sure a planner module is on the
> classpathException in thread "main"
> org.apache.flink.table.api.TableException: Could not instantiate the
> executor. Make sure a planner module is on the classpath at
> org.apache.flink.table.api.java.internal.StreamTableEnvironmentImpl.lookupExecutor(StreamTableEnvironmentImpl.java:140)
> at
> org.apache.flink.table.api.java.internal.StreamTableEnvironmentImpl.create(StreamTableEnvironmentImpl.java:110)
> at
> org.apache.flink.table.api.java.StreamTableEnvironment.create(StreamTableEnvironment.java:112)
> at
> org.apache.flink.table.examples.java.BlinkStreamSQL.main(BlinkStreamSQL.java:19)Caused
> by: org.apache.flink.table.api.NoMatchingTableFactoryException: Could not
> find a suitable table factory for
> 'org.apache.flink.table.delegation.ExecutorFactory' inthe classpath.
> {code}
> *But*, once I add blink planner dependency, it'll work well.
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
[GitHub] [flink] flinkbot edited a comment on issue #9350: [FLINK-13485] [chinese-translation] Translate "Table API Example Walkthrough" page into Chinese
flinkbot edited a comment on issue #9350: [FLINK-13485] [chinese-translation] Translate "Table API Example Walkthrough" page into Chinese URL: https://github.com/apache/flink/pull/9350#issuecomment-517933193 Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community to review your pull request. We will use this comment to track the progress of the review. ## Automated Checks Last check on commit b9c0f8b802135f95b9674a2440a4c4d9c6ebe5e4 (Tue Sep 10 01:38:30 UTC 2019) ✅no warnings Mention the bot in a comment to re-run the automated checks. ## Review Progress * ❓ 1. The [description] looks good. * ❓ 2. There is [consensus] that the contribution should go into to Flink. * ❓ 3. Needs [attention] from. * ❓ 4. The change fits into the overall [architecture]. * ❓ 5. Overall code [quality] is good. Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands The @flinkbot bot supports the following commands: - `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`) - `@flinkbot approve all` to approve all aspects - `@flinkbot approve-until architecture` to approve everything until `architecture` - `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention - `@flinkbot disapprove architecture` to remove an approval you gave earlier This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] wuchong commented on issue #9350: [FLINK-13485] [chinese-translation] Translate "Table API Example Walkthrough" page into Chinese
wuchong commented on issue #9350: [FLINK-13485] [chinese-translation] Translate "Table API Example Walkthrough" page into Chinese URL: https://github.com/apache/flink/pull/9350#issuecomment-529730892 Hi @AT-Fieldless , do you have time to update this PR? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot edited a comment on issue #9583: [hotfix][configuration] Remove usages of deprecated options TASK_MANAGER_HEAP_MEMORY_MB and JOB_MANAGER_HEAP_MEMORY_MB
flinkbot edited a comment on issue #9583: [hotfix][configuration] Remove usages of deprecated options TASK_MANAGER_HEAP_MEMORY_MB and JOB_MANAGER_HEAP_MEMORY_MB URL: https://github.com/apache/flink/pull/9583#issuecomment-526713253 Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community to review your pull request. We will use this comment to track the progress of the review. ## Automated Checks Last check on commit 6e904b5c61931e1cc84215ac297d1f3254b8 (Tue Sep 10 01:36:27 UTC 2019) **Warnings:** * No documentation files were touched! Remember to keep the Flink docs up to date! Mention the bot in a comment to re-run the automated checks. ## Review Progress * ❓ 1. The [description] looks good. * ❓ 2. There is [consensus] that the contribution should go into to Flink. * ❓ 3. Needs [attention] from. * ❓ 4. The change fits into the overall [architecture]. * ❓ 5. Overall code [quality] is good. Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands The @flinkbot bot supports the following commands: - `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`) - `@flinkbot approve all` to approve all aspects - `@flinkbot approve-until architecture` to approve everything until `architecture` - `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention - `@flinkbot disapprove architecture` to remove an approval you gave earlier This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [flink] flinkbot commented on issue #9654: [FLINK-13997][coordination] Remove legacy LeaderAddressAndId
flinkbot commented on issue #9654: [FLINK-13997][coordination] Remove legacy LeaderAddressAndId URL: https://github.com/apache/flink/pull/9654#issuecomment-529730998 Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community to review your pull request. We will use this comment to track the progress of the review. ## Automated Checks Last check on commit c34ea9703f66f705323d8720d4fe2d1de0ee799a (Tue Sep 10 01:37:17 UTC 2019) **Warnings:** * No documentation files were touched! Remember to keep the Flink docs up to date! Mention the bot in a comment to re-run the automated checks. ## Review Progress * ❓ 1. The [description] looks good. * ❓ 2. There is [consensus] that the contribution should go into to Flink. * ❓ 3. Needs [attention] from. * ❓ 4. The change fits into the overall [architecture]. * ❓ 5. Overall code [quality] is good. Please see the [Pull Request Review Guide](https://flink.apache.org/contributing/reviewing-prs.html) for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands The @flinkbot bot supports the following commands: - `@flinkbot approve description` to approve one or more aspects (aspects: `description`, `consensus`, `architecture` and `quality`) - `@flinkbot approve all` to approve all aspects - `@flinkbot approve-until architecture` to approve everything until `architecture` - `@flinkbot attention @username1 [@username2 ..]` to require somebody's attention - `@flinkbot disapprove architecture` to remove an approval you gave earlier This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (FLINK-13997) Remove legacy LeaderAddressAndId
[
https://issues.apache.org/jira/browse/FLINK-13997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-13997:
---
Labels: pull-request-available (was: )
> Remove legacy LeaderAddressAndId
>
>
> Key: FLINK-13997
> URL: https://issues.apache.org/jira/browse/FLINK-13997
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
>Affects Versions: 1.10.0
>Reporter: TisonKun
>Assignee: TisonKun
>Priority: Major
> Labels: pull-request-available
> Fix For: 1.10.0
>
>
> Also {{OneTimeLeaderListenerFuture}} which use {{LeaderAddressAndId}} but is
> dead code, too.
> I'd like to supersede FLINK-11664 with this one because I can see the
> requirement tight {{leader address}} with {{leader session id}}, but it is
> not {{LeaderAddressAndId}}. It would be more natural to introduce such class
> when addressing FLINK-10333. Instead of a dedicate JIRA changes here and
> there.
> WDYT? cc [~till.rohrmann]
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
