jerryshao opened a new issue, #14363:
URL: https://github.com/apache/gravitino/issues/14363

   ### Describe the subtask
   
   Add backing tags to the domain manager in `core/`, following the Domain 
design (#13866) and the Domain API (#13877), on top of the domain manager 
(#13884):
   
   - Create a domain or sub-domain with an explicit backing tag (`TagValue 
backingTag, boolean createBackingTag`):
     - With `createBackingTag`, a new `NO_VALUE` tag is created in the same 
transaction as the domain and its parent edge. If the tag name exists, it fails 
with `TagAlreadyExistsException` and nothing is created.
     - Otherwise the existing tag is bound, with its optional value. A missing 
tag fails with `NoSuchTagException`, and the value must be allowed by the tag.
     - A null backing tag, or a value together with `createBackingTag`, fails 
with `IllegalArgumentException`.
   - `updateBackingTag` replaces the backing tag of a domain, or removes it 
with `null`. Setting the current one is a no-op.
   - No sharing: a tag has either one binding without a value, or bindings with 
values where each value backs at most one domain. A conflict fails with 
`BackingTagAlreadyBoundException`.
   - Locking as in the design: metalake (shared) → parent (shared) → tag 
(exclusive) on create, and domain (exclusive) → tag (exclusive) on update. The 
tag is re-checked after locking, and conflicts are checked under the tag lock.
   
   Authorization (owning the tag or the metalake, `CREATE_TAG`), the owner of a 
new tag, events and REST are covered by later subtasks.
   
   ### Parent issue
   
   #13864
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to