[
https://issues.apache.org/jira/browse/ATLAS-5169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad P. Pawar updated ATLAS-5169:
-----------------------------------
Description:
Currently, during *Business Metadata create/edit* operations, the API request
always uses *SINGLE* cardinality for attributes, regardless of the UI
selection. This limits the ability to correctly define multi-valued attributes.
The UI should support configuring *cardinality* based on the *Enable multiple
values* option, allowing users to choose between {*}SINGLE{*}, {*}SET{*}, and
*LIST* where applicable.
h3. Expected Behavior
* When *Enable multiple values* is {*}unchecked{*}:
** Attribute cardinality should be set to:
{{cardinality: "SINGLE"}}
* When *Enable multiple values* is {*}checked{*}:
** Default cardinality should be:
{{cardinality: "SET"}}
** If the user toggles the option, cardinality should change to:
{{cardinality: "LIST"}}
h3. Impact
This change will ensure that the API request accurately reflects the user’s
selection in the UI and enables proper support for multi-valued Business
Metadata attributes.
was:
During Business Metadata create/edit operations, the API request always uses
*SINGLE* cardinality for attributes. The UI should allow selecting *LIST* or
*SET* for multi-valued attributes.
Default cardinality will be SET, *cardinality:* {*}"SET{*}", when used toggle
the option than *cardinality: "LIST"*
> Atlas UI creates multi-valued Business Metadata with SINGLE cardinality
> -----------------------------------------------------------------------
>
> Key: ATLAS-5169
> URL: https://issues.apache.org/jira/browse/ATLAS-5169
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Affects Versions: 3.0.0
> Reporter: Sheetal Shah
> Assignee: Prasad P. Pawar
> Priority: Major
>
> Currently, during *Business Metadata create/edit* operations, the API request
> always uses *SINGLE* cardinality for attributes, regardless of the UI
> selection. This limits the ability to correctly define multi-valued
> attributes.
> The UI should support configuring *cardinality* based on the *Enable multiple
> values* option, allowing users to choose between {*}SINGLE{*}, {*}SET{*}, and
> *LIST* where applicable.
> h3. Expected Behavior
> * When *Enable multiple values* is {*}unchecked{*}:
> ** Attribute cardinality should be set to:
> {{cardinality: "SINGLE"}}
> * When *Enable multiple values* is {*}checked{*}:
> ** Default cardinality should be:
> {{cardinality: "SET"}}
> ** If the user toggles the option, cardinality should change to:
> {{cardinality: "LIST"}}
> h3. Impact
> This change will ensure that the API request accurately reflects the user’s
> selection in the UI and enables proper support for multi-valued Business
> Metadata attributes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
