You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by GitBox <gi...@apache.org> on 2022/07/25 16:09:16 UTC

[GitHub] [arrow-adbc] GavinRay97 opened a new issue, #46: Question around fixed hierarchy for schema

GavinRay97 opened a new issue, #46:
URL: https://github.com/apache/arrow-adbc/issues/46

   I noticed that the ADBC metadata information assumes a fixed hierarchy:
   https://github.com/apache/arrow-adbc/blob/2485d7c3da217a7190f86128d769a7d0445755ab/java/core/src/main/java/org/apache/arrow/adbc/core/AdbcConnection.java#L58
   
   What would the advice be for datasources that don't fit this, like Snowflake/Trino/Dremio where the hierarchy might be:
   - `datasource.database.schema.table`
   - `postgres1.mydb.public.emps`


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@arrow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [arrow-adbc] lidavidm commented on issue #46: Question around fixed hierarchy for schema

Posted by GitBox <gi...@apache.org>.
lidavidm commented on issue #46:
URL: https://github.com/apache/arrow-adbc/issues/46#issuecomment-1194305728

   Hmm, real-world edge cases are always fun, thanks for poking around. (Admittedly we should've looked more closely at these.)
   
   We were debating whether to keep the hierarchy or split it into multiple views (akin to Flight SQL), so this might be an argument for splitting them. 
   
   Do you have a reference for the Snowflake/Trino behavior? I see examples like the following that document three levels of hierarchy, but not the fourth level: 
   
   https://trino.io/docs/current/connector/postgresql.html#querying-postgresql
   https://docs.snowflake.com/en/user-guide/databases.html


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [arrow-adbc] lidavidm commented on issue #46: Question around fixed hierarchy for schema

Posted by GitBox <gi...@apache.org>.
lidavidm commented on issue #46:
URL: https://github.com/apache/arrow-adbc/issues/46#issuecomment-1374139381

   A few people are plotting out an ADBC 1.1.0 API specification already. In #320 I put up a quick solution to this, based on what we talked about before (letting `db_schema` have a delimiter).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org