[
https://issues.apache.org/jira/browse/FLUME-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13691652#comment-13691652
]
Israel Ekpo commented on FLUME-1687:
------------------------------------
Thanks Mike.
I did get a chance to review your comments. I think that is a good idea.
I would like to add load(List<Event> events) that accepts multiple events at
once.
I was unavailable these last few weeks.
It is probably late now to make 1.4.
I can submit an update patch in a week that we can put in the next release.
Another thing I am also working on is a HTTP client that we can use for both
Solr and ElasticSearch sinks so that we are not tightly coupled with
dependencies that can break if the server version is not the same as what the
client/sink is using.
> ApacheSolrSink
> --------------
>
> Key: FLUME-1687
> URL: https://issues.apache.org/jira/browse/FLUME-1687
> Project: Flume
> Issue Type: New Feature
> Components: Sinks+Sources
> Affects Versions: v1.2.0, v1.4.0
> Reporter: wolfgang hoschek
> Assignee: Israel Ekpo
> Attachments: flume-new-feature-dependencies.zip,
> flume-new-features-1.3.1.jar, flume-new-features-1.3.1-sources.jar
>
>
> Some use cases need near real time full text indexing of data through Flume
> into Solr, where a Flume sink can write directly to a Solr search server.
> This is a scalable way to provide low latency querying and data acquisition.
> It complements (rather than replaces) use cases based on Map Reduce batch
> analysis of HDFS data.
> Apache Solr has a client API that uses REST to add documents to a Solr
> server, which in turn is based on Lucene. A Solr Sink can extract documents
> from flume events and forward them to Solr.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
