You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by GitBox <gi...@apache.org> on 2021/04/16 02:21:37 UTC
[GitHub] [dolphinscheduler] github-actions[bot] commented on issue #5288: [Improvement][ApiServer] Better Entity Restains when Creating
github-actions[bot] commented on issue #5288:
URL: https://github.com/apache/dolphinscheduler/issues/5288#issuecomment-820861806
**Describe the question**
Insufficient data context constraints
-Create tenant: Need to associate the queue, but did not verify the entered queueId
-Update tenant: The upper layer does not reflect, but the bottom layer implies the associated query on the table where the queue is located
-Trigger scenario: create tenant-choose queue at will (success) --> update tenant (failure, prompt that the tenant does not exist)
As title,
-When creating a Tenant by API, queue/queueId can be anything input, no check here.
-While try to update this Tenant, TenantMapper.xml use _where t.queue_id = q.id_, different data restains resulted in _[no tenant found ]_
**What are the current deficiencies and the benefits of improvement**
Stricter and consistently API and behavior
**Which version of DolphinScheduler:**
-[1.3.5.rc]
**Describe alternatives you've considered**
Check when creating
--
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org