You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Lyra requires a schema to be defined up front, providing some friction to using it with SaaS clients who must define a schema themselves before uploading their data.
It would be great to have the schema be automatically generated based off the shape of objects that are added. E.g. the first object with the property "age" on it as a number would add "age" to the schema of type "number".
I'm not sure the optimizations that would have to be dropped or complexity to this feature which might make it impossible.
One idea I had for accomplishing this from the outside would be to set a schema like this:
then creating a property name lookup that could alter the fields of the objects on their way in and out such as:
constactualSchema={author: 'str1',quote: 'str2'};
Intercom describes running into issues with ElasticSearch schema maps growing unbounded and using a solution like this to allow all customer data to run side-by-side in the same index. I thought it might be a solution to implementing schemaless within Lyra.
The text was updated successfully, but these errors were encountered:
Lyra requires a schema to be defined up front, providing some friction to using it with SaaS clients who must define a schema themselves before uploading their data.
It would be great to have the schema be automatically generated based off the shape of objects that are added. E.g. the first object with the property "age" on it as a number would add "age" to the schema of type "number".
I'm not sure the optimizations that would have to be dropped or complexity to this feature which might make it impossible.
One idea I had for accomplishing this from the outside would be to set a schema like this:
then creating a property name lookup that could alter the fields of the objects on their way in and out such as:
Intercom describes running into issues with ElasticSearch schema maps growing unbounded and using a solution like this to allow all customer data to run side-by-side in the same index. I thought it might be a solution to implementing schemaless within Lyra.
The text was updated successfully, but these errors were encountered: