Hi Furkan,

If I were to guess, the XML format is more cross-compatible with different
versions of SolrJ. But it might not be intentional.

In any case, feeding your SolrServer a BinaryResponseParser will switch it
over to javabin.

Michael Della Bitta

Applications Developer

o: +1 646 532 3062

appinions inc.

“The Science of Influence Marketing”

18 East 41st Street

New York, NY 10017

t: @appinions <https://twitter.com/Appinions> | g+:
plus.google.com/appinions<https://plus.google.com/u/0/b/112002776285509593336/112002776285509593336/posts>
w: appinions.com <http://www.appinions.com/>


On Thu, May 8, 2014 at 10:17 AM, Furkan KAMACI <furkankam...@gmail.com>wrote:

> Hi;
>
> I found the reason of weird format at my previous mail. Now I capture the
> data with wireshark and I see that it is pure XML and content type is set
> to application/xml?
>
> Any ideas about why it is not javabin?
>
> Thanks;
> Furkan KAMACI
>
>
> 2014-05-07 22:16 GMT+03:00 Furkan KAMACI <furkankam...@gmail.com>:
>
> > Hmmm, I see that it is like XML format but not. I have added three
> > documents but has something like that:
> >
> > <add>
> > <doc boost="1.0">
> >     <field name="id">id1</field>
> >     <field name="id">id2</field>
> >     <field name="id">id3</field>
> >     <field name="id">id4</field>
> >     <field name="d">d1</field>
> >     <field name="d">d2</field>
> >     <field name="d">d3</field>
> >     <field name="d">d4</field>
> > </doc>
> > <doc boost="1.0"></doc>
> > <doc boost="1.0"></doc>
> > <doc boost="1.0"></doc>
> > </add>
> >
> > is this javabin format? I mean optimizing XML and having a first byte of
> > "2"?
> >
> > Thanks;
> > Furkan KAMACI
> >
> >
> > 2014-05-07 22:04 GMT+03:00 Furkan KAMACI <furkankam...@gmail.com>:
> >
> > Hi;
> >>
> >> I am testing Solrj. I use Solr 4.5.1 and HttpSolrServer for my test. I
> >> just generate some SolrInputDocuments and call add method of server to
> add
> >> them. When  I track the request I see that data is at XML format
> instead of
> >> javabin. Do I miss anything?
> >>
> >> Thanks;
> >> Furkan KAMACI
> >>
> >
> >
>

Reply via email to