# Elastic: Problem with decimal format when indexing from the 64th document (document not indexed)

**URL:** https://discuss.elastic.co/t/elastic-problem-with-decimal-format-when-indexing-from-the-64th-document-document-not-indexed/257588
**Category:** Elasticsearch
**Created:** [December 3, 2020, 9:03pm UTC](https://discuss.elastic.co/t/elastic-problem-with-decimal-format-when-indexing-from-the-64th-document-document-not-indexed/257588 "2020-12-03T21:03:43Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![oldiequattro](https://avatars.discourse-cdn.com/v4/letter/o/e0b2c6/32.png) [@oldiequattro](https://discuss.elastic.co/u/oldiequattro)
#### Post date: [December 3, 2020, 9:03pm UTC](https://discuss.elastic.co/t/elastic-problem-with-decimal-format-when-indexing-from-the-64th-document-document-not-indexed/257588/1 "2020-12-03T21:03:43Z")

</div>

Hello,

I am showing you here a problem encountered in our environments with the indexing of a row in Elasticsearch which is not done as soon as the decimal value contained in the key exceeds 64 (side effect of a base 64 connector?).

Context: replication of data from a DB2 Z / os to a Kafka (confluence) and indexing in an Elasticsearch 7.6.2 via a connector (Kafka connect confluence).

Data: line containing a key composed of:

1 column CHAR format  
1 column decimal format  
1 column CHAR format  
Example:

PAUL 1 DUBOIS ADDRESS 1 BOULANGER  
PAUL 2 DUBOIS ADDRESS 2 BOUCHER  
PAUL 3 DUBOIS ADDRESS 2 PLOMBIER  
... / ...  
PAUL 65 DUBOIS ADDRESS 65 JOINER

Attempt to insert more than 64 rows with the same key except the decimal column.

Description of the problem: from the 64th line on no longer finds the record in Elasticsearch.  
The lines\> to 64 are however extracted (via the capture of modified data) from the DB2 Z / os database, well written in the Kafka topic (verified) but they are not found in Elasticsearch after indexing via Kafka connect.

The problem therefore occurs in the chain at indexing. The Kafka connector does not display any rejects or warnings.  
Elasticsearch isn't meaningful either.

Test done several times with different records but always with col1 and col3 of the same key and col2 incremented (1,2,3,4 etc ... up to more than 64).

Note:  
The functional key used in the connector definition is the one indicated above.  
But the internal ID generated by Elasticsearch still has a key technique.  
Is this the source of the problem?  
If so, how to get around it?

Other opinions?  
Thanks for your help.

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [December 4, 2020, 1:37am UTC](https://discuss.elastic.co/t/elastic-problem-with-decimal-format-when-indexing-from-the-64th-document-document-not-indexed/257588/2 "2020-12-04T01:37:56Z")

</div>

Can you post the error that you are getting?

---

<div class="post-metadata">

### Author: ![oldiequattro](https://avatars.discourse-cdn.com/v4/letter/o/e0b2c6/32.png) [@oldiequattro](https://discuss.elastic.co/u/oldiequattro)
#### Post date: [December 4, 2020, 10:14am UTC](https://discuss.elastic.co/t/elastic-problem-with-decimal-format-when-indexing-from-the-64th-document-document-not-indexed/257588/3 "2020-12-04T10:14:28Z")

</div>

Hello Warkolm,

The difficulty is that i don't have any error in the Kafka-connect log or in the Elasticsearch log.  
It's the problem.  
I have noticed that this behaviour occurs from the 64th rows with multiple tests.

---

<div class="post-metadata">

### Author: ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [December 4, 2020, 10:17am UTC](https://discuss.elastic.co/t/elastic-problem-with-decimal-format-when-indexing-from-the-64th-document-document-not-indexed/257588/4 "2020-12-04T10:17:17Z")

</div>

I can see that you also opened the question en français at [Elastic : Problème avec format décimal à l'indexation (document non indexé)](https://discuss.elastic.co/t/elastic-probleme-avec-format-decimal-a-lindexation-document-non-indexe/257587).

Where do you prefer the discussion to happen? I asked you for some details there. Should I ask here instead and close the other question?

---

<div class="post-metadata">

### Author: ![oldiequattro](https://avatars.discourse-cdn.com/v4/letter/o/e0b2c6/32.png) [@oldiequattro](https://discuss.elastic.co/u/oldiequattro)
#### Post date: [December 5, 2020, 1:40am UTC](https://discuss.elastic.co/t/elastic-problem-with-decimal-format-when-indexing-from-the-64th-document-document-not-indexed/257588/5 "2020-12-05T01:40:28Z")

</div>

yes thank you to delete the french one.

---

<div class="post-metadata">

### Author: ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [December 5, 2020, 4:43am UTC](https://discuss.elastic.co/t/elastic-problem-with-decimal-format-when-indexing-from-the-64th-document-document-not-indexed/257588/6 "2020-12-05T04:43:40Z")

</div>

We had a lot of discussion there so I think we should instead close this one and continue there.

---

<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: [January 2, 2021, 4:43am UTC](https://discuss.elastic.co/t/elastic-problem-with-decimal-format-when-indexing-from-the-64th-document-document-not-indexed/257588/7 "2021-01-02T04:43:43Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
