Pujari,

Drill and Druid are attacking very different parts of the problem.  Drill
is all about query language and semantics against flexible data.  Druid is
about a database-like engine with limited query language and optimizer but
really excellent aggregation capabilities.

I don't know of any comparisons, and I really think that such a comparison
would be very hard to do sensibly since it would tend to be completely
disjoint feature and goal lists.


On Tue, May 6, 2014 at 11:23 PM, Timothy Chen <[email protected]> wrote:

> Hi Pujari,
>
> It's hard to compare something without knowing what is your
> requirements and you're trying to achieve.
>
> Just in general though Drill is not ready for production as we are
> moving towards beta, but definitely like to have hands on trying it
> and get more feedback and what usecases people are interested in.
>
> Tim
>
> On Tue, May 6, 2014 at 10:42 AM, Pujari Pradeep - ppujar
> <[email protected]> wrote:
> > Hi All,
> >
> > I attended the first Apache Drill Design meeting and then disconnected.
> My
> > priority was different at that point. This project came a long way since
> > then. I am now evaluating Drill and Druid to use in production. It will
> be
> > a great help, if some one point me to some resource, which compares these
> > two products.
> >
> > Thanks,
> > Pradeep.
> >
> >
> >
> >
> >
> ***************************************************************************
> > The information contained in this communication is confidential, is
> > intended only for the use of the recipient named above, and may be
> legally
> > privileged.
> >
> > If the reader of this message is not the intended recipient, you are
> > hereby notified that any dissemination, distribution or copying of this
> > communication is strictly prohibited.
> >
> > If you have received this communication in error, please resend this
> > communication to the sender and delete the original message or any copy
> > of it from your computer system.
> >
> > Thank You.
> >
> ****************************************************************************
> >
>

Reply via email to