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
The memory connector is the fastest operating and easiest to use connector for catalogs. Unfortunately it currently does not support many SQL features of Trino and therefore can not be used for testing and other usage.
This issue aims to collect the tasks to expand the functionality of the connector. These features do not necessarily have to be suitable for productions usage or even usable for clusters with multiple workers in terms of data consistency. They can potentially just be suitable for testing or limited scenario usage. We just have to get started and can then expand in terms of robustness. Each update should include relevant doc change.
The memory connector is the fastest operating and easiest to use connector for catalogs. Unfortunately it currently does not support many SQL features of Trino and therefore can not be used for testing and other usage.
This issue aims to collect the tasks to expand the functionality of the connector. These features do not necessarily have to be suitable for productions usage or even usable for clusters with multiple workers in terms of data consistency. They can potentially just be suitable for testing or limited scenario usage. We just have to get started and can then expand in terms of robustness. Each update should include relevant doc change.
Docs for the memory connector are at https://trino.io/docs/current/connector/memory.html
Specifically SQL support - https://trino.io/docs/current/connector/memory.html#sql-support
Following are items to implement:
The text was updated successfully, but these errors were encountered: