[jira] [Updated] (FLINK-22915) FLIP-173: Support DAG of algorithms
[ https://issues.apache.org/jira/browse/FLINK-22915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated FLINK-22915: --- Labels: pull-request-available (was: ) > FLIP-173: Support DAG of algorithms > --- > > Key: FLINK-22915 > URL: https://issues.apache.org/jira/browse/FLINK-22915 > Project: Flink > Issue Type: Improvement > Components: Library / Machine Learning >Reporter: Dong Lin >Priority: Major > Labels: pull-request-available > > The FLIP design doc can be found at > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=184615783. > The existing Flink ML library allows users to compose an > Estimator/Transformer from a pipeline (i.e. linear sequence) of > Estimator/Transformer, and each Estimator/Transformer has one input and one > output. > The following use-cases are not supported yet. And we would like to address > these use-cases with the changes proposed in this FLIP. > 1) Express an Estimator/Transformer that has multiple inputs/outputs. > For example, some graph embedding algorithms (e.g., MetaPath2Vec) need to > take two tables as inputs. These two tables represent nodes labels and edges > of the graph respectively. This logic can be expressed as an Estimator with 2 > input tables. > And some workflow may need to split 1 table into 2 tables, and use these > tables for training and validation respectively. This logic can be expressed > by a Transformer with 1 input table and 2 output tables. > 2) Express a generic machine learning computation logic that does not have > the "transformation" semantic. > We believe most machine learning engineers associate the name "Transformer" > with the "transformation" semantic, where the a record in the output > typically corresponds to one record in the input. Thus it is > counter-intuitive to use Transformer to encode aggregation logic, where a > record in the output corresponds to an arbitrary number of records in the > input. > Therefore we need to have a class with a name different from "Transformer" to > encode generic multi-input multi-output computation logic. > 3) Online learning where a long-running Model instance needs to be > continuously updated by the latest model data generated by another > long-running Estimator instance. > In this scenario, we need to allow the Estimator to be run on a different > machine than the Model, so that the Estimator could consume sufficient > computation resource in a cluster while the Model could be deployed on edge > devices. > 4) Provide APIs to allow Estimator/Model to be efficiently saved/loaded even > if state (e.g. model data) of Estimator/Model is more than 10s of GBs. > The existing PipelineStage::toJson basically requires developer of > Estimator/Model to serialize all model data into an in-memory string, which > could be very inefficient (or practically impossible) if the model data is > very large (e.g 10s of GBs). > In addition to addressing the above use-cases, this FLIP also proposes a few > more changes to simplify the class hierarchy and improve API usability. The > existing Flink ML library has the following usability issues: > 5) fit/transform API requires users to explicitly provide the > TableEnvironment, where the TableEnvironment could be retrieved from the > Table instance given to the fit/transform. > 6) A Pipeline is currently both a Transformer and an Estimator. The > experience of using Pipeline is inconsistent from the experience of using > Estimator (with the needFit API). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [flink-ml] lindong28 commented on pull request #4: [FLINK-22915][FLIP-173] Update Flink ML API to support AlgoOperator with multiple input tables and multiple output tables
lindong28 commented on pull request #4: URL: https://github.com/apache/flink-ml/pull/4#issuecomment-924610482 @becketqin Would you have time to review 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink-ml] lindong28 opened a new pull request #4: [FLINK-22915][FLIP-173] Update Flink ML API to support AlgoOperator with multiple input tables and multiple output tables
lindong28 opened a new pull request #4: URL: https://github.com/apache/flink-ml/pull/4 ## What is the purpose of the change This PR updates the Flink ML API according to [FLIP-173](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=184615783). ## Brief change log This PR mades the following changes: - Added the AlgoOperator class. AlgoOperator class has the same interface as the existing Transformer (i.e. provides the transform(...) API). - Updated fit/transform methods to take list of tables as inputs and return list of tables as output. - Added setModelData and getModelData to the Model interface. - Removed the methods PipelineStage::toJson and PipelineStage::loadJson. Added methods save(...) and load(...) to the Stage interface. - Removed TableEnvironment from the parameter list of fit/transform APIs. - Added pipelineModel and let Pipeline implement only the Estimator. Pipeline is no longer a Transformer. - Removed Pipeline::appendStage from the Pipeline class. - Renamed PipelineStage to Stage and add the PublicEvolving tag to the Stage interface. ## Verifying this change This PR focuses on changing the Flink ML API. Some APIs such as save/load needs to be implemented after we complete the design of the parameter interface. We will have followup PRs to implement all the Flink ML APIs and provide better test coverage. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): (no) - The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes) ## Documentation - Does this pull request introduce a new feature? (yes) - If yes, how is the feature documented? (Java doc) -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #17332: [FLINK-24349]Support customized Calalogs via JDBC
flinkbot edited a comment on pull request #17332: URL: https://github.com/apache/flink/pull/17332#issuecomment-924545241 ## CI report: * ec258f4e17badc0ea8bb0df005b6fe46f7d6b366 Azure: [PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24372) * 4f2da253163dfcd54ca47d9092bc5a070c1d8a84 Azure: [PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24376) Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #17308: [FLINK-24291][table-planner]Decimal precision is lost when deserializing in test cases
flinkbot edited a comment on pull request #17308: URL: https://github.com/apache/flink/pull/17308#issuecomment-921483643 ## CI report: * 8bab59ec4ddf8c0775e3199944be09f37aaa7a5d UNKNOWN * 1d20e8536f5cb590b904763fbcec1a5a2d074164 Azure: [FAILURE](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24246) Azure: [PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24377) * 347481706d1752ab6cdef0ae207d0b286bf6daf2 UNKNOWN * c01a08efebd47269ee842bd6e77472c468b482a8 UNKNOWN Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #17310: [FLINK-24308][docs] Translate Kafka DataStream connector documentation to Chinese
flinkbot edited a comment on pull request #17310: URL: https://github.com/apache/flink/pull/17310#issuecomment-921625581 ## CI report: * 932fbd23a1b9172312d8fc87a8d6ed04725e4b95 Azure: [SUCCESS](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24374) Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] xuyangzhong commented on pull request #17308: [FLINK-24291][table-planner]Decimal precision is lost when deserializing in test cases
xuyangzhong commented on pull request #17308: URL: https://github.com/apache/flink/pull/17308#issuecomment-924603078 @flinkbot run azure -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] Airblader commented on a change in pull request #17332: [FLINK-24349]Support customized Calalogs via JDBC
Airblader commented on a change in pull request #17332:
URL: https://github.com/apache/flink/pull/17332#discussion_r713600160
##
File path:
flink-connectors/flink-connector-jdbc/src/main/java/org/apache/flink/connector/jdbc/dialect/JdbcDialect.java
##
@@ -142,4 +143,16 @@
*/
String getSelectFromStatement(
String tableName, String[] selectFields, String[] conditionFields);
+
+/** Create catalog instance. */
+default AbstractJdbcCatalog createCatalog(
Review comment:
Logically this seems misplaced to me, because creating a catalog doesn't
relate to the definition of a dialect. However, I don't have a better
suggestion either, we shouldn't introduce even more custom infrastructure.
##
File path:
flink-connectors/flink-connector-jdbc/src/main/java/org/apache/flink/connector/jdbc/dialect/JdbcDialect.java
##
@@ -142,4 +143,16 @@
*/
String getSelectFromStatement(
String tableName, String[] selectFields, String[] conditionFields);
+
+/** Create catalog instance. */
+default AbstractJdbcCatalog createCatalog(
+String catalogName,
+String defaultDatabase,
+String username,
+String pwd,
+String baseUrl) {
+JdbcDialect dialect = JdbcDialectLoader.load(baseUrl);
+throw new UnsupportedOperationException(
+String.format("Catalog for '%s' is not supported yet.",
dialect));
Review comment:
This load call is unnecessary, it'll just find itself (`this`) anyway.
We're already in the loaded dialect here. We can also just directly use
`dialectName`.
```suggestion
String.format("Catalog for JDBC dialect '%s' is not
supported yet.", dialectName()));
```
##
File path:
flink-connectors/flink-connector-jdbc/src/main/java/org/apache/flink/connector/jdbc/dialect/JdbcDialect.java
##
@@ -142,4 +143,16 @@
*/
String getSelectFromStatement(
String tableName, String[] selectFields, String[] conditionFields);
+
+/** Create catalog instance. */
+default AbstractJdbcCatalog createCatalog(
+String catalogName,
Review comment:
We should move all of these parameters into a `Context` interface and
pass that so we can easily add more information if we need to without breaking
the API. This is similar to how table factories work, and basically the JDBC
dialect infrastructure is just a clone of table factories anyway.
--
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.
To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Commented] (FLINK-23486) Add monitoring/metrics for the ChangelogStateBackend
[ https://issues.apache.org/jira/browse/FLINK-23486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418415#comment-17418415 ] xingyuan cheng commented on FLINK-23486: Hello, it seems that we need to add some monitoring for flink back pressure. Can you explain the specific indicators you want to monitor? It seems that the parameters provided are not clear > Add monitoring/metrics for the ChangelogStateBackend > > > Key: FLINK-23486 > URL: https://issues.apache.org/jira/browse/FLINK-23486 > Project: Flink > Issue Type: Sub-task > Components: Benchmarks >Reporter: Roman Khachatryan >Priority: Major > Fix For: 1.15.0 > > > E.g. in-flight requests, request size, latency, number of “Logs” per request, > errors. > > With back-pressure (FLINK-23381) it's very important because the task will be > shown as busy in the UI. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [flink] flinkbot edited a comment on pull request #17334: [FLINK-24159][docs][Runtime/Checkpointing] document of entropy injection may mislead users
flinkbot edited a comment on pull request #17334: URL: https://github.com/apache/flink/pull/17334#issuecomment-924581916 ## CI report: * 2a5046348d38066feced088fe0e67f86c52f Azure: [PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24375) Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #17332: [FLINK-24349]Support customized Calalogs via JDBC
flinkbot edited a comment on pull request #17332: URL: https://github.com/apache/flink/pull/17332#issuecomment-924545241 ## CI report: * ec258f4e17badc0ea8bb0df005b6fe46f7d6b366 Azure: [PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24372) * 4f2da253163dfcd54ca47d9092bc5a070c1d8a84 UNKNOWN Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #17308: [FLINK-24291][table-planner]Decimal precision is lost when deserializing in test cases
flinkbot edited a comment on pull request #17308: URL: https://github.com/apache/flink/pull/17308#issuecomment-921483643 ## CI report: * 8bab59ec4ddf8c0775e3199944be09f37aaa7a5d UNKNOWN * 1d20e8536f5cb590b904763fbcec1a5a2d074164 Azure: [FAILURE](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24246) * 347481706d1752ab6cdef0ae207d0b286bf6daf2 UNKNOWN * c01a08efebd47269ee842bd6e77472c468b482a8 UNKNOWN Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot commented on pull request #17334: [FLINK-24159][docs][Runtime/Checkpointing] document of entropy injection may mislead users
flinkbot commented on pull request #17334: URL: https://github.com/apache/flink/pull/17334#issuecomment-924581916 ## CI report: * 2a5046348d38066feced088fe0e67f86c52f UNKNOWN Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #17308: [FLINK-24291][table-planner]Decimal precision is lost when deserializing in test cases
flinkbot edited a comment on pull request #17308: URL: https://github.com/apache/flink/pull/17308#issuecomment-921483643 ## CI report: * 8bab59ec4ddf8c0775e3199944be09f37aaa7a5d UNKNOWN * 1d20e8536f5cb590b904763fbcec1a5a2d074164 Azure: [FAILURE](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24246) * 347481706d1752ab6cdef0ae207d0b286bf6daf2 UNKNOWN Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (FLINK-24159) document of entropy injection may mislead users
[
https://issues.apache.org/jira/browse/FLINK-24159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418404#comment-17418404
]
Feifan Wang commented on FLINK-24159:
-
Thanks [~pnowojski] for reply, I have open a
[PR|https://github.com/apache/flink/pull/17334] for it, please hive a check as
you free.
> document of entropy injection may mislead users
> ---
>
> Key: FLINK-24159
> URL: https://issues.apache.org/jira/browse/FLINK-24159
> Project: Flink
> Issue Type: Improvement
> Components: Documentation, Runtime / Checkpointing
>Affects Versions: 1.14.0, 1.12.5, 1.13.2
>Reporter: Feifan Wang
>Assignee: Feifan Wang
>Priority: Major
> Labels: pull-request-available
>
> FLINK-9061 incroduce entropy inject to s3 path for better scalability, but in
> document of
> [entropy-injection-for-s3-file-systems|https://ci.apache.org/projects/flink/flink-docs-master/docs/deployment/filesystems/s3/#entropy-injection-for-s3-file-systems]
> use a example with checkpoint directory
> "{color:#ff}s3://my-bucket/checkpoints/_entropy_/dashboard-job/{color}",
> with this configuration every checkpoint key will still start with constant
> checkpoints/ prefix which actually reduces scalability.
> Thanks to dmtolpeko for describing this issue in his blog (
> [flink-and-s3-entropy-injection-for-checkpoints
> |http://cloudsqale.com/2021/01/02/flink-and-s3-entropy-injection-for-checkpoints/]).
> h3. Proposal
> alter the checkpoint directory in document of
> [entropy-injection-for-s3-file-systems|https://ci.apache.org/projects/flink/flink-docs-master/docs/deployment/filesystems/s3/#entropy-injection-for-s3-file-systems]
> to
> "{color:#ff}s3://my-bucket/_entropy_/checkpoints/dashboard-job/{color}"
> (make entropy key at start of keys).
>
> If this proposal is appropriate, I am glad to submit a PR to modify the
> document here. Any other ideas for this ?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [flink] flinkbot commented on pull request #17334: [FLINK-24159][docs][Runtime/Checkpointing] document of entropy injection may mislead users
flinkbot commented on pull request #17334: URL: https://github.com/apache/flink/pull/17334#issuecomment-924576693 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 2a5046348d38066feced088fe0e67f86c52f (Wed Sep 22 04:36:35 UTC 2021) ✅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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (FLINK-24159) document of entropy injection may mislead users
[
https://issues.apache.org/jira/browse/FLINK-24159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-24159:
---
Labels: pull-request-available (was: )
> document of entropy injection may mislead users
> ---
>
> Key: FLINK-24159
> URL: https://issues.apache.org/jira/browse/FLINK-24159
> Project: Flink
> Issue Type: Improvement
> Components: Documentation, Runtime / Checkpointing
>Affects Versions: 1.14.0, 1.12.5, 1.13.2
>Reporter: Feifan Wang
>Assignee: Feifan Wang
>Priority: Major
> Labels: pull-request-available
>
> FLINK-9061 incroduce entropy inject to s3 path for better scalability, but in
> document of
> [entropy-injection-for-s3-file-systems|https://ci.apache.org/projects/flink/flink-docs-master/docs/deployment/filesystems/s3/#entropy-injection-for-s3-file-systems]
> use a example with checkpoint directory
> "{color:#ff}s3://my-bucket/checkpoints/_entropy_/dashboard-job/{color}",
> with this configuration every checkpoint key will still start with constant
> checkpoints/ prefix which actually reduces scalability.
> Thanks to dmtolpeko for describing this issue in his blog (
> [flink-and-s3-entropy-injection-for-checkpoints
> |http://cloudsqale.com/2021/01/02/flink-and-s3-entropy-injection-for-checkpoints/]).
> h3. Proposal
> alter the checkpoint directory in document of
> [entropy-injection-for-s3-file-systems|https://ci.apache.org/projects/flink/flink-docs-master/docs/deployment/filesystems/s3/#entropy-injection-for-s3-file-systems]
> to
> "{color:#ff}s3://my-bucket/_entropy_/checkpoints/dashboard-job/{color}"
> (make entropy key at start of keys).
>
> If this proposal is appropriate, I am glad to submit a PR to modify the
> document here. Any other ideas for this ?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [flink] zoltar9264 opened a new pull request #17334: [FLINK-24159][docs][Runtime/Checkpointing] document of entropy injection may mislead users
zoltar9264 opened a new pull request #17334: URL: https://github.com/apache/flink/pull/17334 ## What is the purpose of the change Document fix described in [FLINK-24159](https://issues.apache.org/jira/browse/FLINK-24159). ## Brief change log alter the checkpoint directory in document of [entropy-injection-for-s3-file-systems](https://ci.apache.org/projects/flink/flink-docs-master/docs/deployment/filesystems/s3/#entropy-injection-for-s3-file-systems) to "s3://my-bucket/_entropy_/checkpoints/dashboard-job/" (make entropy key at start of keys). ## Verifying this change Not needed. ## Does this pull request potentially affect one of the following parts: - Dependencies (does it add or upgrade a dependency): no - 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, Kubernetes/Yarn, ZooKeeper: no - The S3 file system connector: no ## Documentation - Does this pull request introduce a new feature? no -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #17310: [FLINK-24308][docs] Translate Kafka DataStream connector documentation to Chinese
flinkbot edited a comment on pull request #17310: URL: https://github.com/apache/flink/pull/17310#issuecomment-921625581 ## CI report: * edaf47441984dccce163e0a91c53176a83b27675 Azure: [FAILURE](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24251) * 932fbd23a1b9172312d8fc87a8d6ed04725e4b95 Azure: [PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24374) Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (FLINK-23886) An exception is thrown out when recover job timers from checkpoint file
[ https://issues.apache.org/jira/browse/FLINK-23886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418400#comment-17418400 ] Steven Zhen Wu commented on FLINK-23886: Just to add another data point. We observed the same issue with Flink 1.13.2 in production. We don't know how to reproduce this type of tricky state corruption problem > An exception is thrown out when recover job timers from checkpoint file > --- > > Key: FLINK-23886 > URL: https://issues.apache.org/jira/browse/FLINK-23886 > Project: Flink > Issue Type: Bug > Components: Runtime / State Backends >Affects Versions: 1.10.0, 1.11.3 >Reporter: JING ZHANG >Priority: Major > Attachments: image-2021-08-25-16-38-04-023.png, > image-2021-08-25-16-38-12-308.png, image-2021-08-25-17-06-29-806.png, > image-2021-08-25-17-07-38-327.png > > > A user report the bug in the [mailist. > |http://mail-archives.apache.org/mod_mbox/flink-user/202108.mbox/%3ccakmsf43j14nkjmgjuy4dh5qn2vbjtw4tfh4pmmuyvcvfhgf...@mail.gmail.com%3E]I > paste the content here. > Setup Specifics: > Version: 1.6.2 > RocksDB Map State > Timers stored in rocksdb > > When we have this job running for long periods of time like > 30 days, if > for some reason the job restarts, we encounter "Error while deserializing the > element". Is this a known issue fixed in later versions? I see some changes > to code for FLINK-10175, but we don't use any queryable state > > Below is the stack trace > > org.apache.flink.util.FlinkRuntimeException: Error while deserializing the > element. > at > org.apache.flink.contrib.streaming.state.RocksDBCachingPriorityQueueSet.deserializeElement(RocksDBCachingPriorityQueueSet.java:389) > at > org.apache.flink.contrib.streaming.state.RocksDBCachingPriorityQueueSet.peek(RocksDBCachingPriorityQueueSet.java:146) > at > org.apache.flink.contrib.streaming.state.RocksDBCachingPriorityQueueSet.peek(RocksDBCachingPriorityQueueSet.java:56) > at > org.apache.flink.runtime.state.heap.KeyGroupPartitionedPriorityQueue$InternalPriorityQueueComparator.comparePriority(KeyGroupPartitionedPriorityQueue.java:274) > at > org.apache.flink.runtime.state.heap.KeyGroupPartitionedPriorityQueue$InternalPriorityQueueComparator.comparePriority(KeyGroupPartitionedPriorityQueue.java:261) > at > org.apache.flink.runtime.state.heap.HeapPriorityQueue.isElementPriorityLessThen(HeapPriorityQueue.java:164) > at > org.apache.flink.runtime.state.heap.HeapPriorityQueue.siftUp(HeapPriorityQueue.java:121) > at > org.apache.flink.runtime.state.heap.HeapPriorityQueue.addInternal(HeapPriorityQueue.java:85) > at > org.apache.flink.runtime.state.heap.AbstractHeapPriorityQueue.add(AbstractHeapPriorityQueue.java:73) > at > org.apache.flink.runtime.state.heap.KeyGroupPartitionedPriorityQueue.(KeyGroupPartitionedPriorityQueue.java:89) > at > org.apache.flink.contrib.streaming.state.RocksDBKeyedStateBackend$RocksDBPriorityQueueSetFactory.create(RocksDBKeyedStateBackend.java:2792) > at > org.apache.flink.contrib.streaming.state.RocksDBKeyedStateBackend.create(RocksDBKeyedStateBackend.java:450) > at > org.apache.flink.streaming.api.operators.InternalTimeServiceManager.createTimerPriorityQueue(InternalTimeServiceManager.java:121) > at > org.apache.flink.streaming.api.operators.InternalTimeServiceManager.registerOrGetTimerService(InternalTimeServiceManager.java:106) > at > org.apache.flink.streaming.api.operators.InternalTimeServiceManager.getInternalTimerService(InternalTimeServiceManager.java:87) > at > org.apache.flink.streaming.api.operators.AbstractStreamOperator.getInternalTimerService(AbstractStreamOperator.java:764) > at > org.apache.flink.streaming.api.operators.KeyedProcessOperator.open(KeyedProcessOperator.java:61) > at > org.apache.flink.streaming.runtime.tasks.StreamTask.openAllOperators(StreamTask.java:424) > at > org.apache.flink.streaming.runtime.tasks.StreamTask.invoke(StreamTask.java:290) > at org.apache.flink.runtime.taskmanager.Task.run(Task.java:711) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.io.EOFException > at java.io.DataInputStream.readUnsignedByte(DataInputStream.java:290) > at org.apache.flink.types.StringValue.readString(StringValue.java:769) > at > org.apache.flink.api.common.typeutils.base.StringSerializer.deserialize(StringSerializer.java:69) > at > org.apache.flink.api.common.typeutils.base.StringSerializer.deserialize(StringSerializer.java:28) > at > org.apache.flink.api.java.typeutils.runtime.RowSerializer.deserialize(RowSerializer.java:179) > at > org.apache.flink.api.java.typeutils.runtime.RowSerializer.deserialize(RowSerializer.java:46) > at > org.apache.flink.streaming.api.operators.TimerSerializer.deserialize(TimerSerializer.java:168) > at >
[GitHub] [flink] godfreyhe commented on a change in pull request #17311: [FLINK-24318][table-planner]Casting a number to boolean has different results between 'select' fields and 'where' condition
godfreyhe commented on a change in pull request #17311:
URL: https://github.com/apache/flink/pull/17311#discussion_r713572846
##
File path:
flink-table/flink-table-planner/src/test/scala/org/apache/flink/table/planner/plan/utils/FlinkRexUtilTest.scala
##
@@ -458,9 +461,64 @@ class FlinkRexUtilTest {
OR,
rexBuilder.makeCall(GREATER_THAN_OR_EQUAL, c, intLiteral(0)),
predicate18Search)
-val newPredicate20 = FlinkRexUtil.simplify(rexBuilder, predicate20)
+val newPredicate20 = simplify(rexBuilder, predicate20)
assertEquals(predicate20.toString, newPredicate20.toString)
+
+//CAST(1 AS BOOLEAN)
+val predicate21CastFromData = intLiteral(1)
+val predicate21CastToType = new BasicSqlType(typeFactory.getTypeSystem,
SqlTypeName.BOOLEAN)
+val predicate21 = rexBuilder.makeCall(
+ predicate21CastToType,
+ CAST,
+ Collections.singletonList(predicate21CastFromData.asInstanceOf[RexNode]))
Review comment:
please extract a method to create cast
--
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.
To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Commented] (FLINK-24179) KafkaSinkITCase.testRecoveryWithExactlyOnceGuarantee fails on azure
[
https://issues.apache.org/jira/browse/FLINK-24179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418398#comment-17418398
]
Xintong Song commented on FLINK-24179:
--
https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=24364=logs=72d4811f-9f0d-5fd0-014a-0bc26b72b642=e424005a-b16e-540f-196d-da062cc19bdf=7452
> KafkaSinkITCase.testRecoveryWithExactlyOnceGuarantee fails on azure
> ---
>
> Key: FLINK-24179
> URL: https://issues.apache.org/jira/browse/FLINK-24179
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kafka
>Affects Versions: 1.14.0, 1.15.0
>Reporter: Xintong Song
>Priority: Major
> Labels: test-stability
> Fix For: 1.15.0
>
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=23626=logs=ce8f3cc3-c1ea-5281-f5eb-df9ebd24947f=918e890f-5ed9-5212-a25e-962628fb4bc5=7339
> {code}
> Sep 06 23:42:30 [ERROR] Tests run: 7, Failures: 1, Errors: 0, Skipped: 0,
> Time elapsed: 59.927 s <<< FAILURE! - in
> org.apache.flink.connector.kafka.sink.KafkaSinkITCase
> Sep 06 23:42:30 [ERROR] testRecoveryWithExactlyOnceGuarantee Time elapsed:
> 10.505 s <<< FAILURE!
> Sep 06 23:42:30 java.lang.AssertionError: expected:<[1, 2, 3, 4, 5, 6]> but
> was:<[1, 2, 3, 4]>
> Sep 06 23:42:30 at org.junit.Assert.fail(Assert.java:89)
> Sep 06 23:42:30 at org.junit.Assert.failNotEquals(Assert.java:835)
> Sep 06 23:42:30 at org.junit.Assert.assertEquals(Assert.java:120)
> Sep 06 23:42:30 at org.junit.Assert.assertEquals(Assert.java:146)
> Sep 06 23:42:30 at
> org.apache.flink.connector.kafka.sink.KafkaSinkITCase.lambda$testRecoveryWithExactlyOnceGuarantee$1(KafkaSinkITCase.java:201)
> Sep 06 23:42:30 at
> org.apache.flink.connector.kafka.sink.KafkaSinkITCase.testRecoveryWithAssertion(KafkaSinkITCase.java:320)
> Sep 06 23:42:30 at
> org.apache.flink.connector.kafka.sink.KafkaSinkITCase.testRecoveryWithExactlyOnceGuarantee(KafkaSinkITCase.java:198)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FLINK-20928) KafkaSourceReaderTest.testOffsetCommitOnCheckpointComplete:189->pollUntil:270 » Timeout
[
https://issues.apache.org/jira/browse/FLINK-20928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418397#comment-17418397
]
Xintong Song commented on FLINK-20928:
--
https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=24364=logs=b0097207-033c-5d9a-b48c-6d4796fbe60d=8338a7d2-16f7-52e5-f576-4b7b3071eb3d=7033
> KafkaSourceReaderTest.testOffsetCommitOnCheckpointComplete:189->pollUntil:270
> » Timeout
> ---
>
> Key: FLINK-20928
> URL: https://issues.apache.org/jira/browse/FLINK-20928
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kafka
>Affects Versions: 1.13.0, 1.14.0, 1.15.0
>Reporter: Robert Metzger
>Assignee: Qingsheng Ren
>Priority: Critical
> Labels: test-stability
> Fix For: 1.14.0
>
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=11861=logs=c5f0071e-1851-543e-9a45-9ac140befc32=1fb1a56f-e8b5-5a82-00a0-a2db7757b4f5
> {code}
> [ERROR] Tests run: 8, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
> 93.992 s <<< FAILURE! - in
> org.apache.flink.connector.kafka.source.reader.KafkaSourceReaderTest
> [ERROR]
> testOffsetCommitOnCheckpointComplete(org.apache.flink.connector.kafka.source.reader.KafkaSourceReaderTest)
> Time elapsed: 60.086 s <<< ERROR!
> java.util.concurrent.TimeoutException: The offset commit did not finish
> before timeout.
> at
> org.apache.flink.core.testutils.CommonTestUtils.waitUtil(CommonTestUtils.java:210)
> at
> org.apache.flink.connector.kafka.source.reader.KafkaSourceReaderTest.pollUntil(KafkaSourceReaderTest.java:270)
> at
> org.apache.flink.connector.kafka.source.reader.KafkaSourceReaderTest.testOffsetCommitOnCheckpointComplete(KafkaSourceReaderTest.java:189)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [flink] flinkbot edited a comment on pull request #17332: [FLINK-24349]Support customized Calalogs via JDBC
flinkbot edited a comment on pull request #17332: URL: https://github.com/apache/flink/pull/17332#issuecomment-924545241 ## CI report: * ec258f4e17badc0ea8bb0df005b6fe46f7d6b366 Azure: [PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24372) Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #17333: [FLINK-24262][runtime] Remove unused ContainerOverlays
flinkbot edited a comment on pull request #17333: URL: https://github.com/apache/flink/pull/17333#issuecomment-924545312 ## CI report: * fad92f7becea65bfd3ae3d9b12a4ee4bf1a5a71b Azure: [PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24373) Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #17310: [FLINK-24308][docs] Translate Kafka DataStream connector documentation to Chinese
flinkbot edited a comment on pull request #17310: URL: https://github.com/apache/flink/pull/17310#issuecomment-921625581 ## CI report: * edaf47441984dccce163e0a91c53176a83b27675 Azure: [FAILURE](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24251) * 932fbd23a1b9172312d8fc87a8d6ed04725e4b95 UNKNOWN Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (FLINK-24321) The Pod Template supports replaceable content
[
https://issues.apache.org/jira/browse/FLINK-24321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418395#comment-17418395
]
liuzhuo commented on FLINK-24321:
-
"containerized.master.env." and "containerized.taskmanager.env." only take
effect at 'spec.containers.env' in the yaml file. If you want to modify other
information in the yaml file, I think there is no way.
> The Pod Template supports replaceable content
> -
>
> Key: FLINK-24321
> URL: https://issues.apache.org/jira/browse/FLINK-24321
> Project: Flink
> Issue Type: New Feature
> Components: Deployment / Kubernetes
>Reporter: liuzhuo
>Priority: Minor
>
> For the current use of pod template, if you want to perform some different
> configurations for each task, you can only modify the pod template file at
> present
> For example, if I want to mount the JM/TM log to the host for subsequent
> viewing, the following configuration will cause the file to be overwritten
> (the host's /data/log directory)
>
> {code:java}
> name: flink-log-volume
> hostPath:
> path: /data/log/
> type: DirectoryOrCreate{code}
>
> At present, it can only be solved by modifying the pod template. Should we
> provide a simpler way to use wildcard replacement to make runtime
> modifications, such as:
> {code:java}
> name: flink-log-volume
> hostPath:
> path: /data/log/${ClusterId}/
> type: DirectoryOrCreate{code}
>
> When constructing the pod, replace specific values, such as commonly used
> values such as ${ClusterId} and ${FlinkJobId}, or replace it with the
> configuration value of “org.apache.flink.configuration.Configuration”, such
> as "kubernetes.pod.temeplate. replace.jobmanager.UserId" = "100", this will
> automatically replace the value of ${UserId} in JM POD with 100
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [flink] dianfu commented on a change in pull request #16798: [FLINK-23651][python] Support RabbitMQ in PyFlink
dianfu commented on a change in pull request #16798: URL: https://github.com/apache/flink/pull/16798#discussion_r713559527 ## File path: flink-connectors/flink-sql-connector-rabbitmq/src/main/resources/META-INF/NOTICE ## @@ -0,0 +1,9 @@ +flink-connector-rabbitmq Review comment: ```suggestion flink-sql-connector-rabbitmq ``` -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot commented on pull request #17333: [FLINK-24262][runtime] Remove unused ContainerOverlays
flinkbot commented on pull request #17333: URL: https://github.com/apache/flink/pull/17333#issuecomment-924545312 ## CI report: * fad92f7becea65bfd3ae3d9b12a4ee4bf1a5a71b UNKNOWN Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot commented on pull request #17332: [FLINK-24349]Support customized Calalogs via JDBC
flinkbot commented on pull request #17332: URL: https://github.com/apache/flink/pull/17332#issuecomment-924545241 ## CI report: * ec258f4e17badc0ea8bb0df005b6fe46f7d6b366 UNKNOWN Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #16853: [FLINK-23827][table-planner] Fix ModifiedMonotonicity inference for s…
flinkbot edited a comment on pull request #16853: URL: https://github.com/apache/flink/pull/16853#issuecomment-900037847 ## CI report: * 0cc6f3f9235ffe069ca7eb7feac3e641cbe3cb22 Azure: [FAILURE](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24238) Azure: [FAILURE](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24186) Azure: [FAILURE](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24292) * 8cc244100e607f1e0778b099b38be1b8f5787d9c Azure: [PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24371) Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] godfreyhe commented on a change in pull request #17308: [FLINK-24291][table-planner]Decimal precision is lost when deserializing in test cases
godfreyhe commented on a change in pull request #17308:
URL: https://github.com/apache/flink/pull/17308#discussion_r713557487
##
File path:
flink-table/flink-table-planner/src/test/scala/org/apache/flink/table/planner/runtime/FileSystemITCaseBase.scala
##
@@ -95,6 +95,60 @@ trait FileSystemITCaseBase {
|)
""".stripMargin
)
+
+tableEnv.executeSql(
+ s"""
+ |create table hasDecimalFieldWithPrecisionTenAndZeroTable (
+ | x decimal(10, 0), y int
+ |) with (
+ | 'connector' = 'filesystem',
+ | 'path' = '$resultPath',
+ | ${formatProperties().mkString(",\n")}
+ |)
+ """.stripMargin
+)
+
+tableEnv.executeSql(
+ s"""
+ |create table hasDecimalFieldWithPrecisionThreeAndTwoTable (
+ | x decimal(3, 2), y int
+ |) with (
+ | 'connector' = 'filesystem',
+ | 'path' = '$resultPath',
+ | ${formatProperties().mkString(",\n")}
+ |)
+ """.stripMargin
+)
+ }
+
+ @Test
+ def testSelectDecimalWithPrecisionTenAndZeroFromFileSystem(): Unit={
Review comment:
make sense
--
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.
To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Updated] (FLINK-24351) translate "JSON Function" pages into Chinese
[ https://issues.apache.org/jira/browse/FLINK-24351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liwei li updated FLINK-24351: - Parent: FLINK-9477 Issue Type: Sub-task (was: Improvement) > translate "JSON Function" pages into Chinese > - > > Key: FLINK-24351 > URL: https://issues.apache.org/jira/browse/FLINK-24351 > Project: Flink > Issue Type: Sub-task > Components: Documentation >Reporter: liwei li >Priority: Major > > translate "JSON Function" pages into Chinese, > docs/data/sql_functions_zh.yml > > https://github.com/apache/flink/pull/17275#issuecomment-924536467 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FLINK-24271) Add document for special char in JSON_VALUE
[
https://issues.apache.org/jira/browse/FLINK-24271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418387#comment-17418387
]
liwei li commented on FLINK-24271:
--
[~lzljs3620320] Can you help to merge the pr?
> Add document for special char in JSON_VALUE
> ---
>
> Key: FLINK-24271
> URL: https://issues.apache.org/jira/browse/FLINK-24271
> Project: Flink
> Issue Type: Improvement
> Components: Documentation
>Reporter: Jingsong Lee
>Assignee: liwei li
>Priority: Minor
> Labels: pull-request-available, starter
>
> If user has a json string:
> {"fields": {"system.process": [0.998]}}
> It is hard to write a valid json path to get 0.998.
> The correct json path should be '$.fields.[''system.process''][0]'
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [flink] hililiwei edited a comment on pull request #17275: [FLINK-24271][docs] Add document for special char in JSON_VALUE and JSON_QUERY
hililiwei edited a comment on pull request #17275: URL: https://github.com/apache/flink/pull/17275#issuecomment-924536467 > @hililiwei Would you be able to do that translation in the end? I don't speak Chinese, so I wouldn't be able to do that task. It'd be good if we could close the parent issue ultimately, but I'm not 100% sure how Chinese translations should be handled here either. My understanding is that it's just an on-going effort. Let me open another issue to translate this part of the content. Although I use Chinese, my translation skills are not good enough. Let's see if there's someone else to do the translation. https://issues.apache.org/jira/browse/FLINK-24351 -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (FLINK-24351) translate "JSON Function" pages into Chinese
liwei li created FLINK-24351: Summary: translate "JSON Function" pages into Chinese Key: FLINK-24351 URL: https://issues.apache.org/jira/browse/FLINK-24351 Project: Flink Issue Type: Improvement Components: Documentation Reporter: liwei li translate "JSON Function" pages into Chinese, docs/data/sql_functions_zh.yml -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-24351) translate "JSON Function" pages into Chinese
[ https://issues.apache.org/jira/browse/FLINK-24351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liwei li updated FLINK-24351: - Description: translate "JSON Function" pages into Chinese, docs/data/sql_functions_zh.yml https://github.com/apache/flink/pull/17275#issuecomment-924536467 was: translate "JSON Function" pages into Chinese, docs/data/sql_functions_zh.yml > translate "JSON Function" pages into Chinese > - > > Key: FLINK-24351 > URL: https://issues.apache.org/jira/browse/FLINK-24351 > Project: Flink > Issue Type: Improvement > Components: Documentation >Reporter: liwei li >Priority: Major > > translate "JSON Function" pages into Chinese, > docs/data/sql_functions_zh.yml > > https://github.com/apache/flink/pull/17275#issuecomment-924536467 -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [flink] flinkbot commented on pull request #17333: [FLINK-24262][runtime] Remove unused ContainerOverlays
flinkbot commented on pull request #17333: URL: https://github.com/apache/flink/pull/17333#issuecomment-924536995 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 fad92f7becea65bfd3ae3d9b12a4ee4bf1a5a71b (Wed Sep 22 02:47:10 UTC 2021) **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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] hililiwei commented on pull request #17275: [FLINK-24271][docs] Add document for special char in JSON_VALUE and JSON_QUERY
hililiwei commented on pull request #17275: URL: https://github.com/apache/flink/pull/17275#issuecomment-924536467 > @hililiwei Would you be able to do that translation in the end? I don't speak Chinese, so I wouldn't be able to do that task. It'd be good if we could close the parent issue ultimately, but I'm not 100% sure how Chinese translations should be handled here either. My understanding is that it's just an on-going effort. Let me open another issue to translate this part of the content. Although I use Chinese, my translation skills are not good enough. Let's see if there's someone else to do the translation. -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (FLINK-24262) Remove unused ContainerOverlays
[ https://issues.apache.org/jira/browse/FLINK-24262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated FLINK-24262: --- Labels: pull-request-available (was: ) > Remove unused ContainerOverlays > --- > > Key: FLINK-24262 > URL: https://issues.apache.org/jira/browse/FLINK-24262 > Project: Flink > Issue Type: Technical Debt > Components: Runtime / Coordination >Affects Versions: 1.14.0 >Reporter: Yangze Guo >Assignee: Yangze Guo >Priority: Major > Labels: pull-request-available > Fix For: 1.14.1 > > > In FLINK-23118, we drop mesos support. Thus, we need also remove the unused > container overlays from our code base. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [flink] KarmaGYZ commented on pull request #17333: [FLINK-24262][runtime] Remove unused ContainerOverlays
KarmaGYZ commented on pull request #17333: URL: https://github.com/apache/flink/pull/17333#issuecomment-924535197 cc @zentol -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] KarmaGYZ opened a new pull request #17333: [FLINK-24262][runtime] Remove unused ContainerOverlays
KarmaGYZ opened a new pull request #17333: URL: https://github.com/apache/flink/pull/17333 ## What is the purpose of the change *(For example: This pull request makes task deployment go through the blob server, rather than through RPC. That way we avoid re-transferring them on each deployment (during recovery).)* ## Brief change log *(for example:)* - *The TaskInfo is stored in the blob store on job creation time as a persistent artifact* - *Deployments RPC transmits only the blob storage reference* - *TaskManagers retrieve the TaskInfo from the blob cache* ## Verifying this change *(Please pick either of the following options)* This change is a trivial rework / code cleanup without any test coverage. *(or)* This change is already covered by existing tests, such as *(please describe tests)*. *(or)* This change added tests and can be verified as follows: *(example:)* - *Added integration tests for end-to-end deployment with large payloads (100MB)* - *Extended integration test for recovery after master (JobManager) failure* - *Added test that validates that TaskInfo is transferred only once across recoveries* - *Manually verified the change by running a 4 node cluser with 2 JobManagers and 4 TaskManagers, a stateful streaming program, and killing one JobManager and two TaskManagers during the execution, verifying that recovery happens correctly.* ## 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, Kubernetes/Yarn, 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (FLINK-22942) Disable upsert into syntax in Flink SQL
[ https://issues.apache.org/jira/browse/FLINK-22942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418382#comment-17418382 ] Jark Wu commented on FLINK-22942: - We may also need to add a release note for this, even if it was never a public API, but there already been some users using it. > Disable upsert into syntax in Flink SQL > --- > > Key: FLINK-22942 > URL: https://issues.apache.org/jira/browse/FLINK-22942 > Project: Flink > Issue Type: Improvement > Components: Table SQL / API >Reporter: Leonard Xu >Assignee: Francesco Guardiani >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > I found we can write *insert into* and *upsert into* in Flink SQL， but the > later syntax's semantic and behavior is never discussed, currently they have > same implementation. > We should disable the later one util we support `*upsert into* ` with > correct behavior. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [flink] flinkbot edited a comment on pull request #16853: [FLINK-23827][table-planner] Fix ModifiedMonotonicity inference for s…
flinkbot edited a comment on pull request #16853: URL: https://github.com/apache/flink/pull/16853#issuecomment-900037847 ## CI report: * 0cc6f3f9235ffe069ca7eb7feac3e641cbe3cb22 Azure: [FAILURE](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24238) Azure: [FAILURE](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24186) Azure: [FAILURE](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24292) * 8cc244100e607f1e0778b099b38be1b8f5787d9c UNKNOWN Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot commented on pull request #17332: [FLINK-24349]Support customized Calalogs via JDBC
flinkbot commented on pull request #17332: URL: https://github.com/apache/flink/pull/17332#issuecomment-924530515 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 ec258f4e17badc0ea8bb0df005b6fe46f7d6b366 (Wed Sep 22 02:26:41 UTC 2021) **Warnings:** * 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-24349).** 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (FLINK-24349) Support customized Calalogs via JDBC
[ https://issues.apache.org/jira/browse/FLINK-24349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated FLINK-24349: --- Labels: pull-request-available (was: ) > Support customized Calalogs via JDBC > > > Key: FLINK-24349 > URL: https://issues.apache.org/jira/browse/FLINK-24349 > Project: Flink > Issue Type: Improvement > Components: Connectors / JDBC >Affects Versions: 1.12.2, 1.13.0, 1.14.0, 1.15.0 >Reporter: Bo Cui >Priority: Major > Labels: pull-request-available > > Support customized catalogs in flink-connector-jdbc -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [flink] cuibo01 opened a new pull request #17332: [FLINK-24349]Support customized Calalogs via JDBC
cuibo01 opened a new pull request #17332: URL: https://github.com/apache/flink/pull/17332 ## What is the purpose of the change *(For example: This pull request makes task deployment go through the blob server, rather than through RPC. That way we avoid re-transferring them on each deployment (during recovery).)* ## Brief change log *(for example:)* - *The TaskInfo is stored in the blob store on job creation time as a persistent artifact* - *Deployments RPC transmits only the blob storage reference* - *TaskManagers retrieve the TaskInfo from the blob cache* ## Verifying this change *(Please pick either of the following options)* This change is a trivial rework / code cleanup without any test coverage. *(or)* This change is already covered by existing tests, such as *(please describe tests)*. *(or)* This change added tests and can be verified as follows: *(example:)* - *Added integration tests for end-to-end deployment with large payloads (100MB)* - *Extended integration test for recovery after master (JobManager) failure* - *Added test that validates that TaskInfo is transferred only once across recoveries* - *Manually verified the change by running a 4 node cluser with 2 JobManagers and 4 TaskManagers, a stateful streaming program, and killing one JobManager and two TaskManagers during the execution, verifying that recovery happens correctly.* ## 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, Kubernetes/Yarn, 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (FLINK-24350) Resuming Savepoint (hashmap, sync, scale up) end-to-end test fails due to ask timeout
Xintong Song created FLINK-24350:
Summary: Resuming Savepoint (hashmap, sync, scale up) end-to-end
test fails due to ask timeout
Key: FLINK-24350
URL: https://issues.apache.org/jira/browse/FLINK-24350
Project: Flink
Issue Type: Bug
Components: Runtime / Coordination
Affects Versions: 1.15.0
Reporter: Xintong Song
https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=24361=logs=c88eea3b-64a0-564d-0031-9fdcd7b8abee=070ff179-953e-5bda-71fa-d6599415701c=142119
{code}
Sep 21 16:51:46 Caused by: org.apache.flink.util.SerializedThrowable:
Invocation of [RemoteRpcInvocation(null.triggerCheckpoint(ExecutionAttemptID,
long, long, CheckpointOptions))] at recipient
[akka.tcp://flink@10.1.0.216:38779/user/rpc/taskmanager_0] timed out.
Sep 21 16:51:46 at
org.apache.flink.runtime.jobmaster.RpcTaskManagerGateway.triggerCheckpoint(RpcTaskManagerGateway.java:106)
~[flink-dist_2.11-1.15-SNAPSHOT.jar:1.15-SNAPSHOT]
Sep 21 16:51:46 at
org.apache.flink.runtime.executiongraph.Execution.triggerCheckpointHelper(Execution.java:868)
~[flink-dist_2.11-1.15-SNAPSHOT.jar:1.15-SNAPSHOT]
Sep 21 16:51:46 at
org.apache.flink.runtime.executiongraph.Execution.triggerSynchronousSavepoint(Execution.java:850)
~[flink-dist_2.11-1.15-SNAPSHOT.jar:1.15-SNAPSHOT]
Sep 21 16:51:46 at
org.apache.flink.runtime.checkpoint.CheckpointCoordinator.triggerTasks(CheckpointCoordinator.java:710)
~[flink-dist_2.11-1.15-SNAPSHOT.jar:1.15-SNAPSHOT]
Sep 21 16:51:46 at
org.apache.flink.runtime.checkpoint.CheckpointCoordinator.triggerCheckpointRequest(CheckpointCoordinator.java:653)
~[flink-dist_2.11-1.15-SNAPSHOT.jar:1.15-SNAPSHOT]
Sep 21 16:51:46 at
org.apache.flink.runtime.checkpoint.CheckpointCoordinator.lambda$startTriggeringCheckpoint$6(CheckpointCoordinator.java:620)
~[flink-dist_2.11-1.15-SNAPSHOT.jar:1.15-SNAPSHOT]
Sep 21 16:51:46 at
java.util.concurrent.CompletableFuture.uniHandle(CompletableFuture.java:836)
~[?:1.8.0_292]
Sep 21 16:51:46 at
java.util.concurrent.CompletableFuture$UniHandle.tryFire(CompletableFuture.java:811)
~[?:1.8.0_292]
Sep 21 16:51:46 at
java.util.concurrent.CompletableFuture$Completion.run(CompletableFuture.java:456)
~[?:1.8.0_292]
Sep 21 16:51:46 at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
~[?:1.8.0_292]
Sep 21 16:51:46 at
java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_292]
Sep 21 16:51:46 at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
~[?:1.8.0_292]
Sep 21 16:51:46 at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
~[?:1.8.0_292]
Sep 21 16:51:46 at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
~[?:1.8.0_292]
Sep 21 16:51:46 at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
~[?:1.8.0_292]
Sep 21 16:51:46 at java.lang.Thread.run(Thread.java:748) ~[?:1.8.0_292]
Sep 21 16:51:46 Caused by: org.apache.flink.util.SerializedThrowable: Ask timed
out on
[Actor[akka.tcp://flink@10.1.0.216:38779/user/rpc/taskmanager_0#-1544322105]]
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.
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-24329) PulsarSourceITCase fails due to port conflict
[
https://issues.apache.org/jira/browse/FLINK-24329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xintong Song updated FLINK-24329:
-
Affects Version/s: 1.14.0
> PulsarSourceITCase fails due to port conflict
> --
>
> Key: FLINK-24329
> URL: https://issues.apache.org/jira/browse/FLINK-24329
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Pulsar
>Affects Versions: 1.14.0, 1.15.0
>Reporter: Xintong Song
>Assignee: xmarker
>Priority: Major
> Labels: pull-request-available, test-stability
> Fix For: 1.15.0
>
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=24255=logs=fc5181b0-e452-5c8f-68de-1097947f6483=995c650b-6573-581c-9ce6-7ad4cc038461=24666
> {code}
> Sep 17 12:47:02 Caused by: org.apache.pulsar.broker.PulsarServerException:
> org.apache.pulsar.broker.PulsarServerException: java.io.IOException: Failed
> to bind to /0.0.0.0:6972
> Sep 17 12:47:02 at
> org.apache.pulsar.broker.PulsarService.start(PulsarService.java:821)
> Sep 17 12:47:02 at
> org.apache.flink.connector.pulsar.testutils.runtime.mock.PulsarMockRuntime.startUp(PulsarMockRuntime.java:59)
> Sep 17 12:47:02 ... 39 more
> Sep 17 12:47:02 Caused by: org.apache.pulsar.broker.PulsarServerException:
> java.io.IOException: Failed to bind to /0.0.0.0:6972
> Sep 17 12:47:02 at
> org.apache.pulsar.broker.web.WebService.start(WebService.java:258)
> Sep 17 12:47:02 at
> org.apache.pulsar.broker.PulsarService.start(PulsarService.java:723)
> Sep 17 12:47:02 ... 40 more
> Sep 17 12:47:02 Caused by: java.io.IOException: Failed to bind to
> /0.0.0.0:6972
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:349)
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:310)
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:234)
> Sep 17 12:47:02 at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.Server.doStart(Server.java:401)
> Sep 17 12:47:02 at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
> Sep 17 12:47:02 at
> org.apache.pulsar.broker.web.WebService.start(WebService.java:241)
> Sep 17 12:47:02 ... 41 more
> Sep 17 12:47:02 Caused by: java.net.BindException: Address already in use
> Sep 17 12:47:02 at sun.nio.ch.Net.bind0(Native Method)
> Sep 17 12:47:02 at sun.nio.ch.Net.bind(Net.java:461)
> Sep 17 12:47:02 at sun.nio.ch.Net.bind(Net.java:453)
> Sep 17 12:47:02 at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:222)
> Sep 17 12:47:02 at
> sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:85)
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:344)
> Sep 17 12:47:02 ... 48 more
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-24329) PulsarSourceITCase fails due to port conflict
[
https://issues.apache.org/jira/browse/FLINK-24329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xintong Song updated FLINK-24329:
-
Fix Version/s: 1.14.0
> PulsarSourceITCase fails due to port conflict
> --
>
> Key: FLINK-24329
> URL: https://issues.apache.org/jira/browse/FLINK-24329
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Pulsar
>Affects Versions: 1.14.0, 1.15.0
>Reporter: Xintong Song
>Assignee: xmarker
>Priority: Major
> Labels: pull-request-available, test-stability
> Fix For: 1.14.0, 1.15.0
>
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=24255=logs=fc5181b0-e452-5c8f-68de-1097947f6483=995c650b-6573-581c-9ce6-7ad4cc038461=24666
> {code}
> Sep 17 12:47:02 Caused by: org.apache.pulsar.broker.PulsarServerException:
> org.apache.pulsar.broker.PulsarServerException: java.io.IOException: Failed
> to bind to /0.0.0.0:6972
> Sep 17 12:47:02 at
> org.apache.pulsar.broker.PulsarService.start(PulsarService.java:821)
> Sep 17 12:47:02 at
> org.apache.flink.connector.pulsar.testutils.runtime.mock.PulsarMockRuntime.startUp(PulsarMockRuntime.java:59)
> Sep 17 12:47:02 ... 39 more
> Sep 17 12:47:02 Caused by: org.apache.pulsar.broker.PulsarServerException:
> java.io.IOException: Failed to bind to /0.0.0.0:6972
> Sep 17 12:47:02 at
> org.apache.pulsar.broker.web.WebService.start(WebService.java:258)
> Sep 17 12:47:02 at
> org.apache.pulsar.broker.PulsarService.start(PulsarService.java:723)
> Sep 17 12:47:02 ... 40 more
> Sep 17 12:47:02 Caused by: java.io.IOException: Failed to bind to
> /0.0.0.0:6972
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:349)
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:310)
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:234)
> Sep 17 12:47:02 at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.Server.doStart(Server.java:401)
> Sep 17 12:47:02 at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
> Sep 17 12:47:02 at
> org.apache.pulsar.broker.web.WebService.start(WebService.java:241)
> Sep 17 12:47:02 ... 41 more
> Sep 17 12:47:02 Caused by: java.net.BindException: Address already in use
> Sep 17 12:47:02 at sun.nio.ch.Net.bind0(Native Method)
> Sep 17 12:47:02 at sun.nio.ch.Net.bind(Net.java:461)
> Sep 17 12:47:02 at sun.nio.ch.Net.bind(Net.java:453)
> Sep 17 12:47:02 at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:222)
> Sep 17 12:47:02 at
> sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:85)
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:344)
> Sep 17 12:47:02 ... 48 more
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-24349) Support customized Calalogs via JDBC
[ https://issues.apache.org/jira/browse/FLINK-24349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bo Cui updated FLINK-24349: --- Issue Type: Improvement (was: Bug) > Support customized Calalogs via JDBC > > > Key: FLINK-24349 > URL: https://issues.apache.org/jira/browse/FLINK-24349 > Project: Flink > Issue Type: Improvement > Components: Connectors / JDBC >Affects Versions: 1.12.2, 1.13.0, 1.14.0, 1.15.0 >Reporter: Bo Cui >Priority: Major > > Support customized catalogs in flink-connector-jdbc -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FLINK-24349) Support customized Calalogs via JDBC
Bo Cui created FLINK-24349: -- Summary: Support customized Calalogs via JDBC Key: FLINK-24349 URL: https://issues.apache.org/jira/browse/FLINK-24349 Project: Flink Issue Type: Bug Components: Connectors / JDBC Affects Versions: 1.13.0, 1.12.2, 1.14.0, 1.15.0 Reporter: Bo Cui Support customized catalogs in flink-connector-jdbc -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FLINK-24329) PulsarSourceITCase fails due to port conflict
[
https://issues.apache.org/jira/browse/FLINK-24329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418376#comment-17418376
]
Xintong Song commented on FLINK-24329:
--
Thanks for providing the PR, [~xmarker]. I've assigned you to this ticket.
[~syhily], if this also affects the 1.14 release, we should for sure backport
the fix.
> PulsarSourceITCase fails due to port conflict
> --
>
> Key: FLINK-24329
> URL: https://issues.apache.org/jira/browse/FLINK-24329
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Pulsar
>Affects Versions: 1.15.0
>Reporter: Xintong Song
>Assignee: xmarker
>Priority: Major
> Labels: pull-request-available, test-stability
> Fix For: 1.15.0
>
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=24255=logs=fc5181b0-e452-5c8f-68de-1097947f6483=995c650b-6573-581c-9ce6-7ad4cc038461=24666
> {code}
> Sep 17 12:47:02 Caused by: org.apache.pulsar.broker.PulsarServerException:
> org.apache.pulsar.broker.PulsarServerException: java.io.IOException: Failed
> to bind to /0.0.0.0:6972
> Sep 17 12:47:02 at
> org.apache.pulsar.broker.PulsarService.start(PulsarService.java:821)
> Sep 17 12:47:02 at
> org.apache.flink.connector.pulsar.testutils.runtime.mock.PulsarMockRuntime.startUp(PulsarMockRuntime.java:59)
> Sep 17 12:47:02 ... 39 more
> Sep 17 12:47:02 Caused by: org.apache.pulsar.broker.PulsarServerException:
> java.io.IOException: Failed to bind to /0.0.0.0:6972
> Sep 17 12:47:02 at
> org.apache.pulsar.broker.web.WebService.start(WebService.java:258)
> Sep 17 12:47:02 at
> org.apache.pulsar.broker.PulsarService.start(PulsarService.java:723)
> Sep 17 12:47:02 ... 40 more
> Sep 17 12:47:02 Caused by: java.io.IOException: Failed to bind to
> /0.0.0.0:6972
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:349)
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:310)
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:234)
> Sep 17 12:47:02 at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.Server.doStart(Server.java:401)
> Sep 17 12:47:02 at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
> Sep 17 12:47:02 at
> org.apache.pulsar.broker.web.WebService.start(WebService.java:241)
> Sep 17 12:47:02 ... 41 more
> Sep 17 12:47:02 Caused by: java.net.BindException: Address already in use
> Sep 17 12:47:02 at sun.nio.ch.Net.bind0(Native Method)
> Sep 17 12:47:02 at sun.nio.ch.Net.bind(Net.java:461)
> Sep 17 12:47:02 at sun.nio.ch.Net.bind(Net.java:453)
> Sep 17 12:47:02 at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:222)
> Sep 17 12:47:02 at
> sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:85)
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:344)
> Sep 17 12:47:02 ... 48 more
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (FLINK-24329) PulsarSourceITCase fails due to port conflict
[
https://issues.apache.org/jira/browse/FLINK-24329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xintong Song reassigned FLINK-24329:
Assignee: xmarker (was: Xintong Song)
> PulsarSourceITCase fails due to port conflict
> --
>
> Key: FLINK-24329
> URL: https://issues.apache.org/jira/browse/FLINK-24329
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Pulsar
>Affects Versions: 1.15.0
>Reporter: Xintong Song
>Assignee: xmarker
>Priority: Major
> Labels: pull-request-available, test-stability
> Fix For: 1.15.0
>
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=24255=logs=fc5181b0-e452-5c8f-68de-1097947f6483=995c650b-6573-581c-9ce6-7ad4cc038461=24666
> {code}
> Sep 17 12:47:02 Caused by: org.apache.pulsar.broker.PulsarServerException:
> org.apache.pulsar.broker.PulsarServerException: java.io.IOException: Failed
> to bind to /0.0.0.0:6972
> Sep 17 12:47:02 at
> org.apache.pulsar.broker.PulsarService.start(PulsarService.java:821)
> Sep 17 12:47:02 at
> org.apache.flink.connector.pulsar.testutils.runtime.mock.PulsarMockRuntime.startUp(PulsarMockRuntime.java:59)
> Sep 17 12:47:02 ... 39 more
> Sep 17 12:47:02 Caused by: org.apache.pulsar.broker.PulsarServerException:
> java.io.IOException: Failed to bind to /0.0.0.0:6972
> Sep 17 12:47:02 at
> org.apache.pulsar.broker.web.WebService.start(WebService.java:258)
> Sep 17 12:47:02 at
> org.apache.pulsar.broker.PulsarService.start(PulsarService.java:723)
> Sep 17 12:47:02 ... 40 more
> Sep 17 12:47:02 Caused by: java.io.IOException: Failed to bind to
> /0.0.0.0:6972
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:349)
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:310)
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:234)
> Sep 17 12:47:02 at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.Server.doStart(Server.java:401)
> Sep 17 12:47:02 at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
> Sep 17 12:47:02 at
> org.apache.pulsar.broker.web.WebService.start(WebService.java:241)
> Sep 17 12:47:02 ... 41 more
> Sep 17 12:47:02 Caused by: java.net.BindException: Address already in use
> Sep 17 12:47:02 at sun.nio.ch.Net.bind0(Native Method)
> Sep 17 12:47:02 at sun.nio.ch.Net.bind(Net.java:461)
> Sep 17 12:47:02 at sun.nio.ch.Net.bind(Net.java:453)
> Sep 17 12:47:02 at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:222)
> Sep 17 12:47:02 at
> sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:85)
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:344)
> Sep 17 12:47:02 ... 48 more
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (FLINK-24329) PulsarSourceITCase fails due to port conflict
[
https://issues.apache.org/jira/browse/FLINK-24329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xintong Song reassigned FLINK-24329:
Assignee: Xintong Song
> PulsarSourceITCase fails due to port conflict
> --
>
> Key: FLINK-24329
> URL: https://issues.apache.org/jira/browse/FLINK-24329
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Pulsar
>Affects Versions: 1.15.0
>Reporter: Xintong Song
>Assignee: Xintong Song
>Priority: Major
> Labels: pull-request-available, test-stability
> Fix For: 1.15.0
>
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=24255=logs=fc5181b0-e452-5c8f-68de-1097947f6483=995c650b-6573-581c-9ce6-7ad4cc038461=24666
> {code}
> Sep 17 12:47:02 Caused by: org.apache.pulsar.broker.PulsarServerException:
> org.apache.pulsar.broker.PulsarServerException: java.io.IOException: Failed
> to bind to /0.0.0.0:6972
> Sep 17 12:47:02 at
> org.apache.pulsar.broker.PulsarService.start(PulsarService.java:821)
> Sep 17 12:47:02 at
> org.apache.flink.connector.pulsar.testutils.runtime.mock.PulsarMockRuntime.startUp(PulsarMockRuntime.java:59)
> Sep 17 12:47:02 ... 39 more
> Sep 17 12:47:02 Caused by: org.apache.pulsar.broker.PulsarServerException:
> java.io.IOException: Failed to bind to /0.0.0.0:6972
> Sep 17 12:47:02 at
> org.apache.pulsar.broker.web.WebService.start(WebService.java:258)
> Sep 17 12:47:02 at
> org.apache.pulsar.broker.PulsarService.start(PulsarService.java:723)
> Sep 17 12:47:02 ... 40 more
> Sep 17 12:47:02 Caused by: java.io.IOException: Failed to bind to
> /0.0.0.0:6972
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:349)
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:310)
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:234)
> Sep 17 12:47:02 at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.Server.doStart(Server.java:401)
> Sep 17 12:47:02 at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
> Sep 17 12:47:02 at
> org.apache.pulsar.broker.web.WebService.start(WebService.java:241)
> Sep 17 12:47:02 ... 41 more
> Sep 17 12:47:02 Caused by: java.net.BindException: Address already in use
> Sep 17 12:47:02 at sun.nio.ch.Net.bind0(Native Method)
> Sep 17 12:47:02 at sun.nio.ch.Net.bind(Net.java:461)
> Sep 17 12:47:02 at sun.nio.ch.Net.bind(Net.java:453)
> Sep 17 12:47:02 at
> sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:222)
> Sep 17 12:47:02 at
> sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:85)
> Sep 17 12:47:02 at
> org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:344)
> Sep 17 12:47:02 ... 48 more
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-24348) KafkaTableITCase fail with "ContainerLaunch Container startup failed"
[
https://issues.apache.org/jira/browse/FLINK-24348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leonard Xu updated FLINK-24348:
---
Issue Type: Bug (was: New Feature)
> KafkaTableITCase fail with "ContainerLaunch Container startup failed"
> -
>
> Key: FLINK-24348
> URL: https://issues.apache.org/jira/browse/FLINK-24348
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kafka
>Affects Versions: 1.14.0
>Reporter: Dawid Wysakowicz
>Priority: Major
> Labels: test-stability
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=24338=logs=b0097207-033c-5d9a-b48c-6d4796fbe60d=8338a7d2-16f7-52e5-f576-4b7b3071eb3d=7140
> {code}
> Sep 21 02:44:33 org.testcontainers.containers.ContainerLaunchException:
> Container startup failed
> Sep 21 02:44:33 at
> org.testcontainers.containers.GenericContainer.doStart(GenericContainer.java:334)
> Sep 21 02:44:33 at
> org.testcontainers.containers.KafkaContainer.doStart(KafkaContainer.java:97)
> Sep 21 02:44:33 at
> org.apache.flink.streaming.connectors.kafka.table.KafkaTableTestBase$1.doStart(KafkaTableTestBase.java:71)
> Sep 21 02:44:33 at
> org.testcontainers.containers.GenericContainer.start(GenericContainer.java:315)
> Sep 21 02:44:33 at
> org.testcontainers.containers.GenericContainer.starting(GenericContainer.java:1060)
> Sep 21 02:44:33 at
> org.testcontainers.containers.FailureDetectingExternalResource$1.evaluate(FailureDetectingExternalResource.java:29)
> Sep 21 02:44:33 at
> org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> Sep 21 02:44:33 at
> org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
> Sep 21 02:44:33 at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> Sep 21 02:44:33 at
> org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
> Sep 21 02:44:33 at
> org.junit.runners.ParentRunner.run(ParentRunner.java:413)
> Sep 21 02:44:33 at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
> Sep 21 02:44:33 at org.junit.runner.JUnitCore.run(JUnitCore.java:115)
> Sep 21 02:44:33 at
> org.junit.vintage.engine.execution.RunnerExecutor.execute(RunnerExecutor.java:43)
> Sep 21 02:44:33 at
> java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
> Sep 21 02:44:33 at
> java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
> Sep 21 02:44:33 at
> java.util.Iterator.forEachRemaining(Iterator.java:116)
> Sep 21 02:44:33 at
> java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
> Sep 21 02:44:33 at
> java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:482)
> Sep 21 02:44:33 at
> java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:472)
> Sep 21 02:44:33 at
> java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150)
> Sep 21 02:44:33 at
> java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173)
> Sep 21 02:44:33 at
> java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
> Sep 21 02:44:33 at
> java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:485)
> Sep 21 02:44:33 at
> org.junit.vintage.engine.VintageTestEngine.executeAllChildren(VintageTestEngine.java:82)
> Sep 21 02:44:33 at
> org.junit.vintage.engine.VintageTestEngine.execute(VintageTestEngine.java:73)
> Sep 21 02:44:33 at
> org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:220)
> Sep 21 02:44:33 at
> org.junit.platform.launcher.core.DefaultLauncher.lambda$execute$6(DefaultLauncher.java:188)
> Sep 21 02:44:33 at
> org.junit.platform.launcher.core.DefaultLauncher.withInterceptedStreams(DefaultLauncher.java:202)
> Sep 21 02:44:33 at
> org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:181)
> Sep 21 02:44:33 at
> org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:128)
> Sep 21 02:44:33 at
> org.apache.maven.surefire.junitplatform.JUnitPlatformProvider.invokeAllTests(JUnitPlatformProvider.java:150)
> Sep 21 02:44:33 at
> org.apache.maven.surefire.junitplatform.JUnitPlatformProvider.invoke(JUnitPlatformProvider.java:120)
> Sep 21 02:44:33 at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:384)
> Sep 21 02:44:33 at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
> Sep 21 02:44:33 at
> org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
> Sep 21 02:44:33 at
>
[GitHub] [flink] leonardBang commented on a change in pull request #17305: [hotfix][flink-avro] Removed unused variable
leonardBang commented on a change in pull request #17305:
URL: https://github.com/apache/flink/pull/17305#discussion_r713532867
##
File path:
flink-formats/flink-avro/src/main/java/org/apache/flink/formats/avro/AvroRowDeserializationSchema.java
##
@@ -243,7 +243,6 @@ private Object convertAvroType(Schema schema,
TypeInformation info, Object ob
case UNION:
final List types = schema.getTypes();
final int size = types.size();
-final Schema actualSchema;
Review comment:
How about giving a meaningful `actualSchema` ?
```
final Schema actualSchema;
if (size == 2 && types.get(0).getType() == Schema.Type.NULL)
{
actualSchema = types.get(1);
} else if (size == 2 && types.get(1).getType() ==
Schema.Type.NULL) {
actualSchema = types.get(0);
} else if (size == 1) {
actualSchema = types.get(0);
} else {
// generic type
return object;
}
return convertAvroType(actualSchema, info, object);
```
--
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.
To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Closed] (FLINK-24347) KafkaSource cannot checkpoint if the parallelism is higher than the partition number
[ https://issues.apache.org/jira/browse/FLINK-24347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephan Ewen closed FLINK-24347. > KafkaSource cannot checkpoint if the parallelism is higher than the partition > number > > > Key: FLINK-24347 > URL: https://issues.apache.org/jira/browse/FLINK-24347 > Project: Flink > Issue Type: Bug > Components: Connectors / Kafka >Affects Versions: 1.14.0, 1.13.2 >Reporter: Fabian Paul >Assignee: Fabian Paul >Priority: Blocker > Labels: pull-request-available > Fix For: 1.14.0, 1.13.3 > > > The KafkaSourceEnumerator signals all the readers if there are no more splits > available and the readers shut down. In case the parallelism is higher than > the partitions of the consumed topic there are not enough partitions to > distribute and reader subtasks go immediately into FINISHED state. > Currently, it is not possible to checkpoint if parts of the job are finished. > (this is lifted once FLIP-147 is by default enabled Flink 1.15+) > We should only signal to the readers to go into finished if the job is in > bounded execution mode and keep them idling otherwise. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [flink] StephanEwen closed pull request #17329: [FLINK-24347][connectors/kafka] Keep idle source readers if paralleli…
StephanEwen closed pull request #17329: URL: https://github.com/apache/flink/pull/17329 -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] StephanEwen commented on pull request #17329: [FLINK-24347][connectors/kafka] Keep idle source readers if paralleli…
StephanEwen commented on pull request #17329: URL: https://github.com/apache/flink/pull/17329#issuecomment-924455791 Manually merged in a595fbbfe0087181f1b92d2d991a885911f290a2 -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Resolved] (FLINK-24347) KafkaSource cannot checkpoint if the parallelism is higher than the partition number
[ https://issues.apache.org/jira/browse/FLINK-24347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephan Ewen resolved FLINK-24347. -- Fix Version/s: 1.13.3 1.14.0 Resolution: Fixed Fixed in - master via d753cf20826c66f20bfbd3772c58709e00d9bcb7 - 1.14.0 (release-1.14) via a595fbbfe0087181f1b92d2d991a885911f290a2 - 1.13.3 (release-1.13) via 28211c0dec1dfb706c5d9583fd757cdd4de38ce8 > KafkaSource cannot checkpoint if the parallelism is higher than the partition > number > > > Key: FLINK-24347 > URL: https://issues.apache.org/jira/browse/FLINK-24347 > Project: Flink > Issue Type: Bug > Components: Connectors / Kafka >Affects Versions: 1.14.0, 1.13.2 >Reporter: Fabian Paul >Assignee: Fabian Paul >Priority: Blocker > Labels: pull-request-available > Fix For: 1.14.0, 1.13.3 > > > The KafkaSourceEnumerator signals all the readers if there are no more splits > available and the readers shut down. In case the parallelism is higher than > the partitions of the consumed topic there are not enough partitions to > distribute and reader subtasks go immediately into FINISHED state. > Currently, it is not possible to checkpoint if parts of the job are finished. > (this is lifted once FLIP-147 is by default enabled Flink 1.15+) > We should only signal to the readers to go into finished if the job is in > bounded execution mode and keep them idling otherwise. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [flink] StephanEwen merged pull request #17330: [FLINK-24347][connectors/kafka] Keep idle source readers if paralleli…
StephanEwen merged pull request #17330: URL: https://github.com/apache/flink/pull/17330 -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] StephanEwen closed pull request #17327: [FLINK-24347][connectors/kafka] Keep idle source readers if paralleli…
StephanEwen closed pull request #17327: URL: https://github.com/apache/flink/pull/17327 -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (FLINK-23397) [DOCS] task_failure_recovery page return 404
[ https://issues.apache.org/jira/browse/FLINK-23397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Flink Jira Bot updated FLINK-23397: --- Labels: auto-deprioritized-major pull-request-available (was: pull-request-available stale-major) Priority: Minor (was: Major) This issue was labeled "stale-major" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Major, please raise the priority and ask a committer to assign you the issue or revive the public discussion. > [DOCS] task_failure_recovery page return 404 > > > Key: FLINK-23397 > URL: https://issues.apache.org/jira/browse/FLINK-23397 > Project: Flink > Issue Type: Bug > Components: Documentation >Reporter: Dino Zhang >Priority: Minor > Labels: auto-deprioritized-major, pull-request-available > Attachments: image-2021-07-15-17-32-39-423.png > > > > [https://ci.apache.org/projects/flink/flink-docs-master/docs/ops/state/task_failure_recovery/] > > [https://ci.apache.org/projects/flink/flink-docs-master/docs/deployment/config/#advanced-fault-tolerance-options] > https://ci.apache.org/projects/flink/flink-docs-master/docs/deployment/config/#full-jobmanager-options > > > In the above page, clicking here will return a 404 > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FLINK-23944) PulsarSourceITCase.testTaskManagerFailure is instable
[
https://issues.apache.org/jira/browse/FLINK-23944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martijn Visser reassigned FLINK-23944:
--
Assignee: Yufan Sheng (was: Qingsheng Ren)
> PulsarSourceITCase.testTaskManagerFailure is instable
> -
>
> Key: FLINK-23944
> URL: https://issues.apache.org/jira/browse/FLINK-23944
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Pulsar
>Affects Versions: 1.14.0
>Reporter: Dian Fu
>Assignee: Yufan Sheng
>Priority: Critical
> Labels: pull-request-available, test-stability
> Fix For: 1.14.0, 1.15.0
>
>
> [https://dev.azure.com/dianfu/Flink/_build/results?buildId=430=logs=f3dc9b18-b77a-55c1-591e-264c46fe44d1=2d3cd81e-1c37-5c31-0ee4-f5d5cdb9324d]
> It's from my personal azure pipeline, however, I'm pretty sure that I have
> not touched any code related to this.
> {code:java}
> Aug 24 10:44:13 [ERROR] testTaskManagerFailure{TestEnvironment,
> ExternalContext, ClusterControllable}[1] Time elapsed: 258.397 s <<< FAILURE!
> Aug 24 10:44:13 java.lang.AssertionError: Aug 24 10:44:13 Aug 24 10:44:13
> Expected: Records consumed by Flink should be identical to test data and
> preserve the order in split Aug 24 10:44:13 but: Mismatched record at
> position 7: Expected '0W6SzacX7MNL4xLL3BZ8C3ljho4iCydbvxIl' but was
> 'wVi5JaJpNvgkDEOBRC775qHgw0LyRW2HBxwLmfONeEmr' Aug 24 10:44:13 at
> org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) Aug 24 10:44:13
> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:8) Aug 24
> 10:44:13 at
> org.apache.flink.connectors.test.common.testsuites.SourceTestSuiteBase.testTaskManagerFailure(SourceTestSuiteBase.java:271)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [flink] flinkbot edited a comment on pull request #17330: [FLINK-24347][connectors/kafka] Keep idle source readers if paralleli…
flinkbot edited a comment on pull request #17330: URL: https://github.com/apache/flink/pull/17330#issuecomment-924142235 ## CI report: * 144c1a4bf5b28d8ad2f3604e1c7148862208d5ad Azure: [SUCCESS](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24362) Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #17331: [FLINK-24344][runtime] Calling the CheckpointFailureManager even if the exception happens during the checkpoint initialization
flinkbot edited a comment on pull request #17331: URL: https://github.com/apache/flink/pull/17331#issuecomment-924142360 ## CI report: * 336d7f0aca4d20c49c1f6cb95ac3702511e8033c Azure: [FAILURE](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24363) Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #17329: [FLINK-24347][connectors/kafka] Keep idle source readers if paralleli…
flinkbot edited a comment on pull request #17329: URL: https://github.com/apache/flink/pull/17329#issuecomment-924120246 ## CI report: * 1187a0d0a8fe25a030e0b3364cc5fafde1132574 Azure: [SUCCESS](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24360) Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] dongjoon-hyun commented on pull request #16644: [FLINK-23551][Connectors/ORC] Bump ORC to 1.7.0
dongjoon-hyun commented on pull request #16644: URL: https://github.com/apache/flink/pull/16644#issuecomment-924229688 Thank you, @mbalassi ! :) -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #17327: [FLINK-24347][connectors/kafka] Keep idle source readers if paralleli…
flinkbot edited a comment on pull request #17327: URL: https://github.com/apache/flink/pull/17327#issuecomment-923962563 ## CI report: * 73c07edc64806c0e9e3d3a7dbffc30eebece0bc2 UNKNOWN * ff7160cbd80d3bc64a2ef0d1e22fb8a28e736ce8 Azure: [SUCCESS](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24358) Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (FLINK-24208) Allow idempotent savepoint triggering
[ https://issues.apache.org/jira/browse/FLINK-24208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418252#comment-17418252 ] Austin Cawley-Edwards commented on FLINK-24208: --- Great, we're on the same page. Thanks! > Allow idempotent savepoint triggering > - > > Key: FLINK-24208 > URL: https://issues.apache.org/jira/browse/FLINK-24208 > Project: Flink > Issue Type: Improvement > Components: Runtime / Checkpointing, Runtime / REST >Reporter: Robert Metzger >Priority: Major > > As a user of Flink, I want to be able to trigger a savepoint from an external > system in a way that I can detect if I have requested this savepoint already. > By passing a custom ID to the savepoint request, I can check (in case of an > error of the original request, or the external system) if the request has > been made already. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FLINK-23944) PulsarSourceITCase.testTaskManagerFailure is instable
[
https://issues.apache.org/jira/browse/FLINK-23944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418244#comment-17418244
]
Yufan Sheng commented on FLINK-23944:
-
[~dwysakowicz] OK, just assign it to me. I'll do it.
> PulsarSourceITCase.testTaskManagerFailure is instable
> -
>
> Key: FLINK-23944
> URL: https://issues.apache.org/jira/browse/FLINK-23944
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Pulsar
>Affects Versions: 1.14.0
>Reporter: Dian Fu
>Assignee: Qingsheng Ren
>Priority: Critical
> Labels: pull-request-available, test-stability
> Fix For: 1.14.0, 1.15.0
>
>
> [https://dev.azure.com/dianfu/Flink/_build/results?buildId=430=logs=f3dc9b18-b77a-55c1-591e-264c46fe44d1=2d3cd81e-1c37-5c31-0ee4-f5d5cdb9324d]
> It's from my personal azure pipeline, however, I'm pretty sure that I have
> not touched any code related to this.
> {code:java}
> Aug 24 10:44:13 [ERROR] testTaskManagerFailure{TestEnvironment,
> ExternalContext, ClusterControllable}[1] Time elapsed: 258.397 s <<< FAILURE!
> Aug 24 10:44:13 java.lang.AssertionError: Aug 24 10:44:13 Aug 24 10:44:13
> Expected: Records consumed by Flink should be identical to test data and
> preserve the order in split Aug 24 10:44:13 but: Mismatched record at
> position 7: Expected '0W6SzacX7MNL4xLL3BZ8C3ljho4iCydbvxIl' but was
> 'wVi5JaJpNvgkDEOBRC775qHgw0LyRW2HBxwLmfONeEmr' Aug 24 10:44:13 at
> org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20) Aug 24 10:44:13
> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:8) Aug 24
> 10:44:13 at
> org.apache.flink.connectors.test.common.testsuites.SourceTestSuiteBase.testTaskManagerFailure(SourceTestSuiteBase.java:271)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [flink] flinkbot edited a comment on pull request #17328: Group of hotfix commits fixing a couple of things in the tests
flinkbot edited a comment on pull request #17328: URL: https://github.com/apache/flink/pull/17328#issuecomment-924027879 ## CI report: * 7504cd9aae82a742cab6e5dd15bbbf4ab49b3599 Azure: [FAILURE](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24359) Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] mbalassi commented on pull request #16644: [FLINK-23551][Connectors/ORC] Bump ORC to 1.7.0
mbalassi commented on pull request #16644: URL: https://github.com/apache/flink/pull/16644#issuecomment-924182969 Hi @dongjoon-hyun, Please let us know when you open the updated version. 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #17327: [FLINK-24347][connectors/kafka] Keep idle source readers if paralleli…
flinkbot edited a comment on pull request #17327: URL: https://github.com/apache/flink/pull/17327#issuecomment-923962563 ## CI report: * 9408d97a015235359fba3d97fbc0bf8fda844c61 Azure: [CANCELED](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24353) * 73c07edc64806c0e9e3d3a7dbffc30eebece0bc2 UNKNOWN * ff7160cbd80d3bc64a2ef0d1e22fb8a28e736ce8 Azure: [PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24358) Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #17330: [FLINK-24347][connectors/kafka] Keep idle source readers if paralleli…
flinkbot edited a comment on pull request #17330: URL: https://github.com/apache/flink/pull/17330#issuecomment-924142235 ## CI report: * 144c1a4bf5b28d8ad2f3604e1c7148862208d5ad Azure: [PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24362) Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #17331: [FLINK-24344][runtime] Calling the CheckpointFailureManager even if the exception happens during the checkpoint initialization
flinkbot edited a comment on pull request #17331: URL: https://github.com/apache/flink/pull/17331#issuecomment-924142360 ## CI report: * 336d7f0aca4d20c49c1f6cb95ac3702511e8033c Azure: [PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24363) Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (FLINK-24347) KafkaSource cannot checkpoint if the parallelism is higher than the partition number
[ https://issues.apache.org/jira/browse/FLINK-24347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17418213#comment-17418213 ] Thomas Weise commented on FLINK-24347: -- Thanks for fixing this. In unbounded executions readers should stay alive because new partitions/splits can be discovered dynamically. > KafkaSource cannot checkpoint if the parallelism is higher than the partition > number > > > Key: FLINK-24347 > URL: https://issues.apache.org/jira/browse/FLINK-24347 > Project: Flink > Issue Type: Bug > Components: Connectors / Kafka >Affects Versions: 1.14.0, 1.13.2 >Reporter: Fabian Paul >Assignee: Fabian Paul >Priority: Blocker > Labels: pull-request-available > > The KafkaSourceEnumerator signals all the readers if there are no more splits > available and the readers shut down. In case the parallelism is higher than > the partitions of the consumed topic there are not enough partitions to > distribute and reader subtasks go immediately into FINISHED state. > Currently, it is not possible to checkpoint if parts of the job are finished. > (this is lifted once FLIP-147 is by default enabled Flink 1.15+) > We should only signal to the readers to go into finished if the job is in > bounded execution mode and keep them idling otherwise. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [flink] flinkbot commented on pull request #17331: [FLINK-24344][runtime] Calling the CheckpointFailureManager even if the exception happens during the checkpoint initialization
flinkbot commented on pull request #17331: URL: https://github.com/apache/flink/pull/17331#issuecomment-924142360 ## CI report: * 336d7f0aca4d20c49c1f6cb95ac3702511e8033c UNKNOWN Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot commented on pull request #17330: [FLINK-24347][connectors/kafka] Keep idle source readers if paralleli…
flinkbot commented on pull request #17330: URL: https://github.com/apache/flink/pull/17330#issuecomment-924142235 ## CI report: * 144c1a4bf5b28d8ad2f3604e1c7148862208d5ad UNKNOWN Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #17329: [FLINK-24347][connectors/kafka] Keep idle source readers if paralleli…
flinkbot edited a comment on pull request #17329: URL: https://github.com/apache/flink/pull/17329#issuecomment-924120246 ## CI report: * 1187a0d0a8fe25a030e0b3364cc5fafde1132574 Azure: [PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24360) Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Resolved] (FLINK-23389) AWS Glue Schema Registry JSON support for Apache Flink
[ https://issues.apache.org/jira/browse/FLINK-23389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Danny Cranmer resolved FLINK-23389. --- Resolution: Done > AWS Glue Schema Registry JSON support for Apache Flink > -- > > Key: FLINK-23389 > URL: https://issues.apache.org/jira/browse/FLINK-23389 > Project: Flink > Issue Type: New Feature > Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile) >Reporter: Kexin Hui >Assignee: Kexin Hui >Priority: Major > Labels: pull-request-available > Fix For: 1.15.0 > > > AWS Glue Schema Registry client library has recently released a new version > (v1.1.1) which highlights JSON support. This request is to add the new data > format support to launch an integration for Apache Flink with the latest AWS > Glue Schema Registry. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [flink] dannycranmer merged pull request #16513: [FLINK-23389][Formats] Glue schema registry JSON support
dannycranmer merged pull request #16513: URL: https://github.com/apache/flink/pull/16513 -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] dannycranmer commented on pull request #16513: [FLINK-23389][Formats] Glue schema registry JSON support
dannycranmer commented on pull request #16513: URL: https://github.com/apache/flink/pull/16513#issuecomment-924133186 e2e tests pass locally. Merging -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot commented on pull request #17329: [FLINK-24347][connectors/kafka] Keep idle source readers if paralleli…
flinkbot commented on pull request #17329: URL: https://github.com/apache/flink/pull/17329#issuecomment-924120246 ## CI report: * 1187a0d0a8fe25a030e0b3364cc5fafde1132574 UNKNOWN Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot commented on pull request #17330: [FLINK-24347][connectors/kafka] Keep idle source readers if paralleli…
flinkbot commented on pull request #17330: URL: https://github.com/apache/flink/pull/17330#issuecomment-924116638 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 144c1a4bf5b28d8ad2f3604e1c7148862208d5ad (Tue Sep 21 15:46:25 UTC 2021) **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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot commented on pull request #17331: [FLINK-24344][runtime] Calling the CheckpointFailureManager even if the exception happens during the checkpoint initialization
flinkbot commented on pull request #17331: URL: https://github.com/apache/flink/pull/17331#issuecomment-924116602 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 336d7f0aca4d20c49c1f6cb95ac3702511e8033c (Tue Sep 21 15:46:23 UTC 2021) **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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (FLINK-24344) Handling of IOExceptions when triggering checkpoints doesn't cause job failover
[
https://issues.apache.org/jira/browse/FLINK-24344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-24344:
---
Labels: pull-request-available (was: )
> Handling of IOExceptions when triggering checkpoints doesn't cause job
> failover
> ---
>
> Key: FLINK-24344
> URL: https://issues.apache.org/jira/browse/FLINK-24344
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Checkpointing
>Affects Versions: 1.14.0
>Reporter: Piotr Nowojski
>Assignee: Anton Kalashnikov
>Priority: Critical
> Labels: pull-request-available
> Fix For: 1.14.0, 1.15.0
>
>
> When running
> {{CheckpointCoordinatorTest#testTriggerCheckpointAfterIOException}}, it
> simulates an {{IOException}} thrown from
> {{CheckpointCoordinator#initializeCheckpoint}}. Which makes sense but:
> # This exception never reaches {{CheckpointFailureManager}} because of the
> logic in {{CheckpointCoordinator#onTriggerFailure()}}. So the main purpose of
> the FLINK-23189 ticket is not working as intended.
> # it would be however much much better to throw {{IOException}} from
> {{checkpointStorageView.initializeLocationForCheckpoint}} rather from
> {{checkpointIdCounter.getAndIncrement}}. The latter could be refactored out,
> while the production {{IOException}} can be thrown in reality from
> {{initializeLocationForCheckpoint}})
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [flink] akalash opened a new pull request #17331: [FLINK-24344][runtime] Calling the CheckpointFailureManager even if the exception happens during the checkpoint initialization
akalash opened a new pull request #17331: URL: https://github.com/apache/flink/pull/17331 ## What is the purpose of the change *This PR fixes the situation when the checkpoint exception happens during the checkpoint initialization and doesn't call the CheckpintFailureManager* ## Brief change log - *Calling the CheckpointFailureManager even if the checkpointId is unknown* ## Verifying this change This change added tests and can be verified as follows: *(example:)* - *Expanded testTriggerCheckpointAfterIOException test* ## 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, Kubernetes/Yarn, 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] fapaul opened a new pull request #17330: [FLINK-24347][connectors/kafka] Keep idle source readers if paralleli…
fapaul opened a new pull request #17330: URL: https://github.com/apache/flink/pull/17330 …sm is higher than partitions in KafkaSource Unchanged backport of #17327 -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #17327: [FLINK-24347][connectors/kafka] Keep idle source readers if paralleli…
flinkbot edited a comment on pull request #17327: URL: https://github.com/apache/flink/pull/17327#issuecomment-923962563 ## CI report: * 9408d97a015235359fba3d97fbc0bf8fda844c61 Azure: [PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24353) * 73c07edc64806c0e9e3d3a7dbffc30eebece0bc2 UNKNOWN * ff7160cbd80d3bc64a2ef0d1e22fb8a28e736ce8 Azure: [PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24358) Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Issue Comment Deleted] (FLINK-22819) YARNFileReplicationITCase fails with "The YARN application unexpectedly switched to state FAILED during deployment"
[
https://issues.apache.org/jira/browse/FLINK-22819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Wysakowicz updated FLINK-22819:
-
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> YARNFileReplicationITCase fails with "The YARN application unexpectedly
> switched to state FAILED during deployment"
> ---
>
> Key: FLINK-22819
> URL: https://issues.apache.org/jira/browse/FLINK-22819
> Project: Flink
> Issue Type: Bug
> Components: Deployment / YARN
>Affects Versions: 1.13.1
>Reporter: Dawid Wysakowicz
>Assignee: David Morávek
>Priority: Major
> Labels: pull-request-available, stale-major, test-stability
> Fix For: 1.14.0, 1.12.5, 1.13.2
>
> Attachments:
> FLINK-22819-YARNFileReplicationITCase-testPerJobModeWithDefaultFileReplication.log
>
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=18467=logs=8fd975ef-f478-511d-4997-6f15fe8a1fd3=ac0fa443-5d45-5a6b-3597-0310ecc1d2ab=32007
> {code}
> May 31 23:14:22
> org.apache.flink.client.deployment.ClusterDeploymentException: Could not
> deploy Yarn job cluster.
> May 31 23:14:22 at
> org.apache.flink.yarn.YarnClusterDescriptor.deployJobCluster(YarnClusterDescriptor.java:481)
> May 31 23:14:22 at
> org.apache.flink.yarn.YARNFileReplicationITCase.deployPerJob(YARNFileReplicationITCase.java:106)
> May 31 23:14:22 at
> org.apache.flink.yarn.YARNFileReplicationITCase.lambda$testPerJobModeWithDefaultFileReplication$1(YARNFileReplicationITCase.java:78)
> May 31 23:14:22 at
> org.apache.flink.yarn.YarnTestBase.runTest(YarnTestBase.java:287)
> May 31 23:14:22 at
> org.apache.flink.yarn.YARNFileReplicationITCase.testPerJobModeWithDefaultFileReplication(YARNFileReplicationITCase.java:78)
> May 31 23:14:22 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> May 31 23:14:22 at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> May 31 23:14:22 at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> May 31 23:14:22 at java.lang.reflect.Method.invoke(Method.java:498)
> May 31 23:14:22 at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> May 31 23:14:22 at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> May 31 23:14:22 at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> May 31 23:14:22 at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> May 31 23:14:22 at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> May 31 23:14:22 at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> May 31 23:14:22 at
> org.apache.flink.util.TestNameProvider$1.evaluate(TestNameProvider.java:45)
> May 31 23:14:22 at
> org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> May 31 23:14:22 at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> May 31 23:14:22 at
> org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> May 31 23:14:22 at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> May 31 23:14:22 at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> May 31 23:14:22 at
> org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> May 31 23:14:22 at
> org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> May 31 23:14:22 at
> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> May 31 23:14:22 at
> org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> May 31 23:14:22 at
> org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> May 31 23:14:22 at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> May 31 23:14:22 at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> May 31 23:14:22 at
> org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> May 31 23:14:22 at
> org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> May 31 23:14:22 at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> May 31 23:14:22 at
> org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> May 31 23:14:22 at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> May 31 23:14:22 at
>
[jira] [Issue Comment Deleted] (FLINK-22819) YARNFileReplicationITCase fails with "The YARN application unexpectedly switched to state FAILED during deployment"
[
https://issues.apache.org/jira/browse/FLINK-22819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Wysakowicz updated FLINK-22819:
-
Comment: was deleted
(was: A comment with security level 'jira-users' was removed.)
> YARNFileReplicationITCase fails with "The YARN application unexpectedly
> switched to state FAILED during deployment"
> ---
>
> Key: FLINK-22819
> URL: https://issues.apache.org/jira/browse/FLINK-22819
> Project: Flink
> Issue Type: Bug
> Components: Deployment / YARN
>Affects Versions: 1.13.1
>Reporter: Dawid Wysakowicz
>Assignee: David Morávek
>Priority: Major
> Labels: pull-request-available, stale-major, test-stability
> Fix For: 1.14.0, 1.12.5, 1.13.2
>
> Attachments:
> FLINK-22819-YARNFileReplicationITCase-testPerJobModeWithDefaultFileReplication.log
>
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=18467=logs=8fd975ef-f478-511d-4997-6f15fe8a1fd3=ac0fa443-5d45-5a6b-3597-0310ecc1d2ab=32007
> {code}
> May 31 23:14:22
> org.apache.flink.client.deployment.ClusterDeploymentException: Could not
> deploy Yarn job cluster.
> May 31 23:14:22 at
> org.apache.flink.yarn.YarnClusterDescriptor.deployJobCluster(YarnClusterDescriptor.java:481)
> May 31 23:14:22 at
> org.apache.flink.yarn.YARNFileReplicationITCase.deployPerJob(YARNFileReplicationITCase.java:106)
> May 31 23:14:22 at
> org.apache.flink.yarn.YARNFileReplicationITCase.lambda$testPerJobModeWithDefaultFileReplication$1(YARNFileReplicationITCase.java:78)
> May 31 23:14:22 at
> org.apache.flink.yarn.YarnTestBase.runTest(YarnTestBase.java:287)
> May 31 23:14:22 at
> org.apache.flink.yarn.YARNFileReplicationITCase.testPerJobModeWithDefaultFileReplication(YARNFileReplicationITCase.java:78)
> May 31 23:14:22 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> May 31 23:14:22 at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> May 31 23:14:22 at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> May 31 23:14:22 at java.lang.reflect.Method.invoke(Method.java:498)
> May 31 23:14:22 at
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> May 31 23:14:22 at
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> May 31 23:14:22 at
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> May 31 23:14:22 at
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> May 31 23:14:22 at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> May 31 23:14:22 at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> May 31 23:14:22 at
> org.apache.flink.util.TestNameProvider$1.evaluate(TestNameProvider.java:45)
> May 31 23:14:22 at
> org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
> May 31 23:14:22 at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> May 31 23:14:22 at
> org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> May 31 23:14:22 at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> May 31 23:14:22 at
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> May 31 23:14:22 at
> org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> May 31 23:14:22 at
> org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> May 31 23:14:22 at
> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> May 31 23:14:22 at
> org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> May 31 23:14:22 at
> org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> May 31 23:14:22 at
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> May 31 23:14:22 at
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> May 31 23:14:22 at
> org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> May 31 23:14:22 at
> org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> May 31 23:14:22 at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> May 31 23:14:22 at
> org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> May 31 23:14:22 at
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> May 31 23:14:22 at
>
[GitHub] [flink] flinkbot commented on pull request #17329: [FLINK-24347][connectors/kafka] Keep idle source readers if paralleli…
flinkbot commented on pull request #17329: URL: https://github.com/apache/flink/pull/17329#issuecomment-924078549 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 1187a0d0a8fe25a030e0b3364cc5fafde1132574 (Tue Sep 21 15:05:20 UTC 2021) **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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] fapaul opened a new pull request #17329: [FLINK-24347][connectors/kafka] Keep idle source readers if paralleli…
fapaul opened a new pull request #17329: URL: https://github.com/apache/flink/pull/17329 …sm is higher than partitions in KafkaSource Unchanged backport of #17327 -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #17327: [FLINK-24347][connectors/kafka] Keep idle source readers if paralleli…
flinkbot edited a comment on pull request #17327: URL: https://github.com/apache/flink/pull/17327#issuecomment-923962563 ## CI report: * 9408d97a015235359fba3d97fbc0bf8fda844c61 Azure: [PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24353) * 73c07edc64806c0e9e3d3a7dbffc30eebece0bc2 UNKNOWN * ff7160cbd80d3bc64a2ef0d1e22fb8a28e736ce8 UNKNOWN Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #17328: Group of hotfix commits fixing a couple of things in the tests
flinkbot edited a comment on pull request #17328: URL: https://github.com/apache/flink/pull/17328#issuecomment-924027879 ## CI report: * 7504cd9aae82a742cab6e5dd15bbbf4ab49b3599 Azure: [PENDING](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24359) Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] flinkbot edited a comment on pull request #17319: [FLINK-24329][connector/pulsar] Fix PulsarSourceITCase fails due to port conflict
flinkbot edited a comment on pull request #17319: URL: https://github.com/apache/flink/pull/17319#issuecomment-922249634 ## CI report: * 79d47d6765dfc205b1ff9e5d59e0e3b17c668bd9 UNKNOWN * 0414dbd560746bc38d7933485aae047885beea34 Azure: [SUCCESS](https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=24352) Bot commands The @flinkbot bot supports the following commands: - `@flinkbot run travis` re-run the last Travis build - `@flinkbot run azure` re-run the last Azure build -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] dannycranmer edited a comment on pull request #16513: [FLINK-23389][Formats] Glue schema registry JSON support
dannycranmer edited a comment on pull request #16513: URL: https://github.com/apache/flink/pull/16513#issuecomment-924053719 I would like to verify the e2e tests are passing with Scala 2.12 before merging: - http://mail-archives.apache.org/mod_mbox/flink-dev/202108.mbox/%3ccajnyzn6yj5fry9yoluqma9dnlbkhm5rcetsfizmvg7fd2cr...@mail.gmail.com%3E -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [flink] dannycranmer edited a comment on pull request #16513: [FLINK-23389][Formats] Glue schema registry JSON support
dannycranmer edited a comment on pull request #16513: URL: https://github.com/apache/flink/pull/16513#issuecomment-901125917 ✅ 1. The [description] looks good. ✅ 2. There is [consensus] that the contribution should go into to Flink. _This is a logical improvement to the already existing GSR integration_ ✅ 3. Needs [attention] from. N/A ✅ 4. The change fits into the overall [architecture]. ✅ 5. Overall code [quality] is good. ✅ 6. License check ✅ 7. E2e tests pass ✅ 8. Commit contains the Jira ID **Please squash commits, rebase and add the Jira ID to commit message** -- 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. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
