# Bug Report For ElasticSearch 0.15.0 ( JsonParseException: Invalid shared name reference )

**URL:** <https://discuss.elastic.co/t/bug-report-for-elasticsearch-0-15-0-jsonparseexception-invalid-shared-name-reference/4019>\
**Category:** Elasticsearch\
**Created:** [March 3, 2011, 9:36am UTC](https://discuss.elastic.co/t/bug-report-for-elasticsearch-0-15-0-jsonparseexception-invalid-shared-name-reference/4019 "2011-03-03T09:36:52Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Abdurrahim\_Eke](https://avatars.discourse-cdn.com/v4/letter/a/3bc359/32.png) [@Abdurrahim\_Eke](https://discuss.elastic.co/u/Abdurrahim_Eke)\
**Post date:** [March 3, 2011, 9:36am UTC](https://discuss.elastic.co/t/bug-report-for-elasticsearch-0-15-0-jsonparseexception-invalid-shared-name-reference/4019/1 "2011-03-03T09:36:52Z")

</div>

Hi,

I have found an interesting bug during importing data from a database  
to ElasticSearch.

We are using java api to create indexes and index data on  
ElasticSearch,

The implemented , re-creatable test scenario is as follows :  
You can find the test java code , test output and elastic search  
configuration on : [https://gist.github.com/852536](https://gist.github.com/852536)

With fresh ElasticSearch 0.15.0 server , with no old data , no old  
logs

1. axios\_views index is created ( with default configuration of es  
api , we don't add any configuration )
2. following index operations are done in order:  
2.a index to type leo\_airports props {prop\_0=a, prop\_1=a, ... ,  
prop\_63=aa , prop\_64=a} ( total 65 props )  
2.b index to type leo\_cities props {prop\_0=a} ( total 1 props )  
2.c index to type leo\_airports props {prop\_0=a, prop\_1=a, ... ,  
prop\_63=aa , prop\_64=a} ( total 65 props )  
2.d index to type leo\_cities props {prop\_0=a} ( total 1 props )
3. All 2.a , 2.b , 2.c index operations are done successfully, but  
when 2.d index operation is done following error occurs :

...  
Caused by: org.elasticsearch.common.jackson.JsonParseException:  
Invalid shared name reference 17; only got 0 names in buffer (invalid  
content)  
at [Source: [B@17b6643; line: 1, column: 7]  
at  
org.elasticsearch.common.jackson.JsonParser.\_constructError(JsonParser.java:  
1213)  
at

Important notes :  
Note 1 . The error does not occur if 64 props is indexed to  
leo\_airports type, 1 prop indexed to leo\_cities type  
Note 2 . The error does not occur if 65 props is indexed to  
leo\_airports type, 65 props indexed to leo\_cities type  
Note 3 . The error does not occur if leo\_cities uses different prop  
name , sample : b\_prop\_0:a  
Note 4. The error does not occur if 2.c index is not done  
Note 5. The error does not occur with ElasticSearch 0.14.4 , 0.14.2  
Note 6. The error occurs with ElasticSearch 0.15.0, 0.15.1  
Note 7. You can find the test java code , test output and elastic  
search configuration on : [https://gist.github.com/852536](https://gist.github.com/852536)

This is one of the most interesting bugs I have found 🙂

Regards,  
Abdurrahim Eke  
[iFountain.com](http://iFountain.com)

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [March 3, 2011, 6:31pm UTC](https://discuss.elastic.co/t/bug-report-for-elasticsearch-0-15-0-jsonparseexception-invalid-shared-name-reference/4019/2 "2011-03-03T18:31:13Z")

</div>

Indeed!, very interesting... . I managed to extract a pure test case that shows the Jackson bug when using Smile format. I will talk to Tatu and report back.  
On Thursday, March 3, 2011 at 11:36 AM, Abdurrahim Eke wrote:

> Hi,
> 
> I have found an interesting bug during importing data from a database  
> to Elasticsearch.
> 
> We are using java api to create indexes and index data on  
> Elasticsearch,
> 
> The implemented , re-creatable test scenario is as follows :  
> You can find the test java code , test output and Elasticsearch  
> configuration on : [EsBugTest · GitHub](https://gist.github.com/852536)
> 
> With fresh Elasticsearch 0.15.0 server , with no old data , no old  
> logs
> 
> 1. axios\_views index is created ( with default configuration of es  
> api , we don't add any configuration )
> 2. following index operations are done in order:  
> 2.a index to type leo\_airports props {prop\_0=a, prop\_1=a, ... ,  
> prop\_63=aa , prop\_64=a} ( total 65 props )  
> 2.b index to type leo\_cities props {prop\_0=a} ( total 1 props )  
> 2.c index to type leo\_airports props {prop\_0=a, prop\_1=a, ... ,  
> prop\_63=aa , prop\_64=a} ( total 65 props )  
> 2.d index to type leo\_cities props {prop\_0=a} ( total 1 props )
> 3. All 2.a , 2.b , 2.c index operations are done successfully, but  
> when 2.d index operation is done following error occurs :
> 
> ...  
> Caused by: org.elasticsearch.common.jackson.JsonParseException:  
> Invalid shared name reference 17; only got 0 names in buffer (invalid  
> content)  
> at [Source: [B@17b6643; line: 1, column: 7]  
> at  
> org.elasticsearch.common.jackson.JsonParser.\_constructError(JsonParser.java:  
> 1213)  
> at
> 
> Important notes :  
> Note 1 . The error does not occur if 64 props is indexed to  
> leo\_airports type, 1 prop indexed to leo\_cities type  
> Note 2 . The error does not occur if 65 props is indexed to  
> leo\_airports type, 65 props indexed to leo\_cities type  
> Note 3 . The error does not occur if leo\_cities uses different prop  
> name , sample : b\_prop\_0:a  
> Note 4. The error does not occur if 2.c index is not done  
> Note 5. The error does not occur with Elasticsearch 0.14.4 , 0.14.2  
> Note 6. The error occurs with Elasticsearch 0.15.0, 0.15.1  
> Note 7. You can find the test java code , test output and elastic  
> search configuration on : [EsBugTest · GitHub](https://gist.github.com/852536)
> 
> This is one of the most interesting bugs I have found 🙂
> 
> Regards,  
> Abdurrahim Eke  
> [iFountain.com](http://iFountain.com)

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [March 3, 2011, 7:28pm UTC](https://discuss.elastic.co/t/bug-report-for-elasticsearch-0-15-0-jsonparseexception-invalid-shared-name-reference/4019/3 "2011-03-03T19:28:49Z")

</div>

Here is the issue in jackson: [http://jira.codehaus.org/browse/JACKSON-525](http://jira.codehaus.org/browse/JACKSON-525).  
On Thursday, March 3, 2011 at 8:31 PM, Shay Banon wrote:

> Indeed!, very interesting... . I managed to extract a pure test case that shows the Jackson bug when using Smile format. I will talk to Tatu and report back.  
> On Thursday, March 3, 2011 at 11:36 AM, Abdurrahim Eke wrote:
> 
> > Hi,
> > 
> > I have found an interesting bug during importing data from a database  
> > to Elasticsearch.
> > 
> > We are using java api to create indexes and index data on  
> > Elasticsearch,
> > 
> > The implemented , re-creatable test scenario is as follows :  
> > You can find the test java code , test output and Elasticsearch  
> > configuration on : [EsBugTest · GitHub](https://gist.github.com/852536)
> > 
> > With fresh Elasticsearch 0.15.0 server , with no old data , no old  
> > logs
> > 
> > 1. axios\_views index is created ( with default configuration of es  
> > api , we don't add any configuration )
> > 2. following index operations are done in order:  
> > 2.a index to type leo\_airports props {prop\_0=a, prop\_1=a, ... ,  
> > prop\_63=aa , prop\_64=a} ( total 65 props )  
> > 2.b index to type leo\_cities props {prop\_0=a} ( total 1 props )  
> > 2.c index to type leo\_airports props {prop\_0=a, prop\_1=a, ... ,  
> > prop\_63=aa , prop\_64=a} ( total 65 props )  
> > 2.d index to type leo\_cities props {prop\_0=a} ( total 1 props )
> > 3. All 2.a , 2.b , 2.c index operations are done successfully, but  
> > when 2.d index operation is done following error occurs :
> > 
> > ...  
> > Caused by: org.elasticsearch.common.jackson.JsonParseException:  
> > Invalid shared name reference 17; only got 0 names in buffer (invalid  
> > content)  
> > at [Source: [B@17b6643; line: 1, column: 7]  
> > at  
> > org.elasticsearch.common.jackson.JsonParser.\_constructError(JsonParser.java:  
> > 1213)  
> > at
> > 
> > Important notes :  
> > Note 1 . The error does not occur if 64 props is indexed to  
> > leo\_airports type, 1 prop indexed to leo\_cities type  
> > Note 2 . The error does not occur if 65 props is indexed to  
> > leo\_airports type, 65 props indexed to leo\_cities type  
> > Note 3 . The error does not occur if leo\_cities uses different prop  
> > name , sample : b\_prop\_0:a  
> > Note 4. The error does not occur if 2.c index is not done  
> > Note 5. The error does not occur with Elasticsearch 0.14.4 , 0.14.2  
> > Note 6. The error occurs with Elasticsearch 0.15.0, 0.15.1  
> > Note 7. You can finnd the test java code , test output and elastic  
> > search configuration on : [EsBugTest · GitHub](https://gist.github.com/852536)
> > 
> > This is one of the most interesting bugs I have found 🙂
> > 
> > Regards,  
> > Abdurrahim Eke  
> > [iFountain.com](http://iFountain.com)

---

<div class="post-metadata">

**Author:** ![Abdurrahim\_Eke](https://avatars.discourse-cdn.com/v4/letter/a/3bc359/32.png) [@Abdurrahim\_Eke](https://discuss.elastic.co/u/Abdurrahim_Eke)\
**Post date:** [March 4, 2011, 7:09am UTC](https://discuss.elastic.co/t/bug-report-for-elasticsearch-0-15-0-jsonparseexception-invalid-shared-name-reference/4019/4 "2011-03-04T07:09:45Z")

</div>

Hi Shay,

Thanks for the fast response, it seems that the issue is fixed on  
Jackson side.  
I wonder if the fix will be included in the next version of  
Elasticsearch or later.

Regards,

On Mar 3, 9:28 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote:

> Here is the issue in jackson:[http://jira.codehaus.org/browse/JACKSON-525](http://jira.codehaus.org/browse/JACKSON-525).
> 
> On Thursday, March 3, 2011 at 8:31 PM, Shay Banon wrote:
> 
> > Indeed!, very interesting... . I managed to extract a pure test case that shows the Jackson bug when using Smile format. I will talk to Tatu and report back.  
> > On Thursday, March 3, 2011 at 11:36 AM, Abdurrahim Eke wrote:
> > 
> > > Hi,
> 
> > > I have found an interesting bug during importing data from a database  
> > > to Elasticsearch.
> 
> > > We are using java api to create indexes and index data on  
> > > Elasticsearch,
> 
> > > The implemented , re-creatable test scenario is as follows :  
> > > You can find the test java code , test output and Elasticsearch  
> > > configuration on :[EsBugTest · GitHub](https://gist.github.com/852536)
> 
> > > With fresh Elasticsearch 0.15.0 server , with no old data , no old  
> > > logs
> 
> > > 1. axios\_views index is created ( with default configuration of es  
> > > api , we don't add any configuration )
> > > 2. following index operations are done in order:  
> > > 2.a index to type leo\_airports props {prop\_0=a, prop\_1=a, ... ,  
> > > prop\_63=aa , prop\_64=a} ( total 65 props )  
> > > 2.b index to type leo\_cities props {prop\_0=a} ( total 1 props )  
> > > 2.c index to type leo\_airports props {prop\_0=a, prop\_1=a, ... ,  
> > > prop\_63=aa , prop\_64=a} ( total 65 props )  
> > > 2.d index to type leo\_cities props {prop\_0=a} ( total 1 props )
> > > 3. All 2.a , 2.b , 2.c index operations are done successfully, but  
> > > when 2.d index operation is done following error occurs :
> 
> > > ...  
> > > Caused by: org.elasticsearch.common.jackson.JsonParseException:  
> > > Invalid shared name reference 17; only got 0 names in buffer (invalid  
> > > content)  
> > > at [Source: [B@17b6643; line: 1, column: 7]  
> > > at  
> > > org.elasticsearch.common.jackson.JsonParser.\_constructError(JsonParser.java:  
> > > 1213)  
> > > at
> 
> > > Important notes :  
> > > Note 1 . The error does not occur if 64 props is indexed to  
> > > leo\_airports type, 1 prop indexed to leo\_cities type  
> > > Note 2 . The error does not occur if 65 props is indexed to  
> > > leo\_airports type, 65 props indexed to leo\_cities type  
> > > Note 3 . The error does not occur if leo\_cities uses different prop  
> > > name , sample : b\_prop\_0:a  
> > > Note 4. The error does not occur if 2.c index is not done  
> > > Note 5. The error does not occur with Elasticsearch 0.14.4 , 0.14.2  
> > > Note 6. The error occurs with Elasticsearch 0.15.0, 0.15.1  
> > > Note 7. You can finnd the test java code , test output and elastic  
> > > search configuration on :[EsBugTest · GitHub](https://gist.github.com/852536)
> 
> > > This is one of the most interesting bugs I have found 🙂
> 
> > > Regards,  
> > > Abdurrahim Eke  
> > > [iFountain.com](http://iFountain.com)

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [March 4, 2011, 3:47pm UTC](https://discuss.elastic.co/t/bug-report-for-elasticsearch-0-15-0-jsonparseexception-invalid-shared-name-reference/4019/5 "2011-03-04T15:47:51Z")

</div>

Yes, once jackson 1.7.4 is released, then both 0.15 branch and master will be updated with it.  
On Friday, March 4, 2011 at 9:09 AM, Abdurrahim Eke wrote:

> Hi Shay,
> 
> Thanks for the fast response, it seems that the issue is fixed on  
> Jackson side.  
> I wonder if the fix will be included in the next version of  
> Elasticsearch or later.
> 
> Regards,
> 
> On Mar 3, 9:28 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote:
> 
> > Here is the issue in jackson:[http://jira.codehaus.org/browse/JACKSON-525](http://jira.codehaus.org/browse/JACKSON-525).
> > 
> > On Thursday, March 3, 2011 at 8:31 PM, Shay Banon wrote:
> > 
> > > Indeed!, very interesting... . I managed to extract a pure test case that shows the Jackson bug when using Smile format. I will talk to Tatu and report back.  
> > > On Thursday, March 3, 2011 at 11:36 AM, Abdurrahim Eke wrote:
> > > 
> > > > Hi,
> > 
> > > > I have found an interesting bug during importing data from a database  
> > > > to Elasticsearch.
> > 
> > > > We are using java api to create indexes and index data on  
> > > > Elasticsearch,
> > 
> > > > The implemented , re-creatable test scenario is as follows :  
> > > > You can find the test java code , test output and Elasticsearch  
> > > > configuration on :[EsBugTest · GitHub](https://gist.github.com/852536)
> > 
> > > > With fresh Elasticsearch 0.15.0 server , with no old data , no old  
> > > > logs
> > 
> > > > 1. axios\_views index is created ( with default configuration of es  
> > > > api , we don't add any configuration )
> > > > 2. following index operations are done in order:  
> > > > 2.a index to type leo\_airports props {prop\_0=a, prop\_1=a, ... ,  
> > > > prop\_63=aa , prop\_64=a} ( total 65 props )  
> > > > 2.b index to type leo\_cities props {prop\_0=a} ( total 1 props )  
> > > > 2.c index to type leo\_airports props {prop\_0=a, prop\_1=a, ... ,  
> > > > prop\_63=aa , prop\_64=a} ( total 65 props )  
> > > > 2.d index to type leo\_cities props {prop\_0=a} ( total 1 props )
> > > > 3. All 2.a , 2.b , 2.c index operations are done successfully, but  
> > > > when 2.d index operation is done following error occurs :
> > 
> > > > ...  
> > > > Caused by: org.elasticsearch.common.jackson.JsonParseException:  
> > > > Invalid shared name reference 17; only got 0 names in buffer (invalid  
> > > > content)  
> > > > at [Source: [B@17b6643; line: 1, column: 7]  
> > > > at  
> > > > org.elasticsearch.common.jackson.JsonParser.\_constructError(JsonParser.java:  
> > > > 1213)  
> > > > at
> > 
> > > > Important notes :  
> > > > Note 1 . The error does not occur if 64 props is indexed to  
> > > > leo\_airports type, 1 prop indexed to leo\_cities type  
> > > > Note 2 . The error does not occur if 65 props is indexed to  
> > > > leo\_airports type, 65 props indexed to leo\_cities type  
> > > > Note 3 . The error does not occur if leo\_cities uses different prop  
> > > > name , sample : b\_prop\_0:a  
> > > > Note 4. The error does not occur if 2.c index is not done  
> > > > Note 5. The error does not occur with Elasticsearch 0.14.4 , 0.14.2  
> > > > Note 6. The error occurs with Elasticsearch 0.15.0, 0.15.1  
> > > > Note 7. You can finnd the test java code , test output and elastic  
> > > > search configuration on :[EsBugTest · GitHub](https://gist.github.com/852536)
> > 
> > > > This is one of the most interesting bugs I have found 🙂
> > 
> > > > Regards,  
> > > > Abdurrahim Eke  
> > > > [iFountain.com](http://iFountain.com)

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [March 5, 2011, 8:47am UTC](https://discuss.elastic.co/t/bug-report-for-elasticsearch-0-15-0-jsonparseexception-invalid-shared-name-reference/4019/6 "2011-03-05T08:47:26Z")

</div>

Heya,

Jackson 1.7.4 was released, updated both master and 0.15 branch to it. 0.15.2 will be out early next week.

-shay.banon  
On Friday, March 4, 2011 at 5:47 PM, Shay Banon wrote:

> Yes, once jackson 1.7.4 is released, then both 0.15 branch and master will be updated with it.  
> On Friday, March 4, 2011 at 9:09 AM, Abdurrahim Eke wrote:
> 
> > Hi Shay,
> > 
> > Thanks for the fast response, it seems that the issue is fixed on  
> > Jackson side.  
> > I wonder if the fix will be included in the next version of  
> > Elasticsearch or later.
> > 
> > Regards,
> > 
> > On Mar 3, 9:28 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote:
> > 
> > > Here is the issue in jackson:[http://jira.codehaus.org/browse/JACKSON-525](http://jira.codehaus.org/browse/JACKSON-525).
> > > 
> > > On Thursday, March 3, 2011 at 8:31 PM, Shay Banon wrote:
> > > 
> > > > Indeed!, very interesting... . I managed to extract a pure test case that shows the Jackson bug when using Smile format. I will talk to Tatu and report back.  
> > > > On Thursday, March 3, 2011 at 11:36 AM, Abdurrahim Eke wrote:
> > > > 
> > > > > Hi,
> > > 
> > > > > I have found an interesting bug during importing data from a database  
> > > > > to Elasticsearch.
> > > 
> > > > > We are using java api to create indexes and index data on  
> > > > > Elasticsearch,
> > > 
> > > > > The implemented , re-creatable test scenario is as follows :  
> > > > > You can find the test java code , test output and Elasticsearch  
> > > > > configuration on :[EsBugTest · GitHub](https://gist.github.com/852536)
> > > 
> > > > > With fresh Elasticsearch 0.15.0 server , with no old data , no old  
> > > > > logs
> > > 
> > > > > 1. axios\_views index is created ( with default configuration of es  
> > > > > api , we don't add any configuration )
> > > > > 2. following index operations are done in order:  
> > > > > 2.a index to type leo\_airports props {prop\_0=a, prop\_1=a, ... ,  
> > > > > prop\_63=aa , prop\_64=a} ( total 65 props )  
> > > > > 2.b index to type leo\_cities props {prop\_0=a} ( total 1 props )  
> > > > > 2.c index to type leo\_airports props {prop\_0=a, prop\_1=a, ... ,  
> > > > > prop\_63=aa , prop\_64=a} ( total 65 props )  
> > > > > 2.d index to type leo\_cities props {prop\_0=a} ( total 1 props )
> > > > > 3. All 2.a , 2.b , 2.c index operations are done successfully, but  
> > > > > when 2.d index operation is done following error occurs :
> > > 
> > > > > ...  
> > > > > Caused by: org.elasticsearch.common.jackson.JsonParseException:  
> > > > > Invalid shared name reference 17; only got 0 names in buffer (invalid  
> > > > > content)  
> > > > > at [Source: [B@17b6643; line: 1, column: 7]  
> > > > > at  
> > > > > org.elasticsearch.common.jackson.JsonParser.\_constructError(JsonParser.java:  
> > > > > 1213)  
> > > > > at
> > > 
> > > > > Important notes :  
> > > > > Note 1 . The error does not occur if 64 props is indexed to  
> > > > > leo\_airports type, 1 prop indexed to leo\_cities type  
> > > > > Note 2 . The error does not occur if 65 props is indexed to  
> > > > > leo\_airports type, 65 props indexed to leo\_cities type  
> > > > > Note 3 . The error does not occur if leo\_cities uses different prop  
> > > > > name , sample : b\_prop\_0:a  
> > > > > Note 4. The error does not occur if 2.c index is not done  
> > > > > Note 5. The error does not occur with Elasticsearch 0.14.4 , 0.14.2  
> > > > > Note 6. The error occurs with Elasticsearch 0.15.0, 0.15.1  
> > > > > Note 7. You can finnd the test java code , test output and elastic  
> > > > > search configuration on :[EsBugTest · GitHub](https://gist.github.com/852536)
> > > 
> > > > > This is one of the most interesting bugs I have found 🙂
> > > 
> > > > > Regards,  
> > > > > Abdurrahim Eke  
> > > > > [iFountain.com](http://iFountain.com)

---

<div class="post-metadata">

**Author:** ![Abdurrahim\_Eke](https://avatars.discourse-cdn.com/v4/letter/a/3bc359/32.png) [@Abdurrahim\_Eke](https://discuss.elastic.co/u/Abdurrahim_Eke)\
**Post date:** [March 11, 2011, 8:29am UTC](https://discuss.elastic.co/t/bug-report-for-elasticsearch-0-15-0-jsonparseexception-invalid-shared-name-reference/4019/7 "2011-03-11T08:29:17Z")

</div>

Hi Shay,

I confirm that both the unit tests and the real scenario runs  
successfully now, no sign of the bug exists.

Many thanks,  
Abdurrahim Eke,  
[iFountain.com](http://iFountain.com)

On Mar 5, 10:47 am, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote:

> Heya,
> 
> Jackson 1.7.4 was released, updated both master and 0.15 branch to it. 0.15.2 will be out early next week.
> 
> -shay.banon
> 
> On Friday, March 4, 2011 at 5:47 PM, Shay Banon wrote:
> 
> > Yes, once jackson 1.7.4 is released, then both 0.15 branch and master will be updated with it.  
> > On Friday, March 4, 2011 at 9:09 AM, Abdurrahim Eke wrote:
> > 
> > > Hi Shay,
> 
> > > Thanks for the fast response, it seems that the issue is fixed on  
> > > Jackson side.  
> > > I wonder if the fix will be included in the next version of  
> > > Elasticsearch or later.
> 
> > > Regards,
> 
> > > On Mar 3, 9:28 pm, Shay Banon [shay.ba...@elasticsearch.com](mailto:shay.ba...@elasticsearch.com) wrote:
> > > 
> > > > Here is the issue in jackson:[http://jira.codehaus.org/browse/JACKSON-525](http://jira.codehaus.org/browse/JACKSON-525).
> 
> > > > On Thursday, March 3, 2011 at 8:31 PM, Shay Banon wrote:
> > > > 
> > > > > Indeed!, very interesting... . I managed to extract a pure test case that shows the Jackson bug when using Smile format. I will talk to Tatu and report back.  
> > > > > On Thursday, March 3, 2011 at 11:36 AM, Abdurrahim Eke wrote:
> > > > > 
> > > > > > Hi,
> 
> > > > > > I have found an interesting bug during importing data from a database  
> > > > > > to Elasticsearch.
> 
> > > > > > We are using java api to create indexes and index data on  
> > > > > > Elasticsearch,
> 
> > > > > > The implemented , re-creatable test scenario is as follows :  
> > > > > > You can find the test java code , test output and Elasticsearch  
> > > > > > configuration on :[EsBugTest · GitHub](https://gist.github.com/852536)
> 
> > > > > > With fresh Elasticsearch 0.15.0 server , with no old data , no old  
> > > > > > logs
> 
> > > > > > 1. axios\_views index is created ( with default configuration of es  
> > > > > > api , we don't add any configuration )
> > > > > > 2. following index operations are done in order:  
> > > > > > 2.a index to type leo\_airports props {prop\_0=a, prop\_1=a, ... ,  
> > > > > > prop\_63=aa , prop\_64=a} ( total 65 props )  
> > > > > > 2.b index to type leo\_cities props {prop\_0=a} ( total 1 props )  
> > > > > > 2.c index to type leo\_airports props {prop\_0=a, prop\_1=a, ... ,  
> > > > > > prop\_63=aa , prop\_64=a} ( total 65 props )  
> > > > > > 2.d index to type leo\_cities props {prop\_0=a} ( total 1 props )
> > > > > > 3. All 2.a , 2.b , 2.c index operations are done successfully, but  
> > > > > > when 2.d index operation is done following error occurs :
> 
> > > > > > ...  
> > > > > > Caused by: org.elasticsearch.common.jackson.JsonParseException:  
> > > > > > Invalid shared name reference 17; only got 0 names in buffer (invalid  
> > > > > > content)  
> > > > > > at [Source: [B@17b6643; line: 1, column: 7]  
> > > > > > at  
> > > > > > org.elasticsearch.common.jackson.JsonParser.\_constructError(JsonParser.java:  
> > > > > > 1213)  
> > > > > > at
> 
> > > > > > Important notes :  
> > > > > > Note 1 . The error does not occur if 64 props is indexed to  
> > > > > > leo\_airports type, 1 prop indexed to leo\_cities type  
> > > > > > Note 2 . The error does not occur if 65 props is indexed to  
> > > > > > leo\_airports type, 65 props indexed to leo\_cities type  
> > > > > > Note 3 . The error does not occur if leo\_cities uses different prop  
> > > > > > name , sample : b\_prop\_0:a  
> > > > > > Note 4. The error does not occur if 2.c index is not done  
> > > > > > Note 5. The error does not occur with Elasticsearch 0.14.4 , 0.14.2  
> > > > > > Note 6. The error occurs with Elasticsearch 0.15.0, 0.15.1  
> > > > > > Note 7. You can finnd the test java code , test output and elastic  
> > > > > > search configuration on :[EsBugTest · GitHub](https://gist.github.com/852536)
> 
> > > > > > This is one of the most interesting bugs I have found 🙂
> 
> > > > > > Regards,  
> > > > > > Abdurrahim Eke  
> > > > > > [iFountain.com](http://iFountain.com)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 4:10am UTC](https://discuss.elastic.co/t/bug-report-for-elasticsearch-0-15-0-jsonparseexception-invalid-shared-name-reference/4019/8 "2017-07-06T04:10:19Z")

</div>