Re: Naming of semantic annotations

2015-01-24 Thread Stephan Ewen
I agree with ForwardFields as well. I vaguely remember that Joe Harjung (when working on the first Scala API version) called it the CopySet. I would assume that ForwardFields is more intuitive to most people. I only mention this, because Joe was one of the few English native speakers in the team

Re: Naming of semantic annotations

2015-01-23 Thread Chesnay Schepler
+1 ForwardedFields On 23.01.2015 22:38, Vasiliki Kalavri wrote: Hi, +1 for ForwardedFields. I like it much more than ConstantFields. I think it makes it clear what the feature does. It's a very cool feature and indeed not advertised a lot. I use it when I remember, but most of the times I forg

Re: Naming of semantic annotations

2015-01-23 Thread Vasiliki Kalavri
Hi, +1 for ForwardedFields. I like it much more than ConstantFields. I think it makes it clear what the feature does. It's a very cool feature and indeed not advertised a lot. I use it when I remember, but most of the times I forget it exists ;) -V. On 23 January 2015 at 22:12, Fabian Hueske w

Naming of semantic annotations

2015-01-23 Thread Fabian Hueske
Hi all, I have a pending pull request (#311) to fix and enable semantic information for functions with nested and Pojo types. Semantic information is used to tell the optimizer about the behavior of user-defined functions. The optimizer can use this information to generate more efficient execution