Jan Novotný
Jan Novotný
Currently, the schema cannot be properly modified during the catalog data lifecycle - only before the data is inserted. We need to handle situations where there is existing data in...
Currently, our `facetSummary' requirement works with references (and referenced entities), but it doesn't take into account the fact that the referenced entity may be part of a hierarchical structure. However,...
In certain situations we want to specify relations from the perspective of one entity, but allow them to be used (filtered / ordered by) from the other entity. Example situation:...
Fulltext is one of the key requirements for the e-commerce catalogs. But is also super-hard to implement. Currently our string based search is sub-optimal and doesn't use no specialized index....
Tip for performance optimization. Queries/query plans /formula tree parts with identical hashes should be calculated only once. The engine would keep an index of all currently processed schedules/formula tree parts...
Currently the durations recorded in query telemetry are represented as seconds in REST API and as nanoseconds in GraphQL API. It would be good to represent them both in a...
We have a backward compatibility problems with the team already working on Next.JS problem. I'd like to introduce some process that will warn us before switching to a new version...
We need to implement the vacuuming process, the backup & restore procedure. We want all of them to be executable while the system is running and writing to the original...
During manual testing of evitaDB we've run into scenarios where evitaDB returned inconsistent results. The problem disappeared when the cache was turned off, which means there is a problem in...
There are some rules for constructing query, that needs to be enforced - primarily to avoid confusion of the users. These rules should be validated and violations reported before processing...