[jira] [Commented] (FLINK-2028) Download pages must not link to snapshots

2015-05-16 Thread Sebb (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546850#comment-14546850
 ] 

Sebb commented on FLINK-2028:
-

This is a policy issue, see

http://www.apache.org/dev/release.html#what

second para, in particular the bold text.

 Download pages must not link to snapshots
 -

 Key: FLINK-2028
 URL: https://issues.apache.org/jira/browse/FLINK-2028
 Project: Flink
  Issue Type: Bug
Reporter: Sebb

 Snapshot builds that have not passed a PMC vote must not be advertised to the 
 general public, so must not be included on the downloads page.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[GitHub] flink pull request: Pluggable state backend support for checkpoint...

2015-05-16 Thread gyfora
Github user gyfora commented on the pull request:

https://github.com/apache/flink/pull/676#issuecomment-102659733
  
I commented out the check in the recovery test that caused the issue until 
I figure it out. It's definitely not a blocker as it seems that only the very 
last successful checkpoints remain in the directory when it runs together with 
other tests.


---
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 but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Commented] (FLINK-2028) Download pages must not link to snapshots

2015-05-16 Thread Maximilian Michels (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546773#comment-14546773
 ] 

Maximilian Michels commented on FLINK-2028:
---

Is this a legal issue or a personal preference? The snapshot builds are clearly 
separated from the stable releases. If it is not a legal issue, I'd advise to 
label the snapshots as unstable including a notice about the missing quality 
assurance that would come with a release. 

 Download pages must not link to snapshots
 -

 Key: FLINK-2028
 URL: https://issues.apache.org/jira/browse/FLINK-2028
 Project: Flink
  Issue Type: Bug
Reporter: Sebb

 Snapshot builds that have not passed a PMC vote must not be advertised to the 
 general public, so must not be included on the downloads page.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (FLINK-2030) Implement an online histogram with Merging and equalization features

2015-05-16 Thread Sachin Goel (JIRA)
Sachin Goel created FLINK-2030:
--

 Summary: Implement an online histogram with Merging and 
equalization features
 Key: FLINK-2030
 URL: https://issues.apache.org/jira/browse/FLINK-2030
 Project: Flink
  Issue Type: Sub-task
Reporter: Sachin Goel
Priority: Blocker


For the implementation of the decision tree in 
https://issues.apache.org/jira/browse/FLINK-1727, we need to implement an 
histogram with online updates, merging and equalization features. A reference 
implementation is provided in [1]

[1].http://www.jmlr.org/papers/volume11/ben-haim10a/ben-haim10a.pdf



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[GitHub] flink pull request: [gelly][Refactoring] Removed example string

2015-05-16 Thread andralungu
Github user andralungu commented on the pull request:

https://github.com/apache/flink/pull/625#issuecomment-102684206
  
PR updated.


---
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 but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Closed] (FLINK-2027) Flink website does not provide link to source repo

2015-05-16 Thread Henry Saputra (JIRA)

 [ 
https://issues.apache.org/jira/browse/FLINK-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henry Saputra closed FLINK-2027.

Resolution: Not A Problem

 Flink website does not provide link to source repo
 --

 Key: FLINK-2027
 URL: https://issues.apache.org/jira/browse/FLINK-2027
 Project: Flink
  Issue Type: Bug
Reporter: Sebb
Priority: Critical

 As the subject says - I could not find a link to the source repo anywhere 
 obvious on the website



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (FLINK-2027) Flink website does not provide link to source repo

2015-05-16 Thread Henry Saputra (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546583#comment-14546583
 ] 

Henry Saputra commented on FLINK-2027:
--

[~s...@apache.org], the main Apache source repo is available at 
http://flink.apache.org/how-to-contribute.html at the Main source 
repositories section

 Flink website does not provide link to source repo
 --

 Key: FLINK-2027
 URL: https://issues.apache.org/jira/browse/FLINK-2027
 Project: Flink
  Issue Type: Bug
Reporter: Sebb
Priority: Critical

 As the subject says - I could not find a link to the source repo anywhere 
 obvious on the website



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Reopened] (FLINK-2027) Flink website does not provide link to source repo

2015-05-16 Thread Henry Saputra (JIRA)

 [ 
https://issues.apache.org/jira/browse/FLINK-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Henry Saputra reopened FLINK-2027:
--

Re-open this one to add link for easy access to source repo information.

 Flink website does not provide link to source repo
 --

 Key: FLINK-2027
 URL: https://issues.apache.org/jira/browse/FLINK-2027
 Project: Flink
  Issue Type: Bug
Reporter: Sebb
Priority: Critical

 As the subject says - I could not find a link to the source repo anywhere 
 obvious on the website



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (FLINK-2023) TypeExtractor does not work for (some) Scala Classes

2015-05-16 Thread Alexander Alexandrov (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546969#comment-14546969
 ] 

Alexander Alexandrov commented on FLINK-2023:
-

I think there is no easy way around this. Generic parameters in Scala classes 
are erased and at the Java level (on which the TypeExtractor operates) you will 
see only {{java.lang.Object}} instances instead. For a more detailed 
description of the problem with some examples check [this Stackoverflow 
entry|http://stackoverflow.com/questions/20749536/why-dont-scala-primitives-show-up-as-type-parameters-in-java-reflection].

 TypeExtractor does not work for (some) Scala Classes
 

 Key: FLINK-2023
 URL: https://issues.apache.org/jira/browse/FLINK-2023
 Project: Flink
  Issue Type: Bug
  Components: Type Serialization System
Reporter: Aljoscha Krettek

 [~vanaepi] discovered some problems while working on the Scala Gelly API 
 where, for example, a Scala MapFunction can not be correctly analyzed by the 
 type extractor. For example, generic types will not be correctly detected.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (FLINK-2023) TypeExtractor does not work for (some) Scala Classes

2015-05-16 Thread Alexander Alexandrov (JIRA)

[ 
https://issues.apache.org/jira/browse/FLINK-2023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14546970#comment-14546970
 ] 

Alexander Alexandrov commented on FLINK-2023:
-

Long story short - you cannot use the Java API directly from Scala (i.e., with 
Scala types) and rely on correct type inference form the TypeExtractor.

 TypeExtractor does not work for (some) Scala Classes
 

 Key: FLINK-2023
 URL: https://issues.apache.org/jira/browse/FLINK-2023
 Project: Flink
  Issue Type: Bug
  Components: Type Serialization System
Reporter: Aljoscha Krettek

 [~vanaepi] discovered some problems while working on the Scala Gelly API 
 where, for example, a Scala MapFunction can not be correctly analyzed by the 
 type extractor. For example, generic types will not be correctly detected.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)