GitHub user zeroshade added a comment to the discussion: [DISCUSS] FlightSQL tracing: expected relationship between Open, statement/query spans, and connection-level correlation
> 1. Should all query-related spans created from a single connection be grouped > under the FlightSQLDatabase.Open span/trace? I don't know about grouping them all under the same span/trace, but if we don't group them under the same span/trace then we should at least connect with them with some sort of ID metadata. > 2. Or should each statement / execute(...) operation start its own logical > trace? I think it might make sense for everything under a given statement being one logical trace, most definitely. > 3. 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? My personal preference would be a stable connection_id attribute on the statement/cursor spans rather than parent-child trace linkage since it's common that a connection might be used for multiple queries/statements. GitHub link: https://github.com/apache/arrow-adbc/discussions/4572#discussioncomment-17756652 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
