I think ES Sink using HTTP API is very good approach because there is no version issue. But instead of new sink implementation, how about adding HTTP API feature to sink using ES Transport? (If hostNames start with http address, use HTTP API otherwise use ES Transport)
-- Regards, Chiwan Park On Jan 6, 2014, at 4:48 AM, Paweł <[email protected]> wrote: > Hi, > I started preparing Sink for Elasticsearch that uses HTTP API instead of ES > Transport (https://issues.apache.org/jira/browse/FLUME-2225). I decided to > make few modifications in existing Elasticsearch Sink to make it possible > to switch between Transport Client and Http Client. Do you think it is good > way of introducing that feature or should I just make another elasticsearch > sink which will be almost the same as existing one with one difference (it > will use HTTP API). > > -- > Regards, > Paweł
