You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

How should we handle String escaping for properties that are stored in the datalake?

In the current implementation we are not consistent and users are not warned when they enter an invalid string for a name.


  • Requirement InfluxDB:
    • "time" can not be a field key
    • "name" cannot be a field key
    • Only number (e.g. 1234) are not allowed
    • "key" cannot be a field key
  • We use "::" to seperate stream ids and runtime names
  • To store files, the file name is escaped: "/" → "_" &  "." → "_"
  • No labels