Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Drill, mail # dev - Parser


Copy link to this message
-
Re: Parser
David Alves 2012-09-12, 19:12
the more detailed version can be found here: http://codahale.com/downloads/email-to-donald.txt

My intention was not to stay that it was impossible to make performant apps with scala, I've used it with mixed success in a stream processor implementation. My comment was intended to be similar in tone to yours: java because of the larger audience, increased predictability and familiarity.

-david
On Sep 12, 2012, at 2:06 PM, Ted Dunning <[EMAIL PROTECTED]> wrote:

> Interesting that they seem to have edited that rant to something a bit
> different in tone.
>
> My own tendency is to stay with low-risk, large audience tools.  I am very
> productive with Java, largely due to my IDE overcoming most of the
> verbosity for me, but I can't imagine that it is impossible to improve.
>
> I don't think that it is common knowledge that scala can't be used for
> performant tasks any more than it is common knowledge that Java can't be
> used for performant tasks.  You may have to look deeper to figure out what
> is going on, but I am pretty sure you can achieve high performance.
>
> On Wed, Sep 12, 2012 at 12:00 PM, David Alves <[EMAIL PROTECTED]> wrote:
>
>> While I also love scala, sintax wise, I think it is now pretty common
>> knowledge that it should not be used for high perf applications/large
>> codebases.
>>
>> There is an epic rant on the subject from coda hale of yammer. Yammer
>> changed from being almost all scala to almost all java.
>> http://eng.yammer.com/blog/2011/11/30/scala-at-yammer.html
>>
>> I share this sentiment and also think it applies to other languages like
>> groovy so like maven I think java is the lesser evil.
>>
>> -david
>>
>> On Sep 12, 2012, at 1:53 PM, Michael Hausenblas <
>> [EMAIL PROTECTED]> wrote:
>>
>>>
>>>
>>>> I know that no-one has mentioned this before but what about the build
>> system for drill?
>>>> I'm personally in favor of maven (lesser evil for java IMO).
>>>> I'd be happy to contribute that setup, if needed.
>>>
>>> If codebase mainly in Java, yeah maven (though it feels like it
>> downloads half of the Internet every time).
>>>
>>> But not so fast - did we agree on Java, yet? How about Scala + SBT [1]?
>> Integrates nicely with Java and is soooo much more productive ;)
>>>
>>> Cheers,
>>>         Michael
>>>
>>> [1] http://www.scala-sbt.org/
>>>
>>> --
>>> Michael Hausenblas
>>> Ireland, Europe
>>> http://mhausenblas.info/
>>>
>>> On 12 Sep 2012, at 20:47, David Alves wrote:
>>>
>>>> I know that no-one has mentioned this before but what about the build
>> system for drill?
>>>> I'm personally in favor of maven (lesser evil for java IMO).
>>>> I'd be happy to contribute that setup, if needed.
>>>>
>>>> -david
>>>>
>>>> On Sep 12, 2012, at 1:42 PM, Ted Dunning <[EMAIL PROTECTED]> wrote:
>>>>
>>>>> I see classes in the source tree:
>>>>>
>>>>>
>> https://github.com/ApacheDrill/parser/tree/master/src/org/apache/drill/parsers/impl/drqlantlr/autogen/classes/org/apache/drill/parsers/impl/drqlantlr/autogen
>>>>>
>>>>> Also, I would strongly recommend pulling the antlr source code into an
>>>>> antler source tree.
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Sep 12, 2012 at 11:31 AM, Camuel Gilyadov
>>>>> <[EMAIL PROTECTED]>wrote:
>>>>>
>>>>>> Still work in progress, but anyway -
>> https://github.com/ApacheDrill/parser
>>>>>>
>>>>>> Constructive critique and contributions are welcome
>>>>>>
>>>>
>>>
>>
>>