[
https://issues.apache.org/jira/browse/FLINK-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henry Saputra resolved FLINK-1314.
--
Resolution: Fixed
Fix Version/s: master
Committed revision 1656952
> Update website abou
[
https://issues.apache.org/jira/browse/FLINK-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14304192#comment-14304192
]
ASF GitHub Bot commented on FLINK-377:
--
Github user zentol commented on the pull reque
Github user zentol commented on the pull request:
https://github.com/apache/flink/pull/202#issuecomment-72752968
@qmlmoon sweet.
@rmetzger errors should show up on the console now. and in the .out file.
and i suppose by extension in the .log file aswell.
---
If your project
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/354#issuecomment-72752435
Nope, sorry, also have no Idea why this is happening.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If y
[
https://issues.apache.org/jira/browse/FLINK-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14304150#comment-14304150
]
ASF GitHub Bot commented on FLINK-377:
--
Github user qmlmoon commented on the pull requ
Github user qmlmoon commented on the pull request:
https://github.com/apache/flink/pull/202#issuecomment-72749480
Great. Now it works for me
---
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 th
[
https://issues.apache.org/jira/browse/FLINK-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14304119#comment-14304119
]
ASF GitHub Bot commented on FLINK-377:
--
Github user zentol commented on the pull reque
Github user zentol commented on the pull request:
https://github.com/apache/flink/pull/202#issuecomment-72746379
Ive added a potential fix for the /tmp path issue.
---
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 p
Github user zentol commented on the pull request:
https://github.com/apache/flink/pull/202#issuecomment-72744279
about error messages going to command-line: the only way i see for that to
work is by wrapping the complete error message into an exception, since they do
show up on the co
[
https://issues.apache.org/jira/browse/FLINK-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14304096#comment-14304096
]
ASF GitHub Bot commented on FLINK-377:
--
Github user zentol commented on the pull reque
[
https://issues.apache.org/jira/browse/FLINK-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14304088#comment-14304088
]
ASF GitHub Bot commented on FLINK-1471:
---
GitHub user twalthr opened a pull request:
GitHub user twalthr opened a pull request:
https://github.com/apache/flink/pull/359
[FLINK-1471][java-api] Fixes wrong input validation if function has no
generics
FLINK-1471 was not implemented properly. See also #354.
This PR skips the input validation if no generic param
Github user twalthr commented on the pull request:
https://github.com/apache/flink/pull/354#issuecomment-72741911
I looked into your issue. Scala has a very strange behavior at this point.
I don't know why it converts `Int` to `Object`. The TypeExtractor gets
`Tuple3` which results in
[
https://issues.apache.org/jira/browse/FLINK-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14304042#comment-14304042
]
ASF GitHub Bot commented on FLINK-592:
--
Github user warneke commented on the pull requ
Github user warneke commented on the pull request:
https://github.com/apache/flink/pull/358#issuecomment-72739181
Hi,
I tried the code and found the following three problems:
__Flink launch script (bin/flink) points to the wrong log4j configuration
file__
log
[
https://issues.apache.org/jira/browse/FLINK-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303979#comment-14303979
]
ASF GitHub Bot commented on FLINK-377:
--
Github user qmlmoon commented on the pull requ
Github user qmlmoon commented on the pull request:
https://github.com/apache/flink/pull/202#issuecomment-72734478
I got the same issue as fabian on OS X. The problem may result from
different tmp files created by java and that used in python.
In java you created a file under `$"ja
[
https://issues.apache.org/jira/browse/FLINK-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303932#comment-14303932
]
ASF GitHub Bot commented on FLINK-377:
--
Github user rmetzger commented on the pull req
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/202#issuecomment-72729815
> "hard to find error messages" what do you mean by that?
Mh, for example that the output of the failed python script was logged to
the ".out" file, and not immed
[
https://issues.apache.org/jira/browse/FLINK-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303665#comment-14303665
]
Henry Saputra commented on FLINK-1314:
--
Awesome! Thanks Robert
> Update website abou
[
https://issues.apache.org/jira/browse/FLINK-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303643#comment-14303643
]
ASF GitHub Bot commented on FLINK-592:
--
GitHub user rmetzger opened a pull request:
GitHub user rmetzger opened a pull request:
https://github.com/apache/flink/pull/358
[FLINK-592] Add support for Kerberos secured YARN setups to Flink.
This pull request is basically a port of @warneke's branch
(https://github.com/warneke/flink/tree/security) to the latest `master`
[
https://issues.apache.org/jira/browse/FLINK-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303569#comment-14303569
]
Robert Metzger commented on FLINK-1314:
---
Sorry, I was too busy today. The change loo
[
https://issues.apache.org/jira/browse/FLINK-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303567#comment-14303567
]
Henry Saputra commented on FLINK-1314:
--
If no comment, will merge this end of day
>
Github user hsaputra commented on the pull request:
https://github.com/apache/flink/pull/351#issuecomment-72686769
Ah, I meant to suggest different error message to make sure we know either
input format or type information is missing.
I will send another PR to implement this.
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/333#issuecomment-72678817
Ah, okay. I was on a branch which has not been rebased yet (so it didn't
contain the exclude).
So for now I have to do a "mvn clean" before going to older branches.
[
https://issues.apache.org/jira/browse/FLINK-1468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ufuk Celebi resolved FLINK-1468.
Resolution: Fixed
Fixed in 2bea793.
> Config parse failure fails task manager startup w/o an error
[
https://issues.apache.org/jira/browse/FLINK-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303508#comment-14303508
]
ASF GitHub Bot commented on FLINK-1330:
---
Github user rmetzger commented on the pull
[
https://issues.apache.org/jira/browse/FLINK-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303497#comment-14303497
]
ASF GitHub Bot commented on FLINK-1330:
---
Github user StephanEwen commented on the pu
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/333#issuecomment-72678344
I modified the merged version to exclude it from rat. I also tried
subsequent builds, it worked.
See here:
https://github.com/apache/flink/commit/0c726f833892
[
https://issues.apache.org/jira/browse/FLINK-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303483#comment-14303483
]
ASF GitHub Bot commented on FLINK-1330:
---
Github user rmetzger commented on the pull
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/333#issuecomment-72676563
The symlink is not excluded from the rat check. So subsequent builds will
fail due to the rat check.
---
If your project is set up for it, you can reply to this email an
Ufuk Celebi created FLINK-1472:
--
Summary: Web frontend config overview shows wrong value
Key: FLINK-1472
URL: https://issues.apache.org/jira/browse/FLINK-1472
Project: Flink
Issue Type: Bug
[
https://issues.apache.org/jira/browse/FLINK-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303420#comment-14303420
]
ASF GitHub Bot commented on FLINK-377:
--
Github user qmlmoon commented on the pull requ
Github user qmlmoon commented on the pull request:
https://github.com/apache/flink/pull/202#issuecomment-72668635
I would also like to try out some examples. I'm starting with TPCH queries:D
---
If your project is set up for it, you can reply to this email and have your
reply appear o
[
https://issues.apache.org/jira/browse/FLINK-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ufuk Celebi resolved FLINK-758.
---
Resolution: Won't Fix
Subsumed by https://github.com/apache/flink/pull/210
> Add count method to DataS
Github user aalexandrov commented on the pull request:
https://github.com/apache/flink/pull/354#issuecomment-72660810
I think that [this StackOverflow article explains my
problem](http://stackoverflow.com/questions/11586944/how-to-obtain-the-raw-datatype-of-a-parameter-of-a-field-that-
Github user aalexandrov commented on the pull request:
https://github.com/apache/flink/pull/354#issuecomment-72660318
I would advocate to adding this one as well as a fallback option.
I have a situation where I want to use KeySelector that might return Java
TupleXX instances p
[
https://issues.apache.org/jira/browse/FLINK-1455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303334#comment-14303334
]
Stephan Ewen commented on FLINK-1455:
-
Hmm, this seems a problem of the JVM setup on t
[
https://issues.apache.org/jira/browse/FLINK-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Ewen resolved FLINK-1326.
-
Resolution: Fixed
Fix Version/s: 0.9
Fixed in bc69b0bb530a6daeea2c18b1ff9edbb4d1faa48c
> T
[
https://issues.apache.org/jira/browse/FLINK-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303266#comment-14303266
]
ASF GitHub Bot commented on FLINK-377:
--
Github user zentol commented on the pull reque
Github user zentol commented on the pull request:
https://github.com/apache/flink/pull/202#issuecomment-72652471
hmm...you are now the second person to report that creating the tmp files
does not work on OS X. i don't know why that doesn't work. the file creation is
done from java, is
[
https://issues.apache.org/jira/browse/FLINK-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Ewen resolved FLINK-1330.
-
Resolution: Fixed
Fix Version/s: 0.9
Assignee: Stephan Ewen
Fixed via 0c726f833892
Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/333
---
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
[
https://issues.apache.org/jira/browse/FLINK-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303260#comment-14303260
]
ASF GitHub Bot commented on FLINK-1330:
---
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/FLINK-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Metzger reopened FLINK-1471:
---
The commit Stephan mentions fixes another issue.
This is still unresolved.
> Allow KeySelectors t
[
https://issues.apache.org/jira/browse/FLINK-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Metzger resolved FLINK-1464.
---
Resolution: Fixed
Fixed via e3f6c9ba69a3e545fdd8f18b7b652fa111ade93e
Thanks for the patch!
Th
[
https://issues.apache.org/jira/browse/FLINK-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303187#comment-14303187
]
ASF GitHub Bot commented on FLINK-1458:
---
Github user aljoscha commented on the pull
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/357#issuecomment-72642370
You're right.
---
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-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Ewen resolved FLINK-1437.
-
Resolution: Fixed
Fix Version/s: 0.9
Fixed via fb7ce0e315e270e10c605dcfa269286bc2add47f
>
[
https://issues.apache.org/jira/browse/FLINK-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Ewen resolved FLINK-1193.
-
Resolution: Fixed
Fix Version/s: 0.9
Fixed via 57b3e9f9e50705033200dcca0762a5a65d1aba60
>
[
https://issues.apache.org/jira/browse/FLINK-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Ewen resolved FLINK-1471.
-
Resolution: Fixed
Fix Version/s: 0.9
Fixed via e3f6c9ba69a3e545fdd8f18b7b652fa111ade93e
Th
[
https://issues.apache.org/jira/browse/FLINK-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303178#comment-14303178
]
ASF GitHub Bot commented on FLINK-1165:
---
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/FLINK-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303176#comment-14303176
]
ASF GitHub Bot commented on FLINK-1193:
---
Github user asfgit closed the pull request
[
https://issues.apache.org/jira/browse/FLINK-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Ewen resolved FLINK-1165.
-
Resolution: Fixed
Fix Version/s: 0.9
Fixed via aeec128b773fca60cbf2ebafe812c5898da4a754 and
Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/348
---
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
[
https://issues.apache.org/jira/browse/FLINK-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303177#comment-14303177
]
ASF GitHub Bot commented on FLINK-1464:
---
Github user asfgit closed the pull request
Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/342
---
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 asfgit closed the pull request at:
https://github.com/apache/flink/pull/320
---
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
[
https://issues.apache.org/jira/browse/FLINK-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303175#comment-14303175
]
ASF GitHub Bot commented on FLINK-1437:
---
Github user asfgit closed the pull request
Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/351
---
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 asfgit closed the pull request at:
https://github.com/apache/flink/pull/349
---
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
[
https://issues.apache.org/jira/browse/FLINK-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303170#comment-14303170
]
ASF GitHub Bot commented on FLINK-377:
--
Github user fhueske commented on the pull requ
Github user fhueske commented on the pull request:
https://github.com/apache/flink/pull/202#issuecomment-72641447
btw. implementing the program felt quite good. Very nice API, IMO!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub a
[
https://issues.apache.org/jira/browse/FLINK-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303164#comment-14303164
]
ASF GitHub Bot commented on FLINK-377:
--
Github user fhueske commented on the pull requ
Github user fhueske commented on the pull request:
https://github.com/apache/flink/pull/202#issuecomment-72640916
Just implemented the basic triangle enumeration job and figured out that
this example is already included in this PR ;-)
However, when trying to run both programs, I en
[
https://issues.apache.org/jira/browse/FLINK-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303075#comment-14303075
]
ASF GitHub Bot commented on FLINK-1464:
---
Github user StephanEwen commented on the pu
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/349#issuecomment-72631504
Looks good to me. I think the API breaking is minor, since it does not
affect the methods on `DataSet` or on any of the operators. The
TypeSerializerInputFormat is onl
[
https://issues.apache.org/jira/browse/FLINK-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303064#comment-14303064
]
ASF GitHub Bot commented on FLINK-1193:
---
Github user StephanEwen commented on the pu
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/348#issuecomment-72630115
I will merge this, fixing the comment...
---
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 projec
[
https://issues.apache.org/jira/browse/FLINK-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303060#comment-14303060
]
ASF GitHub Bot commented on FLINK-1193:
---
Github user StephanEwen commented on a diff
Github user StephanEwen commented on a diff in the pull request:
https://github.com/apache/flink/pull/348#discussion_r23995382
--- Diff:
flink-core/src/main/java/org/apache/flink/api/common/typeutils/base/GenericArraySerializer.java
---
@@ -72,7 +72,9 @@ public boolean isStateful(
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/351#issuecomment-72629129
I tried to implement Henry's idea, but I noticed the error message is very
specific to the site where it is created, since it refers to an alternate
method of `DataSet
[
https://issues.apache.org/jira/browse/FLINK-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303054#comment-14303054
]
ASF GitHub Bot commented on FLINK-1458:
---
Github user StephanEwen commented on the pu
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/357#issuecomment-72628325
The tests cover that the serializer supports this. One issue was that the
type extractor rejected the types, even though they were supported.
---
If your project is s
[
https://issues.apache.org/jira/browse/FLINK-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fabian Hueske resolved FLINK-1105.
--
Resolution: Fixed
Fix Version/s: 0.9
Fixed with 5f475599264d3d388e81cbceb71b641e1bb7d83f
[
https://issues.apache.org/jira/browse/FLINK-1105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303040#comment-14303040
]
ASF GitHub Bot commented on FLINK-1105:
---
Github user asfgit closed the pull request
Github user asfgit closed the pull request at:
https://github.com/apache/flink/pull/347
---
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 StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/351#issuecomment-72623931
I'll merge this...
---
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 f
[
https://issues.apache.org/jira/browse/FLINK-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303028#comment-14303028
]
ASF GitHub Bot commented on FLINK-1437:
---
Github user StephanEwen commented on the pu
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/342#issuecomment-72623753
Ah, just saw that the tests are there. My bad...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If you
[
https://issues.apache.org/jira/browse/FLINK-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303013#comment-14303013
]
ASF GitHub Bot commented on FLINK-1437:
---
Github user StephanEwen commented on the pu
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/342#issuecomment-72621357
I ran into this error as well. Will merge this and add a test...
---
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-1471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303007#comment-14303007
]
ASF GitHub Bot commented on FLINK-1471:
---
Github user rmetzger commented on the pull
Robert Metzger created FLINK-1471:
-
Summary: Allow KeySelectors to implement ResultTypeQueryable
Key: FLINK-1471
URL: https://issues.apache.org/jira/browse/FLINK-1471
Project: Flink
Issue Typ
Github user rmetzger closed the pull request at:
https://github.com/apache/flink/pull/354
---
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/354#issuecomment-72620298
I'll close it.
I've filed a jira for the issue and assigned it to @twalthr:
https://issues.apache.org/jira/browse/FLINK-1471
---
If your project is set up for it, yo
[
https://issues.apache.org/jira/browse/FLINK-1376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14302997#comment-14302997
]
ASF GitHub Bot commented on FLINK-1376:
---
Github user StephanEwen commented on the pu
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/317#issuecomment-72618925
I think this is a good fix, overall. There is one issue I would really like
to fix, and that is the serializability of the `Instance` class. This class is
not meant to
[
https://issues.apache.org/jira/browse/FLINK-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14302986#comment-14302986
]
ASF GitHub Bot commented on FLINK-1458:
---
Github user aljoscha commented on the pull
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/351#issuecomment-72618284
Good idea, Henry, if we can make sure that the IllegalArgumentException is
not thrown in any other cases.
---
If your project is set up for it, you can reply to this
Github user aljoscha commented on the pull request:
https://github.com/apache/flink/pull/357#issuecomment-72618070
But I extended the test with a SerializerTest for both Interfaces (traits)
and abstract classes. The other thing I will change, yes.
---
If your project is set up for it
[
https://issues.apache.org/jira/browse/FLINK-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14302976#comment-14302976
]
ASF GitHub Bot commented on FLINK-377:
--
Github user zentol commented on a diff in the
Github user zentol commented on a diff in the pull request:
https://github.com/apache/flink/pull/202#discussion_r23990492
--- Diff:
flink-addons/flink-language-binding/src/main/python/org/apache/flink/languagebinding/api/python/dill/__diff.py
---
@@ -0,0 +1,247 @@
+##
[
https://issues.apache.org/jira/browse/FLINK-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14302966#comment-14302966
]
ASF GitHub Bot commented on FLINK-1458:
---
Github user StephanEwen commented on the pu
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/354#issuecomment-72614564
So, this pull request can be closed?
---
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 do
Github user StephanEwen commented on the pull request:
https://github.com/apache/flink/pull/357#issuecomment-72614433
Looks good to me so far, modulo two comments:
- Since the type extractor code is changed a lot, it would be good to
have a test validating that the TypeExtractor
[
https://issues.apache.org/jira/browse/FLINK-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14302954#comment-14302954
]
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/265#issuecomment-72613154
The API was just extended, but the parsing logic for strings changed (see
PR description). So programs that relied on the previous way of parsing will
fail now.
---
If y
[
https://issues.apache.org/jira/browse/FLINK-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14302948#comment-14302948
]
ASF GitHub Bot commented on FLINK-1318:
---
Github user StephanEwen commented on the pu
1 - 100 of 101 matches
Mail list logo