GitHub user binarycat-dremio added a comment to the discussion: [DISCUSS] FlightSQL tracing: expected relationship between Open, statement/query spans, and connection-level correlation
Thanks for sharing your opinion. Given the current discussion and the OTel DB span conventions, I think it may make sense to introduce a dedicated span attribute for connection-level correlation, for example `adbc.connection.id`. The intent would not be to force all operations from a single connection into one trace, but to provide an explicit correlation key for users who want to group/query spans originating from the same logical connection. That seems consistent with the query-oriented tracing model: individual statements/operations remain separate spans/traces, while users who need stronger correlation can opt into it via span attributes rather than implicit parent-child linkage. If this direction sounds reasonable, I can open a follow-up issue proposing `adbc.connection.id` as an opaque, stable-for-the-lifetime-of-the-connection attribute. GitHub link: https://github.com/apache/arrow-adbc/discussions/4572#discussioncomment-17796062 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
