Hi!
While I was working on code generation support for PojoComparators, I
stumbled upon the compareSerialized method [1]. It first creates two new
instances and then it is using the reusing overloads of the serializer.
Calling the non-reusing overload would create the instance anyways. Is
there a
github.com/Xazax-hun/flink/commits/serializer_codegen
On 23 April 2016 at 10:33, Gábor Horváth wrote:
> Hi,
>
> The GSoC project proposal was accepted! Thank you for all your support. I
> will do my best to live up to the challenges and deliver everything that
> way planned for this
of
you see similar phenomenon? What would be the best way to debug this?
I have attached the generated Java code.
Thanks in advance,
Gábor
On 9 May 2016 at 20:41, Gábor Horváth wrote:
> Hi,
>
> Thank you for your support, I was able to solve this issue :)
>
> Gábor
>
> O
apache.flink.api.java.typeutils.PojoTypeInfo.createSerializer(PojoTypeInfo.java:306)
> > at org.apache.flink.api.java.DataSet.collect(DataSet.java:407)
> > at org.apache.flink.api.java.DataSet.print(DataSet.java:1605)
> > at
> >
> >
> org.apache.flink.examples.java.wordco
Hi!
I have created a proof of concept implementation of my GSoC project [1]:
introducing code generation to the serializers. The code is available here
[2]. Unfortunately I have run into a problem that I am unable to debug. I
generated some code that I compiled using the Janino compiler [4]. I did
Hi,
The GSoC project proposal was accepted! Thank you for all your support. I
will do my best to live up to the challenges and deliver everything that
way planned for this summer.
Best Regards,
Gábor
On 20 April 2016 at 16:18, Gábor Horváth wrote:
> On the second thought I think you are ri
the TypeInformation in Scala?
> I think we need a way to replace Serializer implementations anyway unless
> the generated serializers are compatible to the current ones.
>
> 2016-04-20 15:53 GMT+02:00 Gábor Horváth :
>
> > Hi Fabian,
> >
> > I agree that it would be aw
; TypeInformations for types with overridden serializers / comparators.
> This would require some design document and discussion in the community.
>
> Cheers, Fabian
>
>
>
>
>
> 2016-04-18 21:19 GMT+02:00 Gábor Horváth :
>
> > Unfortunately making code generation a separ
e I am skeptical. We have seen IDE compilation issues with
> > projects
> > >>> using this setup and have decided that the community-wide potential
> IDE
> > >>> setup pain outweighs the individual implementation convenience with
> > >> Scala.
>
] http://unkrig.de/w/Janino
[2]
https://github.com/apache/flink/blob/master/flink-libraries/flink-table/src/main/scala/org/apache/flink/api/table/codegen/CodeGenerator.scala
On 18 March 2016 at 19:37, Gábor Horváth wrote:
> Thank you! I finalized the project.
>
>
> On 18 March 2016 at 1
hank you I will definitely look into the code.
> >
> > Regards,
> > Timo
> >
> > [1] http://unkrig.de/w/Janino
> > [2]
> >
> https://github.com/apache/flink/blob/master/flink-libraries/flink-table/src/main/scala/org/apache/flink/api/table/codegen/CodeGe
looking for.
Thanks in advance,
Gábor Horváth
[1]
https://docs.google.com/document/d/1VC8lCeErx9kI5lCMPiUn625PO0rxR-iKlVqtt3hkVnk
[2]
https://docs.google.com/document/d/1sITIShmJMGegzAjGqFuwiN_iw1urwykKsLiacokxSw0
, 2016 at 11:16 AM, Gábor Horváth
> wrote:
>
> > Hi,
> >
> > I have updated this draft to include preliminary benchmarks, mentioned
> the
> > interaction of annotations with savepoints, extended it with a timeline,
> > and some notes about scala case classes.
&g
Hi,
I have updated this draft to include preliminary benchmarks, mentioned the
interaction of annotations with savepoints, extended it with a timeline,
and some notes about scala case classes.
Regards,
Gábor
On 9 March 2016 at 16:12, Gábor Horváth wrote:
> Hi!
>
> As far as I ca
Hi!
As far as I can see the formatting was not correct in my previous mail. A
better formatted version is available here:
https://docs.google.com/document/d/1VC8lCeErx9kI5lCMPiUn625PO0rxR-iKlVqtt3hkVnk
Sorry for that.
Regards,
Gábor
On 9 March 2016 at 15:51, Gábor Horváth wrote:
> Hi,I
in JIRA (should
> > be
> > > labeled with gsoc2016).
> > > I am also not sure if any of the Flink committers signed up as a GSoC
> > > mentor.
> > > Maybe it is still time to do that but as it looks right now there are
> no
> > > GSoC projects offered by
Hi,I did not want to send this proposal out before the I have some initial
benchmarks, but this issue was mentioned on the mailing list (
http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/Tuple-performance-and-the-curious-JIT-compiler-td10666.html),
and I wanted to make this informatio
Hi!
I am planning to do GSoC and I would like to work on the serializers. More
specifically I would like to implement code generation. I am planning to
send the first draft of the proposal to the mailing list early next week.
If everything is going well, that will include some preliminary benchmar
18 matches
Mail list logo
