Github user aalexandrov commented on the pull request:
https://github.com/apache/flink/pull/354#issuecomment-72857627
I think that this only happens for the primitive types. I think this is by
design.
If you want to inspect generic parameters, Scala forces you to use the
Scal
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
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
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
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
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 rmetzger commented on the pull request:
https://github.com/apache/flink/pull/354#issuecomment-72316077
Cool, thank you
---
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
Github user twalthr commented on the pull request:
https://github.com/apache/flink/pull/354#issuecomment-72315446
I can create a fix for that.
---
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
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/354#issuecomment-72315355
Do you want to fix it or should I do 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 d
Github user twalthr commented on the pull request:
https://github.com/apache/flink/pull/354#issuecomment-72315121
It's a bug in line 689. The input validation tries to get the generic
parameters that are not available, in this case the validation should be
skipped.
---
If your proje
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/354#issuecomment-72314532
Without the change, I'm getting the following error, even though my
KeyExtractor implements ResultTypeQueryable:
```java
Exception in thread "main" java.lang.Illeg
Github user twalthr commented on the pull request:
https://github.com/apache/flink/pull/354#issuecomment-72314389
getUnaryOperatorReturnType() does already call ResultTypeQueryable if
available.
---
If your project is set up for it, you can reply to this email and have your
reply app
GitHub user rmetzger opened a pull request:
https://github.com/apache/flink/pull/354
Allow KeySelectors to implement ResultTypeQueryable
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rmetzger/flink resulttypeqKS
Alternatively
15 matches
Mail list logo
