[
https://issues.apache.org/jira/browse/FLINK-3059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15021455#comment-15021455
]
ASF GitHub Bot commented on FLINK-3059:
---
GitHub user jaoki opened a pull request:
jun aoki created FLINK-3059:
---
Summary: Javadoc fix for DataSet.writeAsText()
Key: FLINK-3059
URL: https://issues.apache.org/jira/browse/FLINK-3059
Project: Flink
Issue Type: Bug
Reporte
GitHub user jaoki opened a pull request:
https://github.com/apache/flink/pull/1392
[FLINK-3059] Javadoc fix for DataSet.writeAsText()
Currently writeAsText() in javadoc states it simply generates a file,
but this is not always true and it depends on the environment configuration.
[
https://issues.apache.org/jira/browse/FLINK-2956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15021418#comment-15021418
]
ASF GitHub Bot commented on FLINK-2956:
---
Github user gallenvara commented on the pul
Github user gallenvara commented on the pull request:
https://github.com/apache/flink/pull/1349#issuecomment-158838162
Hi, @chiwanpark . I have modified the code format and submitted a new
commit.
---
If your project is set up for it, you can reply to this email and have your
reply a
Github user gyfora commented on the pull request:
https://github.com/apache/flink/pull/1305#issuecomment-158799081
@StephanEwen, @rmetzger:
I addressed the comments regarding the logs and the state id.
I also added a final improvement:
-Now compaction is executed i
Github user smarthi commented on the pull request:
https://github.com/apache/flink/pull/1391#issuecomment-158790920
@rmetzger good to merge now, travis builds are successful.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well
[
https://issues.apache.org/jira/browse/FLINK-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15021108#comment-15021108
]
ASF GitHub Bot commented on FLINK-2017:
---
Github user mliesenberg commented on the pu
Github user mliesenberg commented on the pull request:
https://github.com/apache/flink/pull/1097#issuecomment-158784004
ok. done.
---
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
[
https://issues.apache.org/jira/browse/FLINK-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated FLINK-2837:
---
Assignee: Maximilian Michels (was: Matthias J. Sax)
> FlinkTopologyBuilder cannot handle mult
[
https://issues.apache.org/jira/browse/FLINK-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15021102#comment-15021102
]
Matthias J. Sax commented on FLINK-2837:
No. Go ahead with your PR.
> FlinkTopolo
Robert Metzger created FLINK-3058:
-
Summary: Add Kafka consumer for new 0.9.0.0 Kafka API
Key: FLINK-3058
URL: https://issues.apache.org/jira/browse/FLINK-3058
Project: Flink
Issue Type: New
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/1391#issuecomment-158779096
The tests of `master` on travis are green. Maybe your changes are
side-effecting something with the table API? You could also try to rebase your
changes to the current
Github user smarthi commented on the pull request:
https://github.com/apache/flink/pull/1391#issuecomment-158778768
@rmetzger This is from the Table API which this PR does not touch, I can
either withdraw the PR or we could trigger another travis build for this PR and
see if the error
[
https://issues.apache.org/jira/browse/FLINK-2318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15021080#comment-15021080
]
ASF GitHub Bot commented on FLINK-2318:
---
Github user StephanEwen commented on the pu
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/1390#issuecomment-158778694
Thanks, @zentol , pretty cool fix!
Looks good to me!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
[
https://issues.apache.org/jira/browse/FLINK-3050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15021075#comment-15021075
]
Stephan Ewen commented on FLINK-3050:
-
I think that is what this pretty much would boi
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/1391#issuecomment-158775699
According to travis, this PR is breaking the build
```
[ERROR]
/home/travis/build/apache/flink/flink-staging/flink-table/src/main/scala/org/apache/flink/api/scal
[
https://issues.apache.org/jira/browse/FLINK-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15021065#comment-15021065
]
ASF GitHub Bot commented on FLINK-2017:
---
Github user rmetzger commented on the pull
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/1097#issuecomment-158775559
Oh, I see. I have to admit I didn't closely follow the discussion with
Fabian.
Would be nice if you could change the behavior.
---
If your project is set up f
[
https://issues.apache.org/jira/browse/FLINK-3050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15021054#comment-15021054
]
Chesnay Schepler commented on FLINK-3050:
-
Would it be sufficient to modify this b
[
https://issues.apache.org/jira/browse/FLINK-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15021049#comment-15021049
]
ASF GitHub Bot commented on FLINK-2017:
---
Github user mliesenberg commented on the pu
Github user mliesenberg commented on the pull request:
https://github.com/apache/flink/pull/1097#issuecomment-158766866
yep, based on the discussion above with fabian the default value is set
only on the long key.
I'll go ahead and set it on the short key as well, if nothing
Github user mxm commented on the pull request:
https://github.com/apache/flink/pull/1387#issuecomment-158765658
Maybe a stupid question but why don't you send the operator name along with
the BoltWrapper? Then there is no need to extract it from the Flink task name.
---
If your proje
[
https://issues.apache.org/jira/browse/FLINK-2861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15021037#comment-15021037
]
ASF GitHub Bot commented on FLINK-2861:
---
Github user mxm commented on the pull reque
Github user mxm commented on a diff in the pull request:
https://github.com/apache/flink/pull/1387#discussion_r45559955
--- Diff:
flink-contrib/flink-storm/src/main/java/org/apache/flink/storm/wrappers/WrapperSetupHelper.java
---
@@ -118,6 +119,11 @@ static synchronized TopologyCo
[
https://issues.apache.org/jira/browse/FLINK-2861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15021034#comment-15021034
]
ASF GitHub Bot commented on FLINK-2861:
---
Github user mxm commented on a diff in the
[
https://issues.apache.org/jira/browse/FLINK-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15021030#comment-15021030
]
ASF GitHub Bot commented on FLINK-2017:
---
Github user rmetzger commented on the pull
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/1097#issuecomment-158765143
I've tested the PR again.
I found a minor issue with the alternative arguments.
input: `--input abc --p 12`,
code:
```java
RequiredParameters rq = ne
Github user sachingoel0101 commented on the pull request:
https://github.com/apache/flink/pull/1338#issuecomment-158765098
@rmetzger
1. I have introduced a separate directory for uploads, named randomly, and
deleted as part of the shut down hook.
2. I also tried closing the `
[
https://issues.apache.org/jira/browse/FLINK-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15021027#comment-15021027
]
ASF GitHub Bot commented on FLINK-2978:
---
Github user sachingoel0101 commented on the
Github user mxm commented on the pull request:
https://github.com/apache/flink/pull/1337#issuecomment-158763006
@chiwanpark +1 for merging!
---
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 thi
[
https://issues.apache.org/jira/browse/FLINK-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15021018#comment-15021018
]
ASF GitHub Bot commented on FLINK-2947:
---
Github user mxm commented on the pull reque
[
https://issues.apache.org/jira/browse/FLINK-2837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15021016#comment-15021016
]
Maximilian Michels commented on FLINK-2837:
---
Have you started working on this? I
[
https://issues.apache.org/jira/browse/FLINK-2861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15021013#comment-15021013
]
ASF GitHub Bot commented on FLINK-2861:
---
Github user mxm commented on a diff in the
Github user mxm commented on a diff in the pull request:
https://github.com/apache/flink/pull/1387#discussion_r45559371
--- Diff:
flink-contrib/flink-storm/src/main/java/org/apache/flink/storm/wrappers/BoltWrapper.java
---
@@ -209,12 +209,8 @@ public void open() throws Exception {
Github user mliesenberg commented on the pull request:
https://github.com/apache/flink/pull/1097#issuecomment-158761960
the build failure is due to a test in streaming, so most likely not related.
the test failure has been observed before and is captured in issue
FLINK-2348
---
I
[
https://issues.apache.org/jira/browse/FLINK-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15021009#comment-15021009
]
ASF GitHub Bot commented on FLINK-2017:
---
Github user mliesenberg commented on the pu
[
https://issues.apache.org/jira/browse/FLINK-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chesnay Schepler updated FLINK-3057:
Summary: [py] Provide a way to pass informaiton back to the plan (was:
Provide a way to pas
Chesnay Schepler created FLINK-3057:
---
Summary: Provide a way to pass informaiton back to the plan
Key: FLINK-3057
URL: https://issues.apache.org/jira/browse/FLINK-3057
Project: Flink
Issue
40 matches
Mail list logo
