[
https://issues.apache.org/jira/browse/FLINK-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Metzger closed FLINK-1016.
-
Resolution: Duplicate
> Add directory for user-contributed programs
>
[
https://issues.apache.org/jira/browse/FLINK-1153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Metzger closed FLINK-1153.
-
Resolution: Won't Fix
> Yarn container does not terminate if Flink's yarn client is terminated bef
Github user uce commented on the pull request:
https://github.com/apache/flink/pull/333#issuecomment-71469342
There's another minor thing. After running mvn clean, the symlink will
point to a non-existing directory.
---
If your project is set up for it, you can reply to this email an
[
https://issues.apache.org/jira/browse/FLINK-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291886#comment-14291886
]
ASF GitHub Bot commented on FLINK-1330:
---
Github user uce commented on the pull reque
[
https://issues.apache.org/jira/browse/FLINK-956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Metzger resolved FLINK-956.
--
Resolution: Fixed
Fix Version/s: 0.7.0-incubating
This has been fixed as described in the
[
https://issues.apache.org/jira/browse/FLINK-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Metzger resolved FLINK-512.
--
Resolution: Fixed
Has been resolved by FLINK-1266 (at least to the scope of this issue)
> Add su
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/333#issuecomment-71469736
Oh, actually, that should work because the configuration explicitly binds
the plugin to the "clean" phase.
---
If your project is set up for it, you can reply to this em
[
https://issues.apache.org/jira/browse/FLINK-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291891#comment-14291891
]
ASF GitHub Bot commented on FLINK-1330:
---
Github user rmetzger commented on the pull
Github user uce commented on the pull request:
https://github.com/apache/flink/pull/333#issuecomment-71470142
Yes, I thought it would handle it as well, but I just ran it and it didn't
work.
---
If your project is set up for it, you can reply to this email and have your
reply appear
[
https://issues.apache.org/jira/browse/FLINK-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291898#comment-14291898
]
ASF GitHub Bot commented on FLINK-1330:
---
Github user uce commented on the pull reque
Github user fhueske commented on the pull request:
https://github.com/apache/flink/pull/265#issuecomment-71470231
Any comments on 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
[
https://issues.apache.org/jira/browse/FLINK-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291900#comment-14291900
]
ASF GitHub Bot commented on FLINK-1318:
---
Github user fhueske commented on the pull r
Github user fhueske commented on the pull request:
https://github.com/apache/flink/pull/311#issuecomment-71470851
Addressed most comments and renamed constantFields/Sets to forwardedFields
as discussed on dev-ml.
Would like to merge this soon.
---
If your project is set up for it
[
https://issues.apache.org/jira/browse/FLINK-1328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291904#comment-14291904
]
ASF GitHub Bot commented on FLINK-1328:
---
Github user fhueske commented on the pull r
[
https://issues.apache.org/jira/browse/FLINK-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Metzger resolved FLINK-1453.
---
Resolution: Fixed
Fix Version/s: 0.9
Issue resolved in http://git-wip-us.apache.org/rep
[
https://issues.apache.org/jira/browse/FLINK-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mingliang Qi reassigned FLINK-1430:
---
Assignee: Mingliang Qi
> Add test for streaming scala api completeness
>
[
https://issues.apache.org/jira/browse/FLINK-1430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291921#comment-14291921
]
Mingliang Qi commented on FLINK-1430:
-
I saw some methods like setConfig, getConfig, g
GitHub user twalthr opened a pull request:
https://github.com/apache/flink/pull/342
[FLINK-1437][Java API] Fixes copy() methods in PojoSerializer for null
values.
See description in FLINK-1437.
PR includes tests cases.
You can merge this pull request into a Git repository
[
https://issues.apache.org/jira/browse/FLINK-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291931#comment-14291931
]
ASF GitHub Bot commented on FLINK-1437:
---
GitHub user twalthr opened a pull request:
[
https://issues.apache.org/jira/browse/FLINK-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291934#comment-14291934
]
ASF GitHub Bot commented on FLINK-1437:
---
Github user rmetzger commented on the pull
[
https://issues.apache.org/jira/browse/FLINK-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291936#comment-14291936
]
ASF GitHub Bot commented on FLINK-1446:
---
Github user asfgit closed the pull request
Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/336
---
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 enabl
Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/328#issuecomment-71476676
I updated the PR with the exponential backoff registration strategy. On the
way, I fixed the flakey RecoveryIT case.
---
If your project is set up for it, you can re
[
https://issues.apache.org/jira/browse/FLINK-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291940#comment-14291940
]
ASF GitHub Bot commented on FLINK-1352:
---
Github user tillrohrmann commented on the p
[
https://issues.apache.org/jira/browse/FLINK-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291941#comment-14291941
]
Mingliang Qi commented on FLINK-1454:
-
isn't it because akka timeout is set to 100s?
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/342#issuecomment-71475896
This will probably conflict with https://github.com/apache/flink/pull/316.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/319#issuecomment-71477890
I think so too. The changes of the scheduler are only included because
otherwise the test cases wouldn't pass. The scheduler relevant PR is #317.
---
If your project
[
https://issues.apache.org/jira/browse/FLINK-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291950#comment-14291950
]
ASF GitHub Bot commented on FLINK-1415:
---
Github user tillrohrmann commented on the p
[
https://issues.apache.org/jira/browse/FLINK-1454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291951#comment-14291951
]
Robert Metzger commented on FLINK-1454:
---
Yes. It would be nicer if the system told t
Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/315
---
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 enabl
Github user tillrohrmann commented on a diff in the pull request:
https://github.com/apache/flink/pull/319#discussion_r23537586
--- Diff:
flink-runtime/src/main/java/org/apache/flink/runtime/jobmanager/scheduler/SlotAvailabilityListener.java
---
@@ -21,7 +21,7 @@
import org.a
[
https://issues.apache.org/jira/browse/FLINK-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291953#comment-14291953
]
ASF GitHub Bot commented on FLINK-1147:
---
Github user asfgit closed the pull request
Github user tillrohrmann commented on a diff in the pull request:
https://github.com/apache/flink/pull/319#discussion_r23537642
--- Diff:
flink-runtime/src/main/java/org/apache/flink/runtime/jobmanager/scheduler/SlotSharingGroupAssignment.java
---
@@ -42,86 +44,82 @@
public c
[
https://issues.apache.org/jira/browse/FLINK-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291954#comment-14291954
]
ASF GitHub Bot commented on FLINK-1415:
---
Github user tillrohrmann commented on a dif
[
https://issues.apache.org/jira/browse/FLINK-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291956#comment-14291956
]
ASF GitHub Bot commented on FLINK-1415:
---
Github user tillrohrmann commented on a dif
[
https://issues.apache.org/jira/browse/FLINK-1446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Metzger resolved FLINK-1446.
---
Resolution: Fixed
Resolved for 0.9 (master) in
http://git-wip-us.apache.org/repos/asf/flink/c
[
https://issues.apache.org/jira/browse/FLINK-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timo Walther resolved FLINK-1147.
-
Resolution: Fixed
Fix Version/s: 0.9
Fixed in commit 6067833fb6ad6c11a121d8654d7ca147cc909f
[
https://issues.apache.org/jira/browse/FLINK-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Max Michels reassigned FLINK-1442:
--
Assignee: Max Michels
> Archived Execution Graph consumes too much memory
> ---
Github user rmetzger closed the pull request at:
https://github.com/apache/flink/pull/323
---
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 ena
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/323#issuecomment-71483920
I will make this change part of a new pull request for
https://issues.apache.org/jira/browse/FLINK-1417.
---
If your project is set up for it, you can reply to this emai
[
https://issues.apache.org/jira/browse/FLINK-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291989#comment-14291989
]
ASF GitHub Bot commented on FLINK-1391:
---
Github user rmetzger closed the pull reques
[
https://issues.apache.org/jira/browse/FLINK-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291988#comment-14291988
]
ASF GitHub Bot commented on FLINK-1391:
---
Github user rmetzger commented on the pull
Github user rmetzger closed the pull request at:
https://github.com/apache/flink/pull/322
---
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 ena
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/322#issuecomment-71484526
I will make this change part of a new pull request for
https://issues.apache.org/jira/browse/FLINK-1417.
---
If your project is set up for it, you can reply to this emai
[
https://issues.apache.org/jira/browse/FLINK-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291996#comment-14291996
]
ASF GitHub Bot commented on FLINK-1392:
---
Github user rmetzger closed the pull reques
[
https://issues.apache.org/jira/browse/FLINK-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291995#comment-14291995
]
ASF GitHub Bot commented on FLINK-1392:
---
Github user rmetzger commented on the pull
Github user tillrohrmann commented on a diff in the pull request:
https://github.com/apache/flink/pull/339#discussion_r23541551
--- Diff:
flink-runtime/src/main/java/org/apache/flink/runtime/filecache/FileCache.java
---
@@ -72,7 +72,7 @@
* @return copy task
*/
[
https://issues.apache.org/jira/browse/FLINK-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292011#comment-14292011
]
ASF GitHub Bot commented on FLINK-1419:
---
Github user tillrohrmann commented on a dif
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/304#issuecomment-71487780
I'm going to merge the changes in this pull request into a custom branch.
I'll open a new pull request (FLINK-1417) containing the commit from this
PR.
@aljos
[
https://issues.apache.org/jira/browse/FLINK-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292017#comment-14292017
]
ASF GitHub Bot commented on FLINK-1395:
---
Github user rmetzger commented on the pull
Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/339#issuecomment-71488487
I don't really understand how the static lock solves the mentioned issue.
Is there a concurrency problem between creating files on disk and updating the
count hash ma
[
https://issues.apache.org/jira/browse/FLINK-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292024#comment-14292024
]
ASF GitHub Bot commented on FLINK-1419:
---
Github user tillrohrmann commented on the p
Github user zentol commented on the pull request:
https://github.com/apache/flink/pull/339#issuecomment-71489135
but that is exactly what is changing, both the delete and copy process are
synchronized on the same object.
---
If your project is set up for it, you can reply to this ema
[
https://issues.apache.org/jira/browse/FLINK-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292032#comment-14292032
]
ASF GitHub Bot commented on FLINK-1419:
---
Github user zentol commented on the pull re
Github user zentol commented on the pull request:
https://github.com/apache/flink/pull/339#issuecomment-71490079
oh i see what you mean, maybe extend the synchronized block to include the
actual delete stuff. yup that's a good idea, all i know is i tried it without
the change and ran
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/304#issuecomment-71490297
Ok, closing it ...
---
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 feat
[
https://issues.apache.org/jira/browse/FLINK-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292036#comment-14292036
]
ASF GitHub Bot commented on FLINK-1419:
---
Github user zentol commented on the pull re
[
https://issues.apache.org/jira/browse/FLINK-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292038#comment-14292038
]
ASF GitHub Bot commented on FLINK-1419:
---
Github user tillrohrmann commented on the p
Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/339#issuecomment-71490264
Yes, but only the access to the count hash map. The delete action itself is
not synchronized.
---
If your project is set up for it, you can reply to this email and h
Github user aljoscha closed the pull request at:
https://github.com/apache/flink/pull/304
---
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 ena
[
https://issues.apache.org/jira/browse/FLINK-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292040#comment-14292040
]
ASF GitHub Bot commented on FLINK-1395:
---
Github user aljoscha closed the pull reques
[
https://issues.apache.org/jira/browse/FLINK-1395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292039#comment-14292039
]
ASF GitHub Bot commented on FLINK-1395:
---
Github user aljoscha commented on the pull
Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/338#issuecomment-71490635
LGTM
I suspect that the travis fail is caused by faulty colocated subslot
disposal. Should be fixed with #317
---
If your project is set up for it, you can
[
https://issues.apache.org/jira/browse/FLINK-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292046#comment-14292046
]
ASF GitHub Bot commented on FLINK-1201:
---
Github user vasia commented on the pull req
Github user vasia commented on the pull request:
https://github.com/apache/flink/pull/335#issuecomment-71491484
No worries, I can rename the tests. It's better to be consistent :)
May I ask, what is the difference between a XyzTest and a XyzITCase test
though? Thnx!
---
If your p
[
https://issues.apache.org/jira/browse/FLINK-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292051#comment-14292051
]
ASF GitHub Bot commented on FLINK-1201:
---
Github user fhueske commented on the pull r
Github user fhueske commented on the pull request:
https://github.com/apache/flink/pull/335#issuecomment-71492121
Sure, XyzTest are unit tests which are executed in Maven's test phase.
These should execute rather fast. Everything that brings up a full Flink system
is an integration te
[
https://issues.apache.org/jira/browse/FLINK-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292061#comment-14292061
]
ASF GitHub Bot commented on FLINK-938:
--
Github user tillrohrmann commented on the pull
Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/248#issuecomment-71493259
Mingliang could you rebase the PR on the latest master? In the meantime,
the codebase changed quite a bit.
---
If your project is set up for it, you can reply to thi
Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/339#issuecomment-71494058
Yeah, that would probably solve the problem.
With race conditions it is often very tricky. Sometimes little changes
change the process interleaving such that
[
https://issues.apache.org/jira/browse/FLINK-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292067#comment-14292067
]
ASF GitHub Bot commented on FLINK-1419:
---
Github user tillrohrmann commented on the p
Github user vasia commented on the pull request:
https://github.com/apache/flink/pull/335#issuecomment-71494713
Alright, thanks @fhueske! So, it seems all of our tests are integration
test cases. I will update later today I hope :)
---
If your project is set up for it, you can reply
[
https://issues.apache.org/jira/browse/FLINK-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292076#comment-14292076
]
ASF GitHub Bot commented on FLINK-1201:
---
Github user vasia commented on the pull req
[
https://issues.apache.org/jira/browse/FLINK-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292134#comment-14292134
]
ASF GitHub Bot commented on FLINK-1415:
---
Github user rmetzger commented on the pull
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/319#issuecomment-71501654
Do you think this change is also addressing this error?
https://travis-ci.org/rmetzger/flink/jobs/48365538
---
If your project is set up for it, you can reply to this
Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/319#issuecomment-71504706
To be honest, I have not seen this error before. But I doubt that this is a
subslot release issue. If this error appears more often, then we could try
to increa
[
https://issues.apache.org/jira/browse/FLINK-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292151#comment-14292151
]
ASF GitHub Bot commented on FLINK-1415:
---
Github user tillrohrmann commented on the p
Github user vasia commented on the pull request:
https://github.com/apache/flink/pull/335#issuecomment-71507264
Tests renamed :)
---
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
e
[
https://issues.apache.org/jira/browse/FLINK-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292167#comment-14292167
]
ASF GitHub Bot commented on FLINK-1201:
---
Github user vasia commented on the pull req
GitHub user rmetzger opened a pull request:
https://github.com/apache/flink/pull/343
[Typo] Delete DiscardingOuputFormat
I don't know if we have any users using this output format.
But I would like to get rid of the wrongly named `DiscardingOuputFormat`.
You can merge this pull
[
https://issues.apache.org/jira/browse/FLINK-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292249#comment-14292249
]
Max Michels commented on FLINK-1442:
Here is my take on your first two points. Is ther
GitHub user mxm opened a pull request:
https://github.com/apache/flink/pull/344
[FLINK-1442] Reduce memory consumption of archived execution graph
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mxm/flink flink-1442
Alternativel
[
https://issues.apache.org/jira/browse/FLINK-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292251#comment-14292251
]
ASF GitHub Bot commented on FLINK-1442:
---
GitHub user mxm opened a pull request:
Márton Balassi created FLINK-1456:
-
Summary: Projection to fieldnames, keyselectors
Key: FLINK-1456
URL: https://issues.apache.org/jira/browse/FLINK-1456
Project: Flink
Issue Type: New Featur
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/337#issuecomment-71548405
Okay, if it is an auxiliary classpath then it should be fine.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
[
https://issues.apache.org/jira/browse/FLINK-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292492#comment-14292492
]
ASF GitHub Bot commented on FLINK-1433:
---
Github user StephanEwen commented on the pu
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/344#issuecomment-71548964
Looks good so far. I see that you removed the LRU code. Was that on purpose?
Leaving it in may be a good idea, because the soft references are cleared
in arbit
[
https://issues.apache.org/jira/browse/FLINK-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292498#comment-14292498
]
ASF GitHub Bot commented on FLINK-1442:
---
Github user StephanEwen commented on the pu
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/236#issuecomment-71549414
It would be nice to use the same `registerType()` function for this as for
Kryo. Is there a good way to figure out where to register the type, Kryo or
POJO? If not, sh
[
https://issues.apache.org/jira/browse/FLINK-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292526#comment-14292526
]
Stephan Ewen commented on FLINK-1452:
-
+1
> Add "flink-contrib" maven module and READ
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/341#issuecomment-71553580
I think this is good to merge.
In general, relying on static variables to cache things is a bit of a
fragile mechanism. Maybe we can improve that when bringing
[
https://issues.apache.org/jira/browse/FLINK-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292539#comment-14292539
]
ASF GitHub Bot commented on FLINK-1344:
---
Github user StephanEwen commented on the pu
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/202#issuecomment-71553978
I agree, we should get this into the code.
Important is that it is building out of the box and working well with
Travis. I assume that works?
---
If your pro
[
https://issues.apache.org/jira/browse/FLINK-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292547#comment-14292547
]
ASF GitHub Bot commented on FLINK-377:
--
Github user StephanEwen commented on the pull
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/202#issuecomment-71554357
Concerning the package / project structure: It is a bit humble and hidden
as some language binding for python.
I think this deserves to be more prominently cal
[
https://issues.apache.org/jira/browse/FLINK-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292551#comment-14292551
]
ASF GitHub Bot commented on FLINK-377:
--
Github user StephanEwen commented on the pull
Github user tillrohrmann commented on the pull request:
https://github.com/apache/flink/pull/202#issuecomment-71558532
I'm in favour of putting it more prominently under
```flink-addons/flink-python```.
---
If your project is set up for it, you can reply to this email and have your
r
[
https://issues.apache.org/jira/browse/FLINK-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292592#comment-14292592
]
ASF GitHub Bot commented on FLINK-377:
--
Github user tillrohrmann commented on the pull
Github user dan-blanchard commented on the pull request:
https://github.com/apache/flink/pull/202#issuecomment-71570805
I've only recently started looking at Flink, and the lack of support for
non-JVM languages was a bit of showstopper for me. That's one of the main
reasons we use St
[
https://issues.apache.org/jira/browse/FLINK-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14292761#comment-14292761
]
ASF GitHub Bot commented on FLINK-377:
--
Github user dan-blanchard commented on the pul
101 - 200 of 207 matches
Mail list logo
