You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Lior Zeno (JIRA)" <ji...@apache.org> on 2016/07/23 08:29:20 UTC

[jira] [Resolved] (FLUME-1687) ApacheSolrSink

     [ https://issues.apache.org/jira/browse/FLUME-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lior Zeno resolved FLUME-1687.
------------------------------
    Resolution: Implemented

Implemented by FLUME-2070.

> 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-sources.jar, flume-new-features-1.3.1.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 was sent by Atlassian JIRA
(v6.3.4#6332)