I am curious to hear some thoughts on this question. On Wednesday, April 9, 2014 4:05:52 PM UTC-7, Srinivasan Ramaswamy wrote: > > Hi > > I am porting over an existing search system over to elastic search. We > have a few custom requirements for search. I played around with ES RESTful > APIs and then now I am trying out the java client for elastic search. I am > wondering how should i go about implementing all the custom logic, should i > use the java client or write it as a plugin ? I haven't read anything about > writing plugins yet. > > Here are the two approaches i can think of, I am looking for > recommendation from the group. > > 1. I would have a search service layer in between the front end and the ES > cluster. The search service layer will implement the custom logic using the > java api. > 2. Abstract out all the custom logic as a plugin and have the search > service layer just communicate with the plugin through REST as it would > communicate with the vanilla ES cluster. > > With my current understanding, I feel that 2nd approach is better as > plugins have more customization capability compared to the java api. Please > advice. > > Thanks > Srini >
-- 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/da362235-3652-4d72-8080-d89f654ade8c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
