Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of jack.krupansky@gmail.com
 designates 209.85.212.176 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <000001d06a5b$8f497ab0$addc7010$@whishworks.com>
References: <000001d06a5b$8f497ab0$addc7010$@whishworks.com>
Date: Sun, 29 Mar 2015 16:25:31 -0400
Message-ID: 
 <CAOxAL6374gcV1aYc2VXYM4a2pC1z_Gg_poSC9MhWKXQxHY_oMQ@mail.gmail.com>
Subject: Re: Structured and Unstructured data indexing in SolrCloud
From: Jack Krupansky <jack.krupansky@gmail.com>
To: solr-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=e89a8f3b9f65c27f020512732a65

--e89a8f3b9f65c27f020512732a65
Content-Type: text/plain; charset=UTF-8

The first step is to work out the queries that you wish to perform - that
will determine how the data should be organized in the Solr schema.

-- Jack Krupansky

On Sun, Mar 29, 2015 at 4:04 PM, Vijay Bhoomireddy <
vijaya.bhoomireddy@whishworks.com> wrote:

> Hi,
>
>
>
> We have a requirement where both structured and unstructured data comes
> into
> the system. We need to index both of them and then enable search
> functionality on it. We are using SolrCloud on Hadoop platform. For
> structured data, we are planning to put the data into HBase and for
> unstructured, directly into HDFS.
>
>
>
> My question is how to index these sources under a single Solr core? Would
> that be possible to index both structured and unstructured data under a
> single core/collection in SolrCloud and then enable search functionality
> over that index?
>
>
>
> Thanks in advance.
>
>
> --
> The contents of this e-mail are confidential and for the exclusive use of
> the intended recipient. If you receive this e-mail in error please delete
> it from your system immediately and notify us either by e-mail or
> telephone. You should not copy, forward or otherwise disclose the content
> of the e-mail. The views expressed in this communication may not
> necessarily be the view held by WHISHWORKS.
>

--e89a8f3b9f65c27f020512732a65--