This is a simple example to illustrate the point. The real use case: 1. Is a rather large amount of data which I'd like to handle in parallel & also take advantage of es-hadoop's handling of shards. 2. Uses an existing job execution framework & toolset based on hadoop-streaming; I would rather not have a special case to handle it.
Thanks for your feedback & nice work on es-hadoop, started using the Hive integration today as well. --Pete On Monday, May 5, 2014 4:20:29 PM UTC-4, Costin Leau wrote: > > Hi, > > Reading data in JSON format from ES (which I think is what you are > interested in doing) is not available out of the box. > Simply because you can do the same thing directly from the command line > with curl or any http-like client. > One of the reasons behind hadoop-streaming is to allow native clients to > interact with Hadoop, primarily with HDF; since > you are > interacting with ES, why not talk to it directly? > > Am I missing something? > > > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/3bc7c0cb-fd97-402d-9644-97a60b2aa4b7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
