Computing document _id on the fly

[mieciu]

We're adding additional field to the index configuration (timestampField), which needs to be DateTime/DateTime64 at the ClickHouse end.
It's not required when you don't want to generate document IDs, but in case you do, that's the way to go.

indexes:
  logs:
    timestampField: "reqTimeSec"
    enabled: true
  siem:
    timestampField: "timestamp"
    enabled: true
  kibana_sample_data_ecommerce:
    timestampField: "@timestamp"
    enabled: true

[pivovarit]

Needed to double-check and they indeed called the function *Milli and not *Millis.

[jakozaur]

I have two worries:

1. Dashboard UI might rely on ids being unique for queries.
2. We might want to have some format that we internally could recognize. E.g. t[timestamp hex without 0x]h(irrelevant counter).

Though fine to merge as is.

[jakozaur]

We found one regression it introduce while traversing docs, Przemek is working to fix this.

We found one regression it introduce while traversing docs, Przemek is working to fix this.

[pivovarit]

What's the scenario?

[jakozaur]

What's the scenario?

Open the log view, click on one document and click the next arrow on the document. If ids clash, it does not work. It also highlights all documents instead of the current one.