+dev list
Kai Lin, There are couple of reasons: technical metadata reported by Atlas hooks don’t include namespace attributes. While processing entity update notification by hooks, it is important to not lose existing namespace attributes on these entities. Atlas deployments might be using Atlas clients built before the namespace feature was introduced. Calls to update entities from these clients wouldn’t include namespace attributes. Hence it is important to retain namespace attributes on entities unless the client overrides with appropriate parameter. Hope this helps. Thanks, Madhan From: Kai Lin <lincoln0.981...@gmail.com> Date: Tuesday, March 14, 2023 at 3:31 AM To: <mad...@apache.org> Subject: Consultation on whether Apache Atlas replaceNamespace Attributes is enabled or not Dear Madhan, I would like to know why the replaceNamespaceAttributes parameter of the AtlasEntityStoreV2.createOrUpdate interface is false?Is there any consideration? https://github.com/apache/atlas/commit/d3a08b6eabcc50536c468db2d1328df54ee27fce Can i change the replaceNamespaceAttributes to true?Will there be any problem? Looking forward to your answer. Thank you very much.