I think it is best to drop support a JVM when it reaches the end of life
cycle or some time before reaching this date (when announcement is made).
You can publish this as a policy so there is not surprises.
--
View this message in context:
http://apache-flink-incubator-mailing-list-archive.1008
Hi Timo,
thank you for the explanation!
I guess I will try implementing ResultTypeQueryable then :)
Cheers,
Vasia.
On 30 October 2014 13:01, Timo Walther wrote:
> Hi Vasiliki,
>
> your error is a very common problem we have together with types. The
> problem is that Java does type erasure, whi
Hi Martin,
Flink does not have features to mitigate data skew at the moment, such as
dynamic partitioning.
That would also "only" allow to process large groups as an individual
partitions and multiple smaller groups together in other partitions.
The issue of having a large group would not be solve
It shuld happen as Java 6 is nearing EOL
Sent from my iPhone
> On Oct 30, 2014, at 9:00 AM, Stephan Ewen wrote:
>
> BTW: There is a discussion to bump the required version to java 7. Decision
> pending...
>
>> On Thu, Oct 30, 2014 at 2:00 PM, Stephan Ewen wrote:
>>
>> I think it also works w
I think it also works with openJDK 6, just not with OracleJDK 6 . The
problem you encounter is a known bug in Oracle JDK 6, but will not be fixed
since they stopped supporting java 6.
To run it, java 6 is also fine, it is really only a limitation in the
oracle java 6 compiler.
On Thu, Oct 30, 2
BTW: There is a discussion to bump the required version to java 7. Decision
pending...
On Thu, Oct 30, 2014 at 2:00 PM, Stephan Ewen wrote:
> I think it also works with openJDK 6, just not with OracleJDK 6 . The
> problem you encounter is a known bug in Oracle JDK 6, but will not be fixed
> sinc
Scratch that. It does work with Java 7. I think Java 7 should be made
mandatory??
On Thu, Oct 30, 2014 at 7:43 AM, Suneel Marthi
wrote:
> I am using Java 7. This is from https://github.com/apache/incubator-flink,
> was I looking in the wrong place ?
>
>
> On Thu, Oct 30, 2014 at 5:40 AM, Stepha
Hi Vasiliki,
your error is a very common problem we have together with types. The
problem is that Java does type erasure, which means that
return vertices.map(new ApplyMapperToVertex(mapper));
becomes
return vertices.map(new ApplyMapperToVertex(mapper));
Therefore we don't have the types. B
I am using Java 7. This is from https://github.com/apache/incubator-flink,
was I looking in the wrong place ?
On Thu, Oct 30, 2014 at 5:40 AM, Stephan Ewen wrote:
> Hey Suneel!
>
> Which branch are you referring to?
>
> Also, which Java Version do you use? Java 6 (earlier versions) has some
> l
Hi all,
one of the operations we want to implement for the flink graph api is
mapVertices, i.e. applying a mapper to the vertices of the graph.
The current implementation assumes that the vertex value type remains the
same:
https://github.com/project-flink/flink-graph/blob/master/src/main/java/fli
I think that would look nice.
How easy is that to implement? With that change, we could not initialize
the type info in the constructor any more, but would have to change
everything to lazy initialization, which makes it complicated and error
prone...
On Wed, Oct 29, 2014 at 4:26 PM, Timo Walther
Hey Suneel!
Which branch are you referring to?
Also, which Java Version do you use? Java 6 (earlier versions) has some
limitations to matching generic method signatures and cannot identify the
correct overriding method.
Stephan
Am 30.10.2014 10:06 schrieb "Suneel Marthi" :
> Trying to build t
Trying to build the project via 'mvn clean package', the build fails always
with the folllowing error:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.1:compile
(default-compile) on project flink-java: Compilation failure
[ERROR]
/Users/smarthi/opensourceprojects/in
13 matches
Mail list logo
