CurtHagenlocher commented on issue #1704: URL: https://github.com/apache/arrow-adbc/issues/1704#issuecomment-2602406359
As someone who's very dependent on being able get metadata, it's really easy for me to list the shortcomings of `GetObjects`. It's a lot harder to think of a spec that's generally better in all respects. I like the idea in principle of an API that can reduce round-trips by merging different kinds of metadata in a single result, but in practice I think that the work required on the server to fetch and structure that data ends up being more expensive. And in modern systems aimed at data warehousing, the metadata is typically stored in a different type of system than the data and often doesn't seem to get the same kind of attention in terms of optimization. I've also had problems with xDBC-style `GetFoo` methods, but they're familiar (and therefore more accessible) to people already in the database client space. They also align better with Flight SQL. No matter what else we do, we could explicitly amend the spec as of vNext to say that new columns aren't a breaking change. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
