GitHub user lidavidm added a comment to the discussion: [DISCUSS] FlightSQL tracing: expected relationship between Open, statement/query spans, and connection-level correlation
> * Should all query-related spans created from a single connection be grouped > under the `FlightSQLDatabase.Open` span/trace? It appears OpenTelemetry has only specified what to do for individual calls to the database. https://opentelemetry.io/docs/specs/semconv/db/database-spans/#database-client-span-duration > * Or should each statement / `execute(...)` operation start its own logical > trace? By the above spec, yes. I think we should align with the official spec wherever possible. > * If query operations are intentionally separate, is the preferred > correlation mechanism something like a stable `connection_id` attribute on > statement/cursor spans rather than parent-child trace linkage? It's not clear to me that this is expected of clients in the first place. GitHub link: https://github.com/apache/arrow-adbc/discussions/4572#discussioncomment-17776255 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
