Hadn't thought about that but it makes perfect sense. Very handy.
On Mon, Apr 13, 2015 at 12:02 PM, Aljoscha Krettek
wrote:
> @Till: Correct
>
> On Mon, Apr 13, 2015 at 10:52 AM, Till Rohrmann
> wrote:
> > IMO the symbol notation makes it slightly easier to write Table API
> > expressions, beca
@Till: Correct
On Mon, Apr 13, 2015 at 10:52 AM, Till Rohrmann wrote:
> IMO the symbol notation makes it slightly easier to write Table API
> expressions, because the IDE can assist you in what operations are
> supported by the expression DSL whereas the string notation will only give
> you a syn
IMO the symbol notation makes it slightly easier to write Table API
expressions, because the IDE can assist you in what operations are
supported by the expression DSL whereas the string notation will only give
you a syntax error upon compilation, right?
On Mon, Apr 13, 2015 at 10:42 AM, Maximilian
'Symbol is actually syntactic sugar for Symbol("Symbol") which is part of
the Scala standard library. It is a core feature of Scala which IMO is
perfectly fine to use. I'm not sure whether it makes the expression much
easier to read but it is a neat feature already in place.
@Stephan: As far as I
I am not a deep Scala progammer either, but I think the symbols are a
pretty wide-spread concept.
For example, the Scalding tuple API makes heavy use of them as well.
That said, I do like the idea that the Scala Table API supports the string
variant as well, for homogeneity.
On Sun, Apr 12, 2015
Hey all,
I am not very proficient with Scala and have some questions regarding the
Scala Table API:
The logical queries in the Java API are all String-based, e.g.
table.groupBy("word")
In the Scala API, this works as well, but what's further possible is this:
expr.groupBy('word)
For comparisi
