NihalJain opened a new pull request, #7016:
URL: https://github.com/apache/hbase/pull/7016

   We moved to opentelemetry latest packages with 
[HBASE-29349](https://issues.apache.org/jira/browse/HBASE-29349)  but 
deliberately chose to not jump to latest for semconv as it introduces few 
deprecations, which if removed can cause incompatibilities. With this task we 
want to see best approach to move to latest semconv and how to deal with these 
deprecations.
   
   
[SemanticAttributes.java](https://github.com/open-telemetry/semantic-conventions-java/blob/v1.29.0/semconv/src/main/java/io/opentelemetry/semconv/SemanticAttributes.java)
 has been removed and broken down into following with 
[semantic-conventions-java#v1.30.0-rc.1](https://github.com/open-telemetry/semantic-conventions-java/releases/tag/v1.30.0-rc.1)
   
   - 
[DbIncubatingAttributes.java](https://github.com/open-telemetry/semantic-conventions-java/blob/v1.32.0/semconv-incubating/src/main/java/io/opentelemetry/semconv/incubating/DbIncubatingAttributes.java)
   - 
[RpcIncubatingAttributes.java](https://github.com/open-telemetry/semantic-conventions-java/blob/v1.32.0/semconv-incubating/src/main/java/io/opentelemetry/semconv/incubating/RpcIncubatingAttributes.java)
   - 
[NetIncubatingAttributes.java](https://github.com/open-telemetry/semantic-conventions-java/blob/v1.32.0/semconv-incubating/src/main/java/io/opentelemetry/semconv/incubating/NetIncubatingAttributes.java)
   - 
[ExceptionAttributes.java](https://github.com/open-telemetry/semantic-conventions-java/blob/v1.32.0/semconv/src/main/java/io/opentelemetry/semconv/ExceptionAttributes.java)
   
   Docs:
   
   https://github.com/open-telemetry/semantic-conventions/tree/main/docs
   
https://github.com/open-telemetry/semantic-conventions/tree/main/docs/non-normative
   
   For example refer 
[db-migration.md](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/non-normative/db-migration.md)
   - db.system has been deprecated and renamed to db.system.name
   - db.operation has been deprecated and renamed to db.operation.name
   
   But with first draft of this change we continue to use the deprecated names. 
   
   If we decide on following the migration guide we can remove and handle the 
change as suggested in the guide or simply change them and break the 
compatibility.


-- 
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-unsubscr...@hbase.apache.org

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

Reply via email to