[jira] [Commented] (FLINK-1815) Add methods to read and write a Graph as adjacency list
[ https://issues.apache.org/jira/browse/FLINK-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392327#comment-14392327 ] Faye Beligianni commented on FLINK-1815: Hello [~vkalavri], I would like to work on this issue for Gelly. It sounds interesting and a good opportunity for me to find out more about Gelly API. Faye Add methods to read and write a Graph as adjacency list --- Key: FLINK-1815 URL: https://issues.apache.org/jira/browse/FLINK-1815 Project: Flink Issue Type: New Feature Components: Gelly Affects Versions: 0.9 Reporter: Vasia Kalavri Priority: Minor It would be nice to add utility methods to read a graph from an Adjacency list format and also write a graph in such a format. The simple case would be to read a graph with no vertex or edge values, where we would need to define (a) a line delimiter, (b) a delimiter to separate vertices from neighbor list and (c) and a delimiter to separate the neighbors. For example, 1 2,3,4\n2 1,3 would give vertex 1 with neighbors 2, 3 and 4 and vertex 2 with neighbors 1 and 3. If we have vertex values and/or edge values, we also need to have a way to separate IDs from values. For example, we could have 1 0.1 2 0.5, 3 0.2 to define a vertex 1 with value 0.1, edge (1, 2) with weight 0.5 and edge (1, 3) with weight 0.2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FLINK-1753) Add more tests for Kafka Connectors
[
https://issues.apache.org/jira/browse/FLINK-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Metzger updated FLINK-1753:
--
Description:
The current {{KafkaITCase}} is only doing a single test.
We need to refactor that test so that it brings up a Kafka/Zookeeper server and
than performs various tests:
Tests to include:
- A topology with non-string types MERGED IN 359b39c3
- A topology with a custom Kafka Partitioning class MERGED IN 359b39c3
- A topology testing the regular {{KafkaSource}}. MERGED IN 359b39c3
- Kafka broker failure.
- Flink TaskManager failure
was:
The current {{KafkaITCase}} is only doing a single test.
We need to refactor that test so that it brings up a Kafka/Zookeeper server and
than performs various tests:
Tests to include:
- A topology with non-string types
- A topology with a custom Kafka Partitioning class
- A topology testing the regular {{KafkaSource}}.
- Kafka broker failure.
Add more tests for Kafka Connectors
---
Key: FLINK-1753
URL: https://issues.apache.org/jira/browse/FLINK-1753
Project: Flink
Issue Type: Improvement
Components: Streaming
Affects Versions: 0.9
Reporter: Robert Metzger
Assignee: Gábor Hermann
The current {{KafkaITCase}} is only doing a single test.
We need to refactor that test so that it brings up a Kafka/Zookeeper server
and than performs various tests:
Tests to include:
- A topology with non-string types MERGED IN 359b39c3
- A topology with a custom Kafka Partitioning class MERGED IN 359b39c3
- A topology testing the regular {{KafkaSource}}. MERGED IN 359b39c3
- Kafka broker failure.
- Flink TaskManager failure
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FLINK-1815) Add methods to read and write a Graph as adjacency list
[ https://issues.apache.org/jira/browse/FLINK-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392377#comment-14392377 ] Vasia Kalavri commented on FLINK-1815: -- Thanks [~fobeligi]! I'll assign it to you then. Let me know if you have any questions :) Add methods to read and write a Graph as adjacency list --- Key: FLINK-1815 URL: https://issues.apache.org/jira/browse/FLINK-1815 Project: Flink Issue Type: New Feature Components: Gelly Affects Versions: 0.9 Reporter: Vasia Kalavri Priority: Minor It would be nice to add utility methods to read a graph from an Adjacency list format and also write a graph in such a format. The simple case would be to read a graph with no vertex or edge values, where we would need to define (a) a line delimiter, (b) a delimiter to separate vertices from neighbor list and (c) and a delimiter to separate the neighbors. For example, 1 2,3,4\n2 1,3 would give vertex 1 with neighbors 2, 3 and 4 and vertex 2 with neighbors 1 and 3. If we have vertex values and/or edge values, we also need to have a way to separate IDs from values. For example, we could have 1 0.1 2 0.5, 3 0.2 to define a vertex 1 with value 0.1, edge (1, 2) with weight 0.5 and edge (1, 3) with weight 0.2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] flink pull request: [docs] Add custom search (backport)
GitHub user uce opened a pull request: https://github.com/apache/flink/pull/564 [docs] Add custom search (backport) This is #563 for release-0.8. The separate docs URL needs a separate custom search. You can merge this pull request into a Git repository by running: $ git pull https://github.com/uce/incubator-flink docs_search-0.8 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/flink/pull/564.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #564 commit 179d2fec8426558b7724fb6af0d6a41630ab79eb Author: Ufuk Celebi u...@apache.org Date: 2015-04-02T09:20:15Z [docs] Add custom search (backport) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (FLINK-1816) DegreesWithExceptionITCase.testGetDegreesInvalidEdgeSrcId fails with wrong exception
[
https://issues.apache.org/jira/browse/FLINK-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392462#comment-14392462
]
ASF GitHub Bot commented on FLINK-1816:
---
Github user vasia commented on the pull request:
https://github.com/apache/flink/pull/562#issuecomment-88851563
wow that was quick :)) Thanks a lot @tillrohrmann!
DegreesWithExceptionITCase.testGetDegreesInvalidEdgeSrcId fails with wrong
exception
Key: FLINK-1816
URL: https://issues.apache.org/jira/browse/FLINK-1816
Project: Flink
Issue Type: Bug
Components: Gelly
Reporter: Till Rohrmann
Assignee: Till Rohrmann
In one of the Travis builds [1] I noticed that the
{{DegreesWithExceptionITCase.testGetDegreesInvalidEdgeSrcId}} test case fails
because it receives a wrong exception.
[1] [https://travis-ci.org/apache/flink/jobs/56738202]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] flink pull request: [FLINK-1716] Adds CoCoA algorithm
Github user tillrohrmann commented on the pull request: https://github.com/apache/flink/pull/545#issuecomment-88820531 Travis failed because of some Gelly test case. Travis running on my own repo passed, though. I'll merge the PR then. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (FLINK-1816) DegreesWithExceptionITCase.testGetDegreesInvalidEdgeSrcId fails with wrong exception
Till Rohrmann created FLINK-1816:
Summary: DegreesWithExceptionITCase.testGetDegreesInvalidEdgeSrcId
fails with wrong exception
Key: FLINK-1816
URL: https://issues.apache.org/jira/browse/FLINK-1816
Project: Flink
Issue Type: Bug
Components: Gelly
Reporter: Till Rohrmann
In one of the Travis builds [1] I notices that the
{{DegreesWithExceptionITCase.testGetDegreesInvalidEdgeSrcId}} test case fails
because it receives a wrong exception.
[1] [https://travis-ci.org/apache/flink/jobs/56738202]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] flink pull request: [FLINK-1792] TM Monitoring: CPU utilization, h...
Github user rmetzger commented on the pull request: https://github.com/apache/flink/pull/553#issuecomment-88828965 Please let me know when the PR is ready for review again. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (FLINK-1753) Add more tests for Kafka Connectors
[
https://issues.apache.org/jira/browse/FLINK-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392354#comment-14392354
]
ASF GitHub Bot commented on FLINK-1753:
---
Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/557
Add more tests for Kafka Connectors
---
Key: FLINK-1753
URL: https://issues.apache.org/jira/browse/FLINK-1753
Project: Flink
Issue Type: Improvement
Components: Streaming
Affects Versions: 0.9
Reporter: Robert Metzger
The current {{KafkaITCase}} is only doing a single test.
We need to refactor that test so that it brings up a Kafka/Zookeeper server
and than performs various tests:
Tests to include:
- A topology with non-string types
- A topology with a custom Kafka Partitioning class
- A topology testing the regular {{KafkaSource}}.
- Kafka broker failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] flink pull request: [FLINK-1753] [streaming] Added test for Kafka ...
Github user asfgit closed the pull request at: https://github.com/apache/flink/pull/557 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (FLINK-1589) Add option to pass Configuration to LocalExecutor
[ https://issues.apache.org/jira/browse/FLINK-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392353#comment-14392353 ] ASF GitHub Bot commented on FLINK-1589: --- Github user asfgit closed the pull request at: https://github.com/apache/flink/pull/427 Add option to pass Configuration to LocalExecutor - Key: FLINK-1589 URL: https://issues.apache.org/jira/browse/FLINK-1589 Project: Flink Issue Type: New Feature Reporter: Robert Metzger Assignee: Robert Metzger Right now its not possible for users to pass custom configuration values to Flink when running it from within an IDE. It would be very convenient to be able to create a local execution environment that allows passing configuration files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLINK-1792) Improve TM Monitoring: CPU utilization, hide graphs by default and show summary only
[ https://issues.apache.org/jira/browse/FLINK-1792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392389#comment-14392389 ] ASF GitHub Bot commented on FLINK-1792: --- Github user rmetzger commented on the pull request: https://github.com/apache/flink/pull/553#issuecomment-88828965 Please let me know when the PR is ready for review again. Improve TM Monitoring: CPU utilization, hide graphs by default and show summary only Key: FLINK-1792 URL: https://issues.apache.org/jira/browse/FLINK-1792 Project: Flink Issue Type: Sub-task Components: Webfrontend Affects Versions: 0.9 Reporter: Robert Metzger Assignee: Sachin Bhat As per https://github.com/apache/flink/pull/421 from FLINK-1501, there are some enhancements to the current monitoring required - Get the CPU utilization in % from each TaskManager process - Remove the metrics graph from the overview and only show the current stats as numbers (cpu load, heap utilization) and add a button to enable the detailed graph. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLINK-1716) Add CoCoA algorithm to flink-ml
[ https://issues.apache.org/jira/browse/FLINK-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392405#comment-14392405 ] ASF GitHub Bot commented on FLINK-1716: --- Github user vasia commented on the pull request: https://github.com/apache/flink/pull/545#issuecomment-88834217 Hi @tillrohrmann! Thanks for the heads up :) The failing test is `DegreesWithExceptionITCase` and it seems that it fails because of not throwing the excepted exception type. We had a discussion about this in #475 and if I get it correctly, we can't be sure which exception will be reported to the client, because of the job cancelling. Thus, we removed the check of the exception type and message and only checked for failure. However, I see you added some exception checks in 36b762e. So, I'm not sure what we're supposed to do with this test now, so that it doesn't fail o.O Add CoCoA algorithm to flink-ml --- Key: FLINK-1716 URL: https://issues.apache.org/jira/browse/FLINK-1716 Project: Flink Issue Type: New Feature Components: Machine Learning Library Reporter: Till Rohrmann Assignee: Till Rohrmann Labels: ML Add the communication efficient distributed dual coordinate ascent algorithm to the flink machine learning library. See [CoCoA|http://arxiv.org/pdf/1409.1458.pdf] for the implementation details. I propose to first implement it with hinge loss and l2-norm. This way, it will allow us to train SVMs in parallel. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] flink pull request: [FLINK-1716] Adds CoCoA algorithm
Github user vasia commented on the pull request: https://github.com/apache/flink/pull/545#issuecomment-88834217 Hi @tillrohrmann! Thanks for the heads up :) The failing test is `DegreesWithExceptionITCase` and it seems that it fails because of not throwing the excepted exception type. We had a discussion about this in #475 and if I get it correctly, we can't be sure which exception will be reported to the client, because of the job cancelling. Thus, we removed the check of the exception type and message and only checked for failure. However, I see you added some exception checks in 36b762e. So, I'm not sure what we're supposed to do with this test now, so that it doesn't fail o.O --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (FLINK-1716) Add CoCoA algorithm to flink-ml
[ https://issues.apache.org/jira/browse/FLINK-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392418#comment-14392418 ] ASF GitHub Bot commented on FLINK-1716: --- Github user tillrohrmann commented on the pull request: https://github.com/apache/flink/pull/545#issuecomment-88836418 Oh ok, I was not aware of #475. I just added the additional checks because of the fail message in the try block that you expect a ```NoSuchElementException```. If this is not a case, then we can just adapt the fail message and revert the additional checks I've introduced. Sorry for screwing up your test cases. Add CoCoA algorithm to flink-ml --- Key: FLINK-1716 URL: https://issues.apache.org/jira/browse/FLINK-1716 Project: Flink Issue Type: New Feature Components: Machine Learning Library Reporter: Till Rohrmann Assignee: Till Rohrmann Labels: ML Add the communication efficient distributed dual coordinate ascent algorithm to the flink machine learning library. See [CoCoA|http://arxiv.org/pdf/1409.1458.pdf] for the implementation details. I propose to first implement it with hinge loss and l2-norm. This way, it will allow us to train SVMs in parallel. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] flink pull request: [FLINK-1716] Adds CoCoA algorithm
Github user tillrohrmann commented on the pull request: https://github.com/apache/flink/pull/545#issuecomment-88836418 Oh ok, I was not aware of #475. I just added the additional checks because of the fail message in the try block that you expect a ```NoSuchElementException```. If this is not a case, then we can just adapt the fail message and revert the additional checks I've introduced. Sorry for screwing up your test cases. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (FLINK-1816) DegreesWithExceptionITCase.testGetDegreesInvalidEdgeSrcId fails with wrong exception
[
https://issues.apache.org/jira/browse/FLINK-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann updated FLINK-1816:
-
Description:
In one of the Travis builds [1] I noticed that the
{{DegreesWithExceptionITCase.testGetDegreesInvalidEdgeSrcId}} test case fails
because it receives a wrong exception.
[1] [https://travis-ci.org/apache/flink/jobs/56738202]
was:
In one of the Travis builds [1] I notices that the
{{DegreesWithExceptionITCase.testGetDegreesInvalidEdgeSrcId}} test case fails
because it receives a wrong exception.
[1] [https://travis-ci.org/apache/flink/jobs/56738202]
DegreesWithExceptionITCase.testGetDegreesInvalidEdgeSrcId fails with wrong
exception
Key: FLINK-1816
URL: https://issues.apache.org/jira/browse/FLINK-1816
Project: Flink
Issue Type: Bug
Components: Gelly
Reporter: Till Rohrmann
Assignee: Till Rohrmann
In one of the Travis builds [1] I noticed that the
{{DegreesWithExceptionITCase.testGetDegreesInvalidEdgeSrcId}} test case fails
because it receives a wrong exception.
[1] [https://travis-ci.org/apache/flink/jobs/56738202]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] flink pull request: [FLINK-1816] Fixes wrongly introduced exceptio...
GitHub user tillrohrmann opened a pull request: https://github.com/apache/flink/pull/562 [FLINK-1816] Fixes wrongly introduced exception checks in DegreesWithExceptionITCase I wrongly introduced exception type checks in the ```DegreesWithExceptionITCase``` which are corrected with this PR. See #475 for more details. You can merge this pull request into a Git repository by running: $ git pull https://github.com/tillrohrmann/flink fixDegreesWithExceptionITCase Alternatively you can review and apply these changes as the patch at: https://github.com/apache/flink/pull/562.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #562 commit 10d20bff289ea5f27e4c04b49a4dcb349fbf6ce6 Author: Till Rohrmann trohrm...@apache.org Date: 2015-04-02T09:28:38Z [FLINK-1816] [gelly tests] Fixes wrongly introduced exception checks in DegreesWithExceptionITCase --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (FLINK-1753) Add more tests for Kafka Connectors
[
https://issues.apache.org/jira/browse/FLINK-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392293#comment-14392293
]
ASF GitHub Bot commented on FLINK-1753:
---
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/557#issuecomment-88794220
I'm merging this PR
Add more tests for Kafka Connectors
---
Key: FLINK-1753
URL: https://issues.apache.org/jira/browse/FLINK-1753
Project: Flink
Issue Type: Improvement
Components: Streaming
Affects Versions: 0.9
Reporter: Robert Metzger
The current {{KafkaITCase}} is only doing a single test.
We need to refactor that test so that it brings up a Kafka/Zookeeper server
and than performs various tests:
Tests to include:
- A topology with non-string types
- A topology with a custom Kafka Partitioning class
- A topology testing the regular {{KafkaSource}}.
- Kafka broker failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] flink pull request: [FLINK-1589] Add option to pass configuration ...
Github user rmetzger commented on the pull request: https://github.com/apache/flink/pull/427#issuecomment-88794279 I'm merging this PR --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (FLINK-1815) Add methods to read and write a Graph as adjacency list
[ https://issues.apache.org/jira/browse/FLINK-1815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vasia Kalavri updated FLINK-1815: - Assignee: Faye Beligianni Add methods to read and write a Graph as adjacency list --- Key: FLINK-1815 URL: https://issues.apache.org/jira/browse/FLINK-1815 Project: Flink Issue Type: New Feature Components: Gelly Affects Versions: 0.9 Reporter: Vasia Kalavri Assignee: Faye Beligianni Priority: Minor It would be nice to add utility methods to read a graph from an Adjacency list format and also write a graph in such a format. The simple case would be to read a graph with no vertex or edge values, where we would need to define (a) a line delimiter, (b) a delimiter to separate vertices from neighbor list and (c) and a delimiter to separate the neighbors. For example, 1 2,3,4\n2 1,3 would give vertex 1 with neighbors 2, 3 and 4 and vertex 2 with neighbors 1 and 3. If we have vertex values and/or edge values, we also need to have a way to separate IDs from values. For example, we could have 1 0.1 2 0.5, 3 0.2 to define a vertex 1 with value 0.1, edge (1, 2) with weight 0.5 and edge (1, 3) with weight 0.2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] flink pull request: [FLINK-1777] [docs] Update Java 8 Lambdas with...
Github user rmetzger commented on the pull request: https://github.com/apache/flink/pull/528#issuecomment-88828235 I'm merging this PR. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (FLINK-1814) Revisit the documentation to add new operator
[ https://issues.apache.org/jira/browse/FLINK-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392435#comment-14392435 ] Maximilian Michels commented on FLINK-1814: --- +1 It's not totally outdated but not exhaustive either. Revisit the documentation to add new operator - Key: FLINK-1814 URL: https://issues.apache.org/jira/browse/FLINK-1814 Project: Flink Issue Type: Bug Components: Documentation Reporter: Henry Saputra The doc to describe adding new operator seem to have broken links and may not be accurate anymore [1] This ticket is filed to revisit the doc and update it if necessary [1] http://ci.apache.org/projects/flink/flink-docs-master/internal_add_operator.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] flink pull request: [FLINK-1589] Add option to pass configuration ...
Github user asfgit closed the pull request at: https://github.com/apache/flink/pull/427 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (FLINK-1716) Add CoCoA algorithm to flink-ml
[ https://issues.apache.org/jira/browse/FLINK-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392364#comment-14392364 ] ASF GitHub Bot commented on FLINK-1716: --- Github user tillrohrmann commented on the pull request: https://github.com/apache/flink/pull/545#issuecomment-88820531 Travis failed because of some Gelly test case. Travis running on my own repo passed, though. I'll merge the PR then. Add CoCoA algorithm to flink-ml --- Key: FLINK-1716 URL: https://issues.apache.org/jira/browse/FLINK-1716 Project: Flink Issue Type: New Feature Components: Machine Learning Library Reporter: Till Rohrmann Assignee: Till Rohrmann Labels: ML Add the communication efficient distributed dual coordinate ascent algorithm to the flink machine learning library. See [CoCoA|http://arxiv.org/pdf/1409.1458.pdf] for the implementation details. I propose to first implement it with hinge loss and l2-norm. This way, it will allow us to train SVMs in parallel. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] flink pull request: [FLINK-1816] Fixes wrongly introduced exceptio...
Github user vasia commented on the pull request: https://github.com/apache/flink/pull/562#issuecomment-88851563 wow that was quick :)) Thanks a lot @tillrohrmann! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (FLINK-1815) Add methods to read and write a Graph as adjacency list
Vasia Kalavri created FLINK-1815: Summary: Add methods to read and write a Graph as adjacency list Key: FLINK-1815 URL: https://issues.apache.org/jira/browse/FLINK-1815 Project: Flink Issue Type: New Feature Components: Gelly Affects Versions: 0.9 Reporter: Vasia Kalavri Priority: Minor It would be nice to add utility methods to read a graph from an Adjacency list format and also write a graph in such a format. The simple case would be to read a graph with no vertex or edge values, where we would need to define (a) a line delimiter, (b) a delimiter to separate vertices from neighbor list and (c) and a delimiter to separate the neighbors. For example, 1 2,3,4\n2 1,3 would give vertex 1 with neighbors 2, 3 and 4 and vertex 2 with neighbors 1 and 3. If we have vertex values and/or edge values, we also need to have a way to separate IDs from values. For example, we could have 1 0.1 2 0.5, 3 0.2 to define a vertex 1 with value 0.1, edge (1, 2) with weight 0.5 and edge (1, 3) with weight 0.2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] flink pull request: [FLINK-1753] [streaming] Added test for Kafka ...
Github user rmetzger commented on the pull request: https://github.com/apache/flink/pull/557#issuecomment-88794220 I'm merging this PR --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (FLINK-1589) Add option to pass Configuration to LocalExecutor
[ https://issues.apache.org/jira/browse/FLINK-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392294#comment-14392294 ] ASF GitHub Bot commented on FLINK-1589: --- Github user rmetzger commented on the pull request: https://github.com/apache/flink/pull/427#issuecomment-88794279 I'm merging this PR Add option to pass Configuration to LocalExecutor - Key: FLINK-1589 URL: https://issues.apache.org/jira/browse/FLINK-1589 Project: Flink Issue Type: New Feature Reporter: Robert Metzger Assignee: Robert Metzger Right now its not possible for users to pass custom configuration values to Flink when running it from within an IDE. It would be very convenient to be able to create a local execution environment that allows passing configuration files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FLINK-1589) Add option to pass Configuration to LocalExecutor
[ https://issues.apache.org/jira/browse/FLINK-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Metzger resolved FLINK-1589. --- Resolution: Fixed Fix Version/s: 0.9 Resolved in http://git-wip-us.apache.org/repos/asf/flink/commit/7cf95862. Add option to pass Configuration to LocalExecutor - Key: FLINK-1589 URL: https://issues.apache.org/jira/browse/FLINK-1589 Project: Flink Issue Type: New Feature Components: Java API, Scala API Reporter: Robert Metzger Assignee: Robert Metzger Fix For: 0.9 Right now its not possible for users to pass custom configuration values to Flink when running it from within an IDE. It would be very convenient to be able to create a local execution environment that allows passing configuration files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FLINK-1589) Add option to pass Configuration to LocalExecutor
[ https://issues.apache.org/jira/browse/FLINK-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Metzger updated FLINK-1589: -- Component/s: Scala API Java API Add option to pass Configuration to LocalExecutor - Key: FLINK-1589 URL: https://issues.apache.org/jira/browse/FLINK-1589 Project: Flink Issue Type: New Feature Components: Java API, Scala API Reporter: Robert Metzger Assignee: Robert Metzger Fix For: 0.9 Right now its not possible for users to pass custom configuration values to Flink when running it from within an IDE. It would be very convenient to be able to create a local execution environment that allows passing configuration files. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLINK-1753) Add more tests for Kafka Connectors
[
https://issues.apache.org/jira/browse/FLINK-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392357#comment-14392357
]
Robert Metzger commented on FLINK-1753:
---
First tests merged in
http://git-wip-us.apache.org/repos/asf/flink/commit/359b39c3
Add more tests for Kafka Connectors
---
Key: FLINK-1753
URL: https://issues.apache.org/jira/browse/FLINK-1753
Project: Flink
Issue Type: Improvement
Components: Streaming
Affects Versions: 0.9
Reporter: Robert Metzger
The current {{KafkaITCase}} is only doing a single test.
We need to refactor that test so that it brings up a Kafka/Zookeeper server
and than performs various tests:
Tests to include:
- A topology with non-string types
- A topology with a custom Kafka Partitioning class
- A topology testing the regular {{KafkaSource}}.
- Kafka broker failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FLINK-1753) Add more tests for Kafka Connectors
[
https://issues.apache.org/jira/browse/FLINK-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Metzger updated FLINK-1753:
--
Assignee: Gábor Hermann
Add more tests for Kafka Connectors
---
Key: FLINK-1753
URL: https://issues.apache.org/jira/browse/FLINK-1753
Project: Flink
Issue Type: Improvement
Components: Streaming
Affects Versions: 0.9
Reporter: Robert Metzger
Assignee: Gábor Hermann
The current {{KafkaITCase}} is only doing a single test.
We need to refactor that test so that it brings up a Kafka/Zookeeper server
and than performs various tests:
Tests to include:
- A topology with non-string types
- A topology with a custom Kafka Partitioning class
- A topology testing the regular {{KafkaSource}}.
- Kafka broker failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] flink pull request: [FLINK-1777] [docs] Update Java 8 Lambdas with...
Github user asfgit closed the pull request at: https://github.com/apache/flink/pull/528 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (FLINK-1777) Update Java 8 Lambdas with Eclipse documentation
[ https://issues.apache.org/jira/browse/FLINK-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392384#comment-14392384 ] ASF GitHub Bot commented on FLINK-1777: --- Github user rmetzger commented on the pull request: https://github.com/apache/flink/pull/528#issuecomment-88828235 I'm merging this PR. Update Java 8 Lambdas with Eclipse documentation Key: FLINK-1777 URL: https://issues.apache.org/jira/browse/FLINK-1777 Project: Flink Issue Type: Bug Components: Documentation Reporter: Timo Walther Assignee: Timo Walther Priority: Minor The Eclipse JDT compiler team has introduced a compiler flag for us, which is not covered in the Flink documentation yet. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FLINK-1777) Update Java 8 Lambdas with Eclipse documentation
[ https://issues.apache.org/jira/browse/FLINK-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Metzger resolved FLINK-1777. --- Resolution: Fixed Fix Version/s: 0.9 Merged in http://git-wip-us.apache.org/repos/asf/flink/commit/57e9ae0b Update Java 8 Lambdas with Eclipse documentation Key: FLINK-1777 URL: https://issues.apache.org/jira/browse/FLINK-1777 Project: Flink Issue Type: Bug Components: Documentation Reporter: Timo Walther Assignee: Timo Walther Priority: Minor Fix For: 0.9 The Eclipse JDT compiler team has introduced a compiler flag for us, which is not covered in the Flink documentation yet. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLINK-1777) Update Java 8 Lambdas with Eclipse documentation
[ https://issues.apache.org/jira/browse/FLINK-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392386#comment-14392386 ] ASF GitHub Bot commented on FLINK-1777: --- Github user asfgit closed the pull request at: https://github.com/apache/flink/pull/528 Update Java 8 Lambdas with Eclipse documentation Key: FLINK-1777 URL: https://issues.apache.org/jira/browse/FLINK-1777 Project: Flink Issue Type: Bug Components: Documentation Reporter: Timo Walther Assignee: Timo Walther Priority: Minor Fix For: 0.9 The Eclipse JDT compiler team has introduced a compiler flag for us, which is not covered in the Flink documentation yet. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] flink pull request: [FLINK-1716] Adds CoCoA algorithm
Github user asfgit closed the pull request at: https://github.com/apache/flink/pull/545 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] flink pull request: [FLINK-1816] Fixes wrongly introduced exceptio...
Github user uce commented on the pull request: https://github.com/apache/flink/pull/562#issuecomment-88850486 Good to merge. This was probably just a mistake during a merge. ;) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Created] (FLINK-1814) Revisit the documentation to add new operator
Henry Saputra created FLINK-1814: Summary: Revisit the documentation to add new operator Key: FLINK-1814 URL: https://issues.apache.org/jira/browse/FLINK-1814 Project: Flink Issue Type: Bug Components: Documentation Reporter: Henry Saputra The doc to describe adding new operator seem to have broken links and may not be accurate anymore [1] This ticket is filed to revisit the doc and update it if necessary [1] http://ci.apache.org/projects/flink/flink-docs-master/internal_add_operator.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (FLINK-1816) DegreesWithExceptionITCase.testGetDegreesInvalidEdgeSrcId fails with wrong exception
[
https://issues.apache.org/jira/browse/FLINK-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann reassigned FLINK-1816:
Assignee: Till Rohrmann
DegreesWithExceptionITCase.testGetDegreesInvalidEdgeSrcId fails with wrong
exception
Key: FLINK-1816
URL: https://issues.apache.org/jira/browse/FLINK-1816
Project: Flink
Issue Type: Bug
Components: Gelly
Reporter: Till Rohrmann
Assignee: Till Rohrmann
In one of the Travis builds [1] I notices that the
{{DegreesWithExceptionITCase.testGetDegreesInvalidEdgeSrcId}} test case fails
because it receives a wrong exception.
[1] [https://travis-ci.org/apache/flink/jobs/56738202]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FLINK-1816) DegreesWithExceptionITCase.testGetDegreesInvalidEdgeSrcId fails with wrong exception
[
https://issues.apache.org/jira/browse/FLINK-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392459#comment-14392459
]
ASF GitHub Bot commented on FLINK-1816:
---
Github user uce commented on the pull request:
https://github.com/apache/flink/pull/562#issuecomment-88850486
Good to merge. This was probably just a mistake during a merge. ;)
DegreesWithExceptionITCase.testGetDegreesInvalidEdgeSrcId fails with wrong
exception
Key: FLINK-1816
URL: https://issues.apache.org/jira/browse/FLINK-1816
Project: Flink
Issue Type: Bug
Components: Gelly
Reporter: Till Rohrmann
Assignee: Till Rohrmann
In one of the Travis builds [1] I noticed that the
{{DegreesWithExceptionITCase.testGetDegreesInvalidEdgeSrcId}} test case fails
because it receives a wrong exception.
[1] [https://travis-ci.org/apache/flink/jobs/56738202]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FLINK-1820) Bug in DoubleParser and FloatParser - empty String is not casted to 0
[ https://issues.apache.org/jira/browse/FLINK-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Neutatz updated FLINK-1820: - Description: Hi, I found the bug, when I wanted to read a csv file, which had a line like: ||\n If I treat it as a Tuple2Long,Long, I get as expected a tuple (0L,0L). But if I want to read it into a Double-Tuple or a Float-Tuple, I get the following error: java.lang.AssertionError: Test failed due to a org.apache.flink.api.common.io.ParseException: Line could not be parsed: '||' ParserError NUMERIC_VALUE_FORMAT_ERROR This error can be solved by adding an additional condition for empty strings in the FloatParser / DoubleParser. We definitely need the CSVReader to be able to read empty values. I can fix it like described if there are no better ideas :) was: Hi, I found the bug, when I wanted to read a csv file, which had a line like: ||\n If I treat it as a Tuple2Long,Long, I get as expected a tuple (0L,0L). But if I want to read it into a Double-Tuple or a Float-Tuple, I get the following error: java.lang.AssertionError: Test failed due to a org.apache.flink.api.common.io.ParseException: Line could not be parsed: '||' ParserError NUMERIC_VALUE_FORMAT_ERROR This error can be solved by adding an additional condition for empty strings in the FloatParser / DoubleParser. We definitly need the CSVReader to be able to read empty values. I can fix it like described if there are no better ideas :) Bug in DoubleParser and FloatParser - empty String is not casted to 0 - Key: FLINK-1820 URL: https://issues.apache.org/jira/browse/FLINK-1820 Project: Flink Issue Type: Bug Components: core Affects Versions: 0.8.0, 0.9, 0.8.1 Reporter: Felix Neutatz Assignee: Felix Neutatz Priority: Critical Fix For: 0.9 Hi, I found the bug, when I wanted to read a csv file, which had a line like: ||\n If I treat it as a Tuple2Long,Long, I get as expected a tuple (0L,0L). But if I want to read it into a Double-Tuple or a Float-Tuple, I get the following error: java.lang.AssertionError: Test failed due to a org.apache.flink.api.common.io.ParseException: Line could not be parsed: '||' ParserError NUMERIC_VALUE_FORMAT_ERROR This error can be solved by adding an additional condition for empty strings in the FloatParser / DoubleParser. We definitely need the CSVReader to be able to read empty values. I can fix it like described if there are no better ideas :) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FLINK-1820) Bug in DoubleParser and FloatParser - empty String is not casted to 0
Felix Neutatz created FLINK-1820: Summary: Bug in DoubleParser and FloatParser - empty String is not casted to 0 Key: FLINK-1820 URL: https://issues.apache.org/jira/browse/FLINK-1820 Project: Flink Issue Type: Bug Components: core Affects Versions: 0.8.1, 0.8.0, 0.9 Reporter: Felix Neutatz Assignee: Felix Neutatz Priority: Critical Fix For: 0.9 Hi, I found the bug, when I wanted to read a csv file, which had a line like: ||\n If I treat it as a Tuple2Long,Long, I get as expected a tuple (0L,0L). But if I want to read it into a Double-Tuple or a Float-Tuple, I get the following error: java.lang.AssertionError: Test failed due to a org.apache.flink.api.common.io.ParseException: Line could not be parsed: '||' ParserError NUMERIC_VALUE_FORMAT_ERROR This error can be solved by adding an additional condition for empty strings in the FloatParser / DoubleParser. We definitly need the CSVReader to be able to read empty values. I can fix it like described if there are no better ideas :) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLINK-1664) Forbid sorting on POJOs
[
https://issues.apache.org/jira/browse/FLINK-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14394070#comment-14394070
]
ASF GitHub Bot commented on FLINK-1664:
---
Github user hsaputra commented on a diff in the pull request:
https://github.com/apache/flink/pull/541#discussion_r27715729
--- Diff:
flink-java/src/main/java/org/apache/flink/api/java/operators/DataSink.java ---
@@ -208,6 +214,28 @@ public DataSink(DataSetT data, OutputFormatT
format, TypeInformationT type
return this;
}
+ private void isValidSortKeyType(int field) {
--- End diff --
There are repeating yet similar code for isValidSortKeyType methods to
check if sortable. Could the code be moved to utility class to be reused/
shared?
Forbid sorting on POJOs
---
Key: FLINK-1664
URL: https://issues.apache.org/jira/browse/FLINK-1664
Project: Flink
Issue Type: Bug
Components: JobManager
Affects Versions: 0.8.0, 0.9
Reporter: Fabian Hueske
Assignee: Fabian Hueske
Flink's groupSort, partitionSort, and outputSort operators allow to sort
partitions or groups of a DataSet.
If the sort is defined on a POJO field, the sort order is not well defined.
Internally, the POJO is recursively decomposed into atomic fields (primitives
or generic types) and sorted by sorting these atomic fields. Thereby, the
order of these atomic fields is not well defined (I believe it is
lexicographic order of the POJO's member names).
IMO, the best approach is to forbid sorting on POJO types for now. Instead,
it is always possible to select the nested fields of the POJO that should be
used for sorting. Later we can relax this restriction.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] flink pull request: [FLINK-1664] Adds checks if selected sort key ...
Github user hsaputra commented on a diff in the pull request:
https://github.com/apache/flink/pull/541#discussion_r27715729
--- Diff:
flink-java/src/main/java/org/apache/flink/api/java/operators/DataSink.java ---
@@ -208,6 +214,28 @@ public DataSink(DataSetT data, OutputFormatT
format, TypeInformationT type
return this;
}
+ private void isValidSortKeyType(int field) {
--- End diff --
There are repeating yet similar code for isValidSortKeyType methods to
check if sortable. Could the code be moved to utility class to be reused/
shared?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
[jira] [Commented] (FLINK-1656) Filtered Semantic Properties for Operators with Iterators
[ https://issues.apache.org/jira/browse/FLINK-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14393167#comment-14393167 ] ASF GitHub Bot commented on FLINK-1656: --- Github user fhueske commented on the pull request: https://github.com/apache/flink/pull/525#issuecomment-89009870 Will merge this in about 24h unless somebody raises a flag. Filtered Semantic Properties for Operators with Iterators - Key: FLINK-1656 URL: https://issues.apache.org/jira/browse/FLINK-1656 Project: Flink Issue Type: Bug Components: Documentation Affects Versions: 0.9 Reporter: Fabian Hueske Assignee: Fabian Hueske Priority: Critical The documentation of ForwardedFields is incomplete for operators with iterator inputs (GroupReduce, CoGroup). This should be fixed ASAP, because it can lead to incorrect program execution. The conditions for forwarded fields on operators with iterator input are: 1) forwarded fields must be emitted in the order in which they are received through the iterator 2) all forwarded fields of a record must stick together, i.e., if your function builds record from field 0 of the 1st, 3rd, 5th, ... and field 1 of the 2nd, 4th, ... record coming through the iterator, these are not valid forwarded fields. 3) it is OK to completely filter out records coming through the iterator. The reason for these conditions is that the optimizer uses forwarded fields to reason about physical data properties such as order and grouping. Mixing up the order of records or emitting records which are composed from different input records, might destroy a (secondary) order or grouping. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] flink pull request: [FLINK-1664] Adds checks if selected sort key ...
Github user fhueske commented on the pull request: https://github.com/apache/flink/pull/541#issuecomment-89010189 Will rebase and merge this in about 24h unless somebody raises a flag. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] flink pull request: [FLINK-1776] Add offsets to field indexes of s...
Github user fhueske commented on the pull request: https://github.com/apache/flink/pull/532#issuecomment-89010020 Will rebase and merge this in about 24h unless somebody raises a flag. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (FLINK-1776) APIs provide invalid Semantic Properties for Operators with SelectorFunction keys
[ https://issues.apache.org/jira/browse/FLINK-1776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14393169#comment-14393169 ] ASF GitHub Bot commented on FLINK-1776: --- Github user fhueske commented on the pull request: https://github.com/apache/flink/pull/532#issuecomment-89010020 Will rebase and merge this in about 24h unless somebody raises a flag. APIs provide invalid Semantic Properties for Operators with SelectorFunction keys - Key: FLINK-1776 URL: https://issues.apache.org/jira/browse/FLINK-1776 Project: Flink Issue Type: Bug Components: Java API, Scala API Affects Versions: 0.9 Reporter: Fabian Hueske Assignee: Fabian Hueske Priority: Critical Fix For: 0.9 Semantic properties are defined by users and evaluated by the optimizer. When semantic properties such as forwarded or read fields are bound to the input type of a function. In case of operators with selector function keys, a user function is wrapped by a wrapping function that has a different input types than the original user function. However, the user-defined semantic properties are verbatim forwarded to the optimizer. Since the properties refer to a specific type which is changed by the wrapping function and the semantic properties are not adapted, the optimizer uses wrong properties and might produce invalid plans -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLINK-1664) Forbid sorting on POJOs
[ https://issues.apache.org/jira/browse/FLINK-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14393170#comment-14393170 ] ASF GitHub Bot commented on FLINK-1664: --- Github user fhueske commented on the pull request: https://github.com/apache/flink/pull/541#issuecomment-89010189 Will rebase and merge this in about 24h unless somebody raises a flag. Forbid sorting on POJOs --- Key: FLINK-1664 URL: https://issues.apache.org/jira/browse/FLINK-1664 Project: Flink Issue Type: Bug Components: JobManager Affects Versions: 0.8.0, 0.9 Reporter: Fabian Hueske Assignee: Fabian Hueske Flink's groupSort, partitionSort, and outputSort operators allow to sort partitions or groups of a DataSet. If the sort is defined on a POJO field, the sort order is not well defined. Internally, the POJO is recursively decomposed into atomic fields (primitives or generic types) and sorted by sorting these atomic fields. Thereby, the order of these atomic fields is not well defined (I believe it is lexicographic order of the POJO's member names). IMO, the best approach is to forbid sorting on POJO types for now. Instead, it is always possible to select the nested fields of the POJO that should be used for sorting. Later we can relax this restriction. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FLINK-1818) Provide API to cancel running job
Robert Metzger created FLINK-1818: - Summary: Provide API to cancel running job Key: FLINK-1818 URL: https://issues.apache.org/jira/browse/FLINK-1818 Project: Flink Issue Type: Improvement Components: Java API Affects Versions: 0.9 Reporter: Robert Metzger http://apache-flink-incubator-mailing-list-archive.1008284.n3.nabble.com/Canceling-a-Cluster-Job-from-Java-td4897.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLINK-1219) Add support for Apache Tez as execution engine
[ https://issues.apache.org/jira/browse/FLINK-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392725#comment-14392725 ] ASF GitHub Bot commented on FLINK-1219: --- Github user rmetzger commented on the pull request: https://github.com/apache/flink/pull/189#issuecomment-88910737 Fix for the build failure is being tested: https://travis-ci.org/rmetzger/flink/builds/56885481 Add support for Apache Tez as execution engine -- Key: FLINK-1219 URL: https://issues.apache.org/jira/browse/FLINK-1219 Project: Flink Issue Type: New Feature Reporter: Kostas Tzoumas Assignee: Kostas Tzoumas This is an umbrella issue to track Apache Tez support. The goal is to be able to run unmodified Flink programs as Apache Tez jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLINK-1816) DegreesWithExceptionITCase.testGetDegreesInvalidEdgeSrcId fails with wrong exception
[
https://issues.apache.org/jira/browse/FLINK-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392739#comment-14392739
]
ASF GitHub Bot commented on FLINK-1816:
---
Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/562
DegreesWithExceptionITCase.testGetDegreesInvalidEdgeSrcId fails with wrong
exception
Key: FLINK-1816
URL: https://issues.apache.org/jira/browse/FLINK-1816
Project: Flink
Issue Type: Bug
Components: Gelly
Reporter: Till Rohrmann
Assignee: Till Rohrmann
In one of the Travis builds [1] I noticed that the
{{DegreesWithExceptionITCase.testGetDegreesInvalidEdgeSrcId}} test case fails
because it receives a wrong exception.
[1] [https://travis-ci.org/apache/flink/jobs/56738202]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] flink pull request: [FLINK-1816] Fixes wrongly introduced exceptio...
Github user tillrohrmann commented on the pull request: https://github.com/apache/flink/pull/562#issuecomment-88919364 I'll merge it now. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (FLINK-1816) DegreesWithExceptionITCase.testGetDegreesInvalidEdgeSrcId fails with wrong exception
[
https://issues.apache.org/jira/browse/FLINK-1816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392737#comment-14392737
]
ASF GitHub Bot commented on FLINK-1816:
---
Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/562#issuecomment-88919364
I'll merge it now.
DegreesWithExceptionITCase.testGetDegreesInvalidEdgeSrcId fails with wrong
exception
Key: FLINK-1816
URL: https://issues.apache.org/jira/browse/FLINK-1816
Project: Flink
Issue Type: Bug
Components: Gelly
Reporter: Till Rohrmann
Assignee: Till Rohrmann
In one of the Travis builds [1] I noticed that the
{{DegreesWithExceptionITCase.testGetDegreesInvalidEdgeSrcId}} test case fails
because it receives a wrong exception.
[1] [https://travis-ci.org/apache/flink/jobs/56738202]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] flink pull request: [FLINK-1219] Add support for Apache Tez as exe...
Github user rmetzger commented on the pull request: https://github.com/apache/flink/pull/189#issuecomment-88910737 Fix for the build failure is being tested: https://travis-ci.org/rmetzger/flink/builds/56885481 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] flink pull request: [FLINK-1816] Fixes wrongly introduced exceptio...
Github user asfgit closed the pull request at: https://github.com/apache/flink/pull/562 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] flink pull request: Reworking of Iteration Synchronization, Accumu...
Github user markus-h commented on the pull request: https://github.com/apache/flink/pull/36#issuecomment-88924335 I continued working on this. I will try to integrate this change in the current master. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (FLINK-967) Make intermediate results a first-class citizen in the JobGraph
[ https://issues.apache.org/jira/browse/FLINK-967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14392980#comment-14392980 ] Alexander Alexandrov commented on FLINK-967: [~StephanEwen] what is the status on this? Make intermediate results a first-class citizen in the JobGraph --- Key: FLINK-967 URL: https://issues.apache.org/jira/browse/FLINK-967 Project: Flink Issue Type: New Feature Components: JobManager, TaskManager Affects Versions: 0.6-incubating Reporter: Stephan Ewen Assignee: Stephan Ewen Fix For: 0.9 In order to add incremental plan rollout to the system, we need to make intermediate results a first-class citizen in the job graph and scheduler. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLINK-1219) Add support for Apache Tez as execution engine
[ https://issues.apache.org/jira/browse/FLINK-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14393060#comment-14393060 ] ASF GitHub Bot commented on FLINK-1219: --- Github user asfgit closed the pull request at: https://github.com/apache/flink/pull/189 Add support for Apache Tez as execution engine -- Key: FLINK-1219 URL: https://issues.apache.org/jira/browse/FLINK-1219 Project: Flink Issue Type: New Feature Reporter: Kostas Tzoumas Assignee: Kostas Tzoumas This is an umbrella issue to track Apache Tez support. The goal is to be able to run unmodified Flink programs as Apache Tez jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] flink pull request: [FLINK-1219] Add support for Apache Tez as exe...
Github user asfgit closed the pull request at: https://github.com/apache/flink/pull/189 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Updated] (FLINK-1219) Add support for Apache Tez as execution engine
[ https://issues.apache.org/jira/browse/FLINK-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Metzger updated FLINK-1219: -- Component/s: Flink on Tez Add support for Apache Tez as execution engine -- Key: FLINK-1219 URL: https://issues.apache.org/jira/browse/FLINK-1219 Project: Flink Issue Type: New Feature Components: Flink on Tez, New Components Reporter: Kostas Tzoumas Assignee: Kostas Tzoumas Fix For: 0.9 This is an umbrella issue to track Apache Tez support. The goal is to be able to run unmodified Flink programs as Apache Tez jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (FLINK-1219) Add support for Apache Tez as execution engine
[ https://issues.apache.org/jira/browse/FLINK-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Metzger resolved FLINK-1219. --- Resolution: Fixed Fix Version/s: 0.9 Merged in http://git-wip-us.apache.org/repos/asf/flink/commit/2cbbd328. Add support for Apache Tez as execution engine -- Key: FLINK-1219 URL: https://issues.apache.org/jira/browse/FLINK-1219 Project: Flink Issue Type: New Feature Reporter: Kostas Tzoumas Assignee: Kostas Tzoumas Fix For: 0.9 This is an umbrella issue to track Apache Tez support. The goal is to be able to run unmodified Flink programs as Apache Tez jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FLINK-1219) Add support for Apache Tez as execution engine
[ https://issues.apache.org/jira/browse/FLINK-1219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Metzger updated FLINK-1219: -- Component/s: New Components Add support for Apache Tez as execution engine -- Key: FLINK-1219 URL: https://issues.apache.org/jira/browse/FLINK-1219 Project: Flink Issue Type: New Feature Components: New Components Reporter: Kostas Tzoumas Assignee: Kostas Tzoumas Fix For: 0.9 This is an umbrella issue to track Apache Tez support. The goal is to be able to run unmodified Flink programs as Apache Tez jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
