[jira] [Created] (FLINK-1872) How can generation dataset in flink automatic depend on number of filed and data type

2015-04-11 Thread hagersaleh (JIRA)
hagersaleh created FLINK-1872: - Summary: How can generation dataset in flink automatic depend on number of filed and data type Key: FLINK-1872 URL: https://issues.apache.org/jira/browse/FLINK-1872 Projec

[jira] [Created] (FLINK-1871) Add a Spargel to Gelly migration guide

2015-04-11 Thread Vasia Kalavri (JIRA)
Vasia Kalavri created FLINK-1871: Summary: Add a Spargel to Gelly migration guide Key: FLINK-1871 URL: https://issues.apache.org/jira/browse/FLINK-1871 Project: Flink Issue Type: Task

[jira] [Comment Edited] (FLINK-1660) MultiTriggerPolicyTest timeout during test

2015-04-11 Thread Ufuk Celebi (JIRA)
[ https://issues.apache.org/jira/browse/FLINK-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14490881#comment-14490881 ] Ufuk Celebi edited comment on FLINK-1660 at 4/11/15 9:18 AM: -

[jira] [Commented] (FLINK-1660) MultiTriggerPolicyTest timeout during test

2015-04-11 Thread Ufuk Celebi (JIRA)
[ https://issues.apache.org/jira/browse/FLINK-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14490881#comment-14490881 ] Ufuk Celebi commented on FLINK-1660: Seems to be a thread-safety issue. Each thread r

[GitHub] flink pull request: [docs] Add custom search (backport)

2015-04-11 Thread uce
Github user uce closed the pull request at: https://github.com/apache/flink/pull/564 --- 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

[jira] [Commented] (FLINK-1660) MultiTriggerPolicyTest timeout during test

2015-04-11 Thread Ufuk Celebi (JIRA)
[ https://issues.apache.org/jira/browse/FLINK-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14490856#comment-14490856 ] Ufuk Celebi commented on FLINK-1660: Occurred again https://s3.amazonaws.com/archive.