[jira] [Assigned] (ATLAS-3682) Multivalued attributes are not listed under Business Metadata Attribute filter
[ https://issues.apache.org/jira/browse/ATLAS-3682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt reassigned ATLAS-3682: -- Assignee: Keval Bhatt > Multivalued attributes are not listed under Business Metadata Attribute filter > -- > > Key: ATLAS-3682 > URL: https://issues.apache.org/jira/browse/ATLAS-3682 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Affects Versions: 2.1.0, 3.0.0 >Reporter: Umesh Padashetty >Assignee: Keval Bhatt >Priority: Major > Attachments: Screenshot 2020-03-24 at 1.01.54 AM.png, Screenshot > 2020-03-24 at 1.02.28 AM.png > > > Added attributes of different types, noticed that the multi valued attributes > are bot being listed for an entity filter, even when the attribute is > applicable to that entity. Screenshots attached below. > As you can see, the attribute "Reviewed by" which is of type "array" > is not being listed under the Business Metadata Attribute drop down. > CC: [~kevalbhatt] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3156) UI:No loading animation while creating or deleting a Classification, Create Entity, View loading
[ https://issues.apache.org/jira/browse/ATLAS-3156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069260#comment-17069260 ] ASF subversion and git services commented on ATLAS-3156: Commit d32b78b75f4ba64050ce9e049eefd0e73e64336f in atlas's branch refs/heads/branch-2.0 from Keval Bhatt [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=d32b78b ] ATLAS-3156 : Assign term/category loader not disappearing (cherry picked from commit 22ca98b04cb8c66c60ca1f688029d2fe9682e7af) > UI:No loading animation while creating or deleting a Classification, Create > Entity, View loading > > > Key: ATLAS-3156 > URL: https://issues.apache.org/jira/browse/ATLAS-3156 > Project: Atlas > Issue Type: Improvement >Reporter: Rahul Kurup >Assignee: Keval Bhatt >Priority: Minor > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3156-1.patch, ATLAS-3156.patch > > > While creating a Classification, there is no loading animation or any > indication to the user that the creation process is underway. The user only > gets a notification that the creation process is complete. If for some reason > the creation process takes a long while, then this lack of indication might > confuse the user into thinking that nothing is happening on clicking the > 'Create' button. > > This same issue exists when trying to delete a classification. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3156) UI:No loading animation while creating or deleting a Classification, Create Entity, View loading
[ https://issues.apache.org/jira/browse/ATLAS-3156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069259#comment-17069259 ] ASF subversion and git services commented on ATLAS-3156: Commit 22ca98b04cb8c66c60ca1f688029d2fe9682e7af in atlas's branch refs/heads/master from Keval Bhatt [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=22ca98b ] ATLAS-3156 : Assign term/category loader not disappearing > UI:No loading animation while creating or deleting a Classification, Create > Entity, View loading > > > Key: ATLAS-3156 > URL: https://issues.apache.org/jira/browse/ATLAS-3156 > Project: Atlas > Issue Type: Improvement >Reporter: Rahul Kurup >Assignee: Keval Bhatt >Priority: Minor > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3156-1.patch, ATLAS-3156.patch > > > While creating a Classification, there is no loading animation or any > indication to the user that the creation process is underway. The user only > gets a notification that the creation process is complete. If for some reason > the creation process takes a long while, then this lack of indication might > confuse the user into thinking that nothing is happening on clicking the > 'Create' button. > > This same issue exists when trying to delete a classification. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3156) UI:No loading animation while creating or deleting a Classification, Create Entity, View loading
[ https://issues.apache.org/jira/browse/ATLAS-3156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3156: --- Attachment: ATLAS-3156-1.patch > UI:No loading animation while creating or deleting a Classification, Create > Entity, View loading > > > Key: ATLAS-3156 > URL: https://issues.apache.org/jira/browse/ATLAS-3156 > Project: Atlas > Issue Type: Improvement >Reporter: Rahul Kurup >Assignee: Keval Bhatt >Priority: Minor > Fix For: 2.1.0, 3.0.0 > > Attachments: ATLAS-3156-1.patch, ATLAS-3156.patch > > > While creating a Classification, there is no loading animation or any > indication to the user that the creation process is underway. The user only > gets a notification that the creation process is complete. If for some reason > the creation process takes a long while, then this lack of indication might > confuse the user into thinking that nothing is happening on clicking the > 'Create' button. > > This same issue exists when trying to delete a classification. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Review Request 72278: ATLAS-3700: Partial update to Atlas overwrite map entry with different keys
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/72278/ --- Review request for atlas, Ashutosh Mestry, Karthik Manamcheri, Sridhar K, and Sarath Subramanian. Bugs: atlas-3700 https://issues.apache.org/jira/browse/atlas-3700 Repository: atlas Description --- 1) The model definition is in "https://github.com/apache/atlas/blob/master/addons/models/4000-MachineLearning/4010-ml_model.json#L90"; 2) I created a request of type EntityCreateRequestV2. It contains an entity of type ml_model_build with an attribute "metadata", which is a map, and contains key-value entries for "engineImageTag" and "engineImageName". 3) Then I created a request of type EntityPartialUpdateRequestV2. It contains an entity of type ml_model_build with an attribute "metadata", which is a map, and contains key-value entry for "updated_at". 4) In the properties of the entity ml_model_build, the * attribute "*metadata" only contains key-value entry for "updated_at". Desired behavior: The attribute "metadata" should contains key-value entries for "engineImageTag", "engineImageName" and "updated_at". Current behavior: the attribute "metadata" only contains key-value entry for "updated_at". Diffs - intg/src/main/java/org/apache/atlas/model/instance/EntityMutationResponse.java 1434a24590c4f4172378f98d83ca8d9e9ec9c4d8 repository/src/main/java/org/apache/atlas/repository/store/graph/v2/EntityGraphMapper.java 75b016cca04801c4c1512c1527453fd59a11a6c4 repository/src/test/java/org/apache/atlas/repository/store/graph/v2/AtlasEntityStoreV2Test.java 225b72cbef20b2329b36f550da60c1bbe1f95efa Diff: https://reviews.apache.org/r/72278/diff/1/ Testing --- add new test case for map attribute for partial update Thanks, Na Li
[jira] [Created] (ATLAS-3700) Partial update to Atlas overwrite map entry with different keys
Na Li created ATLAS-3700: Summary: Partial update to Atlas overwrite map entry with different keys Key: ATLAS-3700 URL: https://issues.apache.org/jira/browse/ATLAS-3700 Project: Atlas Issue Type: Bug Components: atlas-core Affects Versions: 3.0.0 Reporter: Na Li Assignee: Na Li *Details:* 1) The model definition is in "https://github.com/apache/atlas/blob/master/addons/models/4000-MachineLearning/4010-ml_model.json#L90"; 2) I created a request of type EntityCreateRequestV2. It contains an entity of type ml_model_build with an attribute "metadata", which is a map, and contains key-value entries for "engineImageTag" and "engineImageName". 3) Then I created a request of type EntityPartialUpdateRequestV2. It contains an entity of type ml_model_build with an attribute "metadata", which is a map, and contains key-value entry for "updated_at". 4) In the properties of the entity ml_model_build, the * attribute "*metadata" only contains key-value entry for "updated_at". *Desired behavior:* The attribute "metadata" should contains key-value entries for "engineImageTag", "engineImageName" and "updated_at". Current behavior: the attribute "metadata" only contains key-value entry for "updated_at". -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3674) ZipFileMigrationImporter: Set Shell Entity Creation
[ https://issues.apache.org/jira/browse/ATLAS-3674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ashutosh Mestry updated ATLAS-3674: --- Attachment: ATLAS-3674-ZipFileMigrationImport-Part-2.patch > ZipFileMigrationImporter: Set Shell Entity Creation > --- > > Key: ATLAS-3674 > URL: https://issues.apache.org/jira/browse/ATLAS-3674 > Project: Atlas > Issue Type: Improvement > Components: atlas-core >Affects Versions: trunk >Reporter: Ashutosh Mestry >Assignee: Ashutosh Mestry >Priority: Major > Fix For: trunk > > Attachments: ATLAS-3674-ZipFileMigrationImport-Part-2.patch, > ATLAS-3674-ZipFileMigrationImporter-Set-Shell-Entity.patch > > > *Background* > Existing implementation if _ZipFileMigrationImporter_ does not enable shell > entity creation by default. It expects user to set it. Setting this globally > may impact entity creation via REST API. > *Solution* > The _EntityConsumer_ can set it as part of its entity creation process. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Apache Atlas 2.1 release
That would be great! A faster release cycle would be appreciated as well. When is the vote due? Thanks Bolke Sent from my iPhone > On 19 Feb 2020, at 02:10, Madhan Neethiraj wrote: > > Atlas community, > > > > Over past months the dev community has been busy in enhancing Apache Atlas > with new features, improvements and fixes. Here are few features/enhancements > since last major release, Apache Atlas 2.0: > > - added quick-search feature, to provide a simpler search experience with > type-ahead suggestions > > - introduced Namespaces feature, which allows grouping of attributes to > be applied to multiple entity-types > > - introduced labels on entity instances, and search for entities using > the label > > - enhancement to support entity instance specific custom attributes > > - enhanced search to find entities by more than one classification > > - introduced shell/incomplete entities to handle notifications > referencing entities that don’t (yet) exist in Atlas > > - added REST APIs to purge deleted entities > > - performance improvements in lineage retrieval and tag-propagation > > - updated Atlas server to process notifications from multiple Kafka topics > > - updated Hive hook to track process executions, via > hive_process_execution entities > > - updated Hive hook to capture DDL operations, via hive_db_ddl and > hive_table_ddl entities > > - added models for Spark; introduced new models for AWS S3 > > - updated versions of dependent libraries/components: JanusGraph, Jackson > parser, Spring Framework, > > - updated authorization model to cover new features/APIs, like add/remove > labels, purge entities, update namespace attributes > > > > With significant improvements in place, it is time for the next maintenance > release of Apache Atlas! > > > > I propose to release Apache Atlas 2.1 by early next month. Please review and > send your comments. > > > > Regards, > > Madhan >
[jira] [Updated] (ATLAS-3699) Update authorization for Update Entity for audits with user defined attributes
[ https://issues.apache.org/jira/browse/ATLAS-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nixon Rodrigues updated ATLAS-3699: --- Summary: Update authorization for Update Entity for audits with user defined attributes (was: Update authorization for Update Entity with user defined attributes) > Update authorization for Update Entity for audits with user defined attributes > -- > > Key: ATLAS-3699 > URL: https://issues.apache.org/jira/browse/ATLAS-3699 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: chaitali borole >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3699) Update authorization for Update Entity with user defined attributes
[ https://issues.apache.org/jira/browse/ATLAS-3699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chaitali borole reassigned ATLAS-3699: -- Assignee: chaitali borole > Update authorization for Update Entity with user defined attributes > --- > > Key: ATLAS-3699 > URL: https://issues.apache.org/jira/browse/ATLAS-3699 > Project: Atlas > Issue Type: Bug >Reporter: Nixon Rodrigues >Assignee: chaitali borole >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3699) Update authorization for Update Entity with user defined attributes
Nixon Rodrigues created ATLAS-3699: -- Summary: Update authorization for Update Entity with user defined attributes Key: ATLAS-3699 URL: https://issues.apache.org/jira/browse/ATLAS-3699 Project: Atlas Issue Type: Bug Reporter: Nixon Rodrigues -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3698) Update Response for Bulk import's in Atlas
[ https://issues.apache.org/jira/browse/ATLAS-3698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mayank Jain updated ATLAS-3698: --- Description: This Jira is regarding an improvement in providing response for Bulk imports in Atlas , the basic idea was to create the response more user friendly by providing appropriate and understandable response to the end user. E.g : If the user uploads a csv/excel file with 15 records out of which 10 records got updated and 5 didn't then we tend to maintain a separate list for both successful as well as Failed records. Also the Failed records would have the msgs addressing why the records didn't got uploaded i.e what exactly went wrong using which the user can make appropriate changes and do a re-upload. > Update Response for Bulk import's in Atlas > -- > > Key: ATLAS-3698 > URL: https://issues.apache.org/jira/browse/ATLAS-3698 > Project: Atlas > Issue Type: Improvement >Reporter: Mayank Jain >Priority: Major > > This Jira is regarding an improvement in providing response for Bulk imports > in Atlas , > the basic idea was to create the response more user friendly by providing > appropriate and understandable response to the end user. > E.g : If the user uploads a csv/excel file with 15 records out of which 10 > records got updated and 5 didn't then we tend to maintain a separate list for > both successful as well as Failed records. > Also the Failed records would have the msgs addressing why the records didn't > got uploaded i.e what exactly went wrong using which the user can make > appropriate changes and do a re-upload. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3697) [Business Metadata] Incorrect values populated in Entity details > Business Metatdata attribute values, after encountering an error previously
[ https://issues.apache.org/jira/browse/ATLAS-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17068509#comment-17068509 ] ASF subversion and git services commented on ATLAS-3697: Commit 1a0d7786078ade3c7be12c809f452518080e8e64 in atlas's branch refs/heads/branch-2.0 from Keval Bhatt [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=1a0d778 ] ATLAS-3697:- [Business Metadata] Incorrect values populated in Entity details > Business Metatdata attribute values, after encountering an error previously (cherry picked from commit d0147981ceb9a0afdef58ee53fea6c5d2379b0f3) > [Business Metadata] Incorrect values populated in Entity details > Business > Metatdata attribute values, after encountering an error previously > -- > > Key: ATLAS-3697 > URL: https://issues.apache.org/jira/browse/ATLAS-3697 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Umesh Padashetty >Assignee: Keval Bhatt >Priority: Critical > Attachments: ATLAS-3697.patch, Issue with editing attribute values > post error.mov > > > While adding/updating a Business Metadata attribute value in the entity > details page, suppose a user updates multiple values, and then click on save. > If say, there is an error in updating some value, the user cannot obviously > save it. So once you click on cancel, and click on edit again, instead of > populating the original values, we are populating the values which the user > tried to update while he encountered an error. > This could be problematic because let's say the user changes the mind and > wants to update only one value. Now he cannot do it, because the original > values are not populated. Also, the user might save wrong data unknowingly > while trying to fix a rogue field. > Attached video for the detailed explanation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3697) [Business Metadata] Incorrect values populated in Entity details > Business Metatdata attribute values, after encountering an error previously
[ https://issues.apache.org/jira/browse/ATLAS-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17068505#comment-17068505 ] ASF subversion and git services commented on ATLAS-3697: Commit d0147981ceb9a0afdef58ee53fea6c5d2379b0f3 in atlas's branch refs/heads/master from Keval Bhatt [ https://gitbox.apache.org/repos/asf?p=atlas.git;h=d014798 ] ATLAS-3697:- [Business Metadata] Incorrect values populated in Entity details > Business Metatdata attribute values, after encountering an error previously > [Business Metadata] Incorrect values populated in Entity details > Business > Metatdata attribute values, after encountering an error previously > -- > > Key: ATLAS-3697 > URL: https://issues.apache.org/jira/browse/ATLAS-3697 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Umesh Padashetty >Assignee: Keval Bhatt >Priority: Critical > Attachments: ATLAS-3697.patch, Issue with editing attribute values > post error.mov > > > While adding/updating a Business Metadata attribute value in the entity > details page, suppose a user updates multiple values, and then click on save. > If say, there is an error in updating some value, the user cannot obviously > save it. So once you click on cancel, and click on edit again, instead of > populating the original values, we are populating the values which the user > tried to update while he encountered an error. > This could be problematic because let's say the user changes the mind and > wants to update only one value. Now he cannot do it, because the original > values are not populated. Also, the user might save wrong data unknowingly > while trying to fix a rogue field. > Attached video for the detailed explanation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (ATLAS-3697) [Business Metadata] Incorrect values populated in Entity details > Business Metatdata attribute values, after encountering an error previously
[ https://issues.apache.org/jira/browse/ATLAS-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17068494#comment-17068494 ] Nixon Rodrigues commented on ATLAS-3697: +1 for the patch, thanks [~kevalbhatt] ! > [Business Metadata] Incorrect values populated in Entity details > Business > Metatdata attribute values, after encountering an error previously > -- > > Key: ATLAS-3697 > URL: https://issues.apache.org/jira/browse/ATLAS-3697 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Umesh Padashetty >Assignee: Keval Bhatt >Priority: Critical > Attachments: ATLAS-3697.patch, Issue with editing attribute values > post error.mov > > > While adding/updating a Business Metadata attribute value in the entity > details page, suppose a user updates multiple values, and then click on save. > If say, there is an error in updating some value, the user cannot obviously > save it. So once you click on cancel, and click on edit again, instead of > populating the original values, we are populating the values which the user > tried to update while he encountered an error. > This could be problematic because let's say the user changes the mind and > wants to update only one value. Now he cannot do it, because the original > values are not populated. Also, the user might save wrong data unknowingly > while trying to fix a rogue field. > Attached video for the detailed explanation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (ATLAS-3698) Update Response for Bulk import's in Atlas
Mayank Jain created ATLAS-3698: -- Summary: Update Response for Bulk import's in Atlas Key: ATLAS-3698 URL: https://issues.apache.org/jira/browse/ATLAS-3698 Project: Atlas Issue Type: Improvement Reporter: Mayank Jain -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3697) [Business Metadata] Incorrect values populated in Entity details > Business Metatdata attribute values, after encountering an error previously
[ https://issues.apache.org/jira/browse/ATLAS-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3697: --- Attachment: ATLAS-3697.patch > [Business Metadata] Incorrect values populated in Entity details > Business > Metatdata attribute values, after encountering an error previously > -- > > Key: ATLAS-3697 > URL: https://issues.apache.org/jira/browse/ATLAS-3697 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Umesh Padashetty >Assignee: Keval Bhatt >Priority: Critical > Attachments: ATLAS-3697.patch, Issue with editing attribute values > post error.mov > > > While adding/updating a Business Metadata attribute value in the entity > details page, suppose a user updates multiple values, and then click on save. > If say, there is an error in updating some value, the user cannot obviously > save it. So once you click on cancel, and click on edit again, instead of > populating the original values, we are populating the values which the user > tried to update while he encountered an error. > This could be problematic because let's say the user changes the mind and > wants to update only one value. Now he cannot do it, because the original > values are not populated. Also, the user might save wrong data unknowingly > while trying to fix a rogue field. > Attached video for the detailed explanation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[DISCUSS] How to speed up contributions?
Dear Atlas Dev Community, Myself and my team have been contributors to Apache Atlas. We have contributed in the area of authentication and kubernetes/docker improvements. We like to contribute in the context of performance and usability. Unfortunately, we also notice that it is hard to get attention to the contributions. Saying it out loud: the dev list is hardly alive with close to none discussion (e.g. see the Apache Atlas 2.1 release ‘thread’ of February), Jira items feel lost and abandoned, items on the review board take months to get integrated although they are “ship it” marked. There are some ‘fast-tracked’ items, but they seem to come from a selective group of people and feels not inclusive. This results in loss of interest/energy of potential contributors. What can be done to improve this situation? I think there are a couple of options that could help with improving this. I don’t want to stipulate any of them but want to put them up for consideration, like: 1. Add new committers. I have not seen the latest report to the ASF, but I am going to assume that assume that it has been a while that new committers have added to the project. 2. Allow and accept PRs on Github. The ASF has moved to GitHub and it does give the same if not better and more native workflow for contributors. 3. Consider moving to Github issues. GH Issues and JIRA are both not perfect, but Jira does tend to make discussions less visible. 4. Integrate with a CI like Travis or Azure pipelines. Visibility whether a particular PR passes tests increases confidence in the PR and speeds up contributions. ASF has a contract with Travis although Azure pipelines seem to gain more popularity. What do you think? Kind regards, Bolke Verstuurd vanaf mijn iPad
[jira] [Assigned] (ATLAS-3697) [Business Metadata] Incorrect values populated in Entity details > Business Metatdata attribute values, after encountering an error previously
[ https://issues.apache.org/jira/browse/ATLAS-3697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt reassigned ATLAS-3697: -- Assignee: Keval Bhatt > [Business Metadata] Incorrect values populated in Entity details > Business > Metatdata attribute values, after encountering an error previously > -- > > Key: ATLAS-3697 > URL: https://issues.apache.org/jira/browse/ATLAS-3697 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Umesh Padashetty >Assignee: Keval Bhatt >Priority: Critical > Attachments: Issue with editing attribute values post error.mov > > > While adding/updating a Business Metadata attribute value in the entity > details page, suppose a user updates multiple values, and then click on save. > If say, there is an error in updating some value, the user cannot obviously > save it. So once you click on cancel, and click on edit again, instead of > populating the original values, we are populating the values which the user > tried to update while he encountered an error. > This could be problematic because let's say the user changes the mind and > wants to update only one value. Now he cannot do it, because the original > values are not populated. Also, the user might save wrong data unknowingly > while trying to fix a rogue field. > Attached video for the detailed explanation. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (ATLAS-3691) [Business Metadata] Date field does not have year and month selector
[ https://issues.apache.org/jira/browse/ATLAS-3691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt updated ATLAS-3691: --- Fix Version/s: 3.0.0 2.1.0 > [Business Metadata] Date field does not have year and month selector > > > Key: ATLAS-3691 > URL: https://issues.apache.org/jira/browse/ATLAS-3691 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Umesh Padashetty >Assignee: Keval Bhatt >Priority: Minor > Fix For: 2.1.0, 3.0.0 > > > While assigining the business metadata attribute in the entity details page, > the date selector does not have an option to change the year. We can just > change the monthwise. > Imagine the case where I went to set the date to some distant date, either in > past (say Jan 20, 1989) or future (say Feb 26, 2036), the user will have to > click hundreds of times to reach this date. It is better to provide an year > selection option -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (ATLAS-3691) [Business Metadata] Date field does not have year and month selector
[ https://issues.apache.org/jira/browse/ATLAS-3691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Keval Bhatt reassigned ATLAS-3691: -- Assignee: Keval Bhatt > [Business Metadata] Date field does not have year and month selector > > > Key: ATLAS-3691 > URL: https://issues.apache.org/jira/browse/ATLAS-3691 > Project: Atlas > Issue Type: Bug > Components: atlas-webui >Reporter: Umesh Padashetty >Assignee: Keval Bhatt >Priority: Minor > > While assigining the business metadata attribute in the entity details page, > the date selector does not have an option to change the year. We can just > change the monthwise. > Imagine the case where I went to set the date to some distant date, either in > past (say Jan 20, 1989) or future (say Feb 26, 2036), the user will have to > click hundreds of times to reach this date. It is better to provide an year > selection option -- This message was sent by Atlassian Jira (v8.3.4#803005)
