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 noble.paul@gmail.com
 designates 74.125.82.43 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAPCAqaGVOhicrxmohMRGMfn69rkk7QFmzPFg65SkpZ_DOAWMmg@mail.gmail.com>
References: 
 <CAPCAqaGVOhicrxmohMRGMfn69rkk7QFmzPFg65SkpZ_DOAWMmg@mail.gmail.com>
From: Noble Paul <noble.paul@gmail.com>
Date: Thu, 16 Oct 2014 23:40:01 +0530
Message-ID: 
 <CABVqxwBsraz4dL0p-99RCr2C5wnHTk6uxzb_NsNfe_84i43YNQ@mail.gmail.com>
Subject: Re: Custom JSON
To: solr-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=047d7b6da43c62dd3305058e29ac

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

The end point  /update/json/docs is enabled implicitly in Solr irrespective
of the solrconfig.xml
In schemaless the fields are created automatically by solr.

If you have all the fields created in your schema.xml it will work .

if you  need an id field please use a copy field to create one

--Noble

On Thu, Oct 16, 2014 at 8:42 PM, Scott Dawson <sc.e.dawson@gmail.com> wrote:

> Hello,
> I'm trying to use the new custom JSON feature described in
> https://issues.apache.org/jira/browse/SOLR-6304. I'm running Solr 4.10.1.
> It seems that the new feature, or more specifically, the /update/json/docs
> endpoint is not enabled out-of-the-box except in the schema-less example.
> Is there some dependence of the feature on schemaless mode? I've tried
> pulling the endpoint definition and related pieces of the
> example-schemaless solrconfig.xml and adding those to the "standard"
> solrconfig.xml in the main example but I've run into a cascade of issues.
> Right now I'm getting a "This IndexSchema is not mutable" exception when I
> try to post to the /update/json/docs endpoint.
>
> My real question is -- what's the easiest way to get this feature up and
> running quickly and is this documented somewhere? I'm trying to do a quick
> proof-of-concept to verify that we can move from our current flat JSON
> ingestion to a more natural use of structured JSON.
>
> Thanks,
> Scott Dawson
>


-- 
-----------------------------------------------------
Noble Paul

--047d7b6da43c62dd3305058e29ac--