Table isn't suddenly accepting new data because of bug

CrateDB version

4.6.7

CrateDB setup information

I have a 3 node cluster with 3 gb memory and 2gb heap size setup.

Steps to Reproduce

I can’t reproduce it, I did made a new table with the query SHOW CREATE TABLE and made a new table and directly new data is showing up. So it looks like the old table got corrupt or something.

Expected Result

When I add new data to a staging cluster it is working, but on the identical production cluster it is not. I has been accepting data until 23:59 last night. After that it is giving me the following error:

[2022-02-01 06:36:51] [CRATE] Error inserting for vehicle v77!
[2022-02-01 06:36:51] { message: 'MapperParsingException[Failed to parse mapping: Mapping definition for [date_field] has unsupported parameters:  [fields : {keyword={ignore_above=256, type=keyword}}]]',
  code: 4000 }```

Actual Result

Even when not adding the specific field in the insert the table won’t accept the new data.

[rjbaat]

Maybe the table was indeed upgraded, but when I run your query I get:

version['created'] | version['upgraded']
-- | --
t1 | 4.6.7 | NULL

Anyway the table responded differently on a certain insert where the mentioned field was inserted in the new version 4.6.7 of crate. On the new table t2 with the analyser spec it was going good. Either way the table schema needed a change on our end, because the field was a timestamp and not a text field. So we changed the object from DYNAMIC to STRICT and set the field to a TIMESTAMP field and it looks good now. I think the object schema got auto extended where we didn’t want that to happen anyway.

Thnx for the quick responses!

[proddata]

It’s not totally clear how this could happen (if not done manually), as an OBJECT(DYNAMIC) should never map to a FULLTEXT indexed field, but rather map all text input as TEXT with a plain index.

Be aware that you can also predefine mappings for OBJECT(DYNAMIC) on table creation and add mappings by using ALTER TABLE ADD COLUMN

"raw_meta_data" OBJECT(DYNAMIC) AS (
    "date_field" TIMESTAMP,
    ...)

---

I will close this for now, as there is not enough information to reproduce this and classify it as bug.