Re: Contributor Request/ Request to contribute

[Sharmadha Sainath]

Hi All,

A Gentle Reminder. Kindly approve Abhishek Pal to contribute to Atlas.

Thanks,
Sharmadha S.

On Wed, Jun 29, 2022 at 8:54 AM Abhishek Pal
 wrote:

> Hi Atlas Team,
>
> I am interested in contributing to Apache Atlas project, kindly add me as a
> contributor.
>
>
> My Jira id is *devabhishekpal.*
>
> My account was created using the mail id: *pal.abhishek03012...@gmail.com
> *
>

Re: Contributor Request

[Sharmadha Sainath]

Hi All,

A gentle reminder. Kindly approve Kundan Kumar Jha to contribute to Atlas.

Thanks,
Sharmadha S.

On Tue, Aug 16, 2022 at 10:26 PM Kundan Kumar Jha 
wrote:

> Hi Atlas Team,
>
> I am interested in contributing to the Apache Atlas project, kindly add me
> as a contributor.
>
> My Jira details:
> Username: kundan.jha
> Email: kundan3...@gmail.com
>
> Thanks & regards,
> Kundan Kumar Jha
>

Re: [VOTE] Release Apache Atlas version 2.2.0 - rc1

[Sharmadha Sainath]

Hi ,

+1 for Apache Atlas v2.2.0 RC1

- Verified PGP Signature, SHA512 hash, MD5 hash
- Setup Atlas with embedded-hbase-solr
- Verified Basic/DSL/Quick Search
- Verified tag association/disassociation and propagation
- Verified Saved search
- Added Labels , User defined key value pairs , Business metadata to
entities
- Verified Entity audits
- Verified metrics response
- Verified Soft Deletion of entities
- Verified functionalities in BETA UI.

Thanks,
Sharmadha S.




On Wed, Aug 11, 2021 at 9:36 PM Radhika Kundam 
wrote:

> Hi Sid,
>
> +1 for Apache Atlas v2.2.0 rc1.
>
> Verified the following
>
>- Clean Build and setup Atlas with embedded-hbase-solr
>- Created entities, classifications on Atlas UI
>- Verified Entity Audit data
>- Verified entity search with REST API
>- Verified Basic Search and Advanced Search
>- Verified Metrics
>
>
> Thanks,
> Radhika
>
>
> On Wed, Aug 11, 2021 at 8:53 AM mayank jain <
> mayank.j...@freestoneinfotech.com> wrote:
>
> > Hi Sidharth
> >
> > +1 for Apache Atlas v2.2.0 rc1.
> >
> > Verified the following -
> >  *  Clean build embedded-hbase-solr profile.
> >  *  Bulk import of glossary amd Business metadata
> >  *  Tested the metrics of atlas
> >  *  Setup Atlas server in embedded HBase and Solr.
> >  *  Verified md5, sha512, Signature
> >  *  Verified Import zip with REST API
> >  *  Ran quick start
> >  *  Created entities, glossaries ,terms on Atlas UI
> >
> >
> > Regards,
> > Mayank Jain
> >
> > On Wed, Aug 11, 2021 at 6:21 PM Jayendra Parab  >
> > wrote:
> >
> > > Thanks Sidharth for putting this together for vote.
> > >
> > > +1 for 2.2.0 - rc1 release.
> > >
> > > Verified following:
> > >   * MD5, SHA512, release signature
> > >   * mvn build with embedded-hbase-solr
> > >   * Setup Atlas server with embedded HBase and Solr.
> > >   * Ran quick_start.py
> > >   * Atlas UI loading cleanly.
> > >   * Created entities using Atlas UI
> > >   * Validated basic and DSL search
> > >
> > >
> > > On Wed, Aug 11, 2021 at 1:14 PM Mandar Ambawane <
> > > mandar.ambaw...@freestoneinfotech.com> wrote:
> > >
> > > > Hi Sidharth,
> > > >
> > > > +1 for Apache Atlas 2.2.0 rc1
> > > >
> > > > Verified following:
> > > >
> > > >- md5, sha512 signatures
> > > >- mvn build with embedded-hbase-solr -DskipTests
> > > >- Started Atlas server and did run quick start
> > > >- Atlas UI loading cleanly
> > > >- Created entities using Atlas UI
> > > >- Validated basic search
> > > >- Validated Admin audits
> > > >
> > > > Thanks,
> > > > Mandar
> > > >
> > > > On Wed, Aug 11, 2021 at 12:06 PM Chaitali Borole <
> > > > chaitali.bor...@freestoneinfotech.com> wrote:
> > > >
> > > > > Hello Sidharth,
> > > > >
> > > > > +1 for Apache Atlas 2.2.0 rc1
> > > > >
> > > > > Checked for below points:
> > > > >   *  md5, sha512 signatures.
> > > > >   *  Clean build with mvn clean package -Pdist,embedded-hbase-solr
> > > > > -DskipTests -Drat.skip.
> > > > >   *  Atlas server up and running.
> > > > >   *  Re-indexing with JAVA_PATCH.
> > > > >   *  Sanity checks :
> > > > > quick_search,entities,relationship,tags,glossaries,metrics api.
> > > > >   *  Quick start is successful.
> > > > >
> > > > > Thanks,
> > > > > Chaitali.
> > > > >
> > > > > On Tue, Aug 10, 2021 at 4:25 AM Sidharth Mishra <
> > sidmis...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > Atlas team,
> > > > > >
> > > > > > Apache Atlas 2.2.0 rc1, with the following fixes since rc0, is
> now
> > > > > > available for vote within the dev community.
> > > > > >
> > > > > > ATLAS-4390 - Changed Atlas branch to release-2.2.0-rc1
> > > > > > ATLAS-4391 - NoSuchFileException for
> > > > > {atlas.log.dir}/atlas-metrics.out
> > > > > > ATLAS-4343 - [Entity Audits] 'Propagated Classification
> Added'
> > > > > > Timestamp is < 'Entity
> > > > > > Created' Timestamp
> > > > > > ATLAS-4387 - UI: Propagated Classifications shows wrong count
> > for
> > > > > > entity type on Entity
> > >  detail
> > > > > > page
> > > > > > ATLAS-4386 - Relationship search: Sorting does not work when
> > > > > > relationship label is passed
> > > > > >
> > > > > > Links to the release artifacts are given below. Please review and
> > > vote.
> > > > > >
> > > > > > The vote will be open for at least 72 hours or until necessary
> > votes
> > > > > > are reached.
> > > > > >
> > > > > >   [ ] +1 Approve
> > > > > >
> > > > > >   [ ] +0 No opinion
> > > > > >
> > > > > >   [ ] -1 Disapprove (and reason why)
> > > > > >
> > > > > > Thanks,
> > > > > > Sid
> > > > > >
> > > > > > List of all issues addressed in this release:
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%3DATLAS%20AND%20status%3DResolved%20AND%20fixVersion%3D2.2.0%20ORDER%20BY%20key%20DESC
> > > > > >
> > > > > > Git tag for the release:
> > > > > > https://github.com/apache/atlas/tree/release-2.2.0-rc1
> > > > > >
> > > > > > Sources for the release:
> > > > > >
> > > > > 

Re: [VOTE] Release Apache Atlas version 2.1.0 - rc3

[Sharmadha Sainath]

+1 for Apache Atlas 2.1.0-rc3 release.

   - Validated MD5 and SHA512 checksum of source.
   - Verified PGP Signature
   - Brought up Atlas using embedded HBase and Solr.
   - Verified DSL , Basic Search , Quick search and Suggestions
   - Validated CRUD on labels, custom attributes , business metadata
   - Verified Basic search using system attributes filters (multiple
   classifications , labels , custom attributes , business metadata search)
   - Added labels , user defined properties (custom attributes) , business
   metadata to entities and verified the entity properties and audits.
   - Purged Soft Deleted entity  and verified the audits of purged entity.
   Deleted tag associated to the purged entity and verified there are no
   references.
   - Saved the Favorite searches and executed them.
   - Tested Atlas UI against XSS strings

Thanks,
Sharmadha Sainath

On Mon, Jul 13, 2020 at 7:15 PM Nixon Rodrigues <
nixon.rodrig...@freestoneinfotech.com> wrote:

> +1 for Atlas 2.1.0 rc3 release.
>
> Verified signature and MD5/SHA keys.
> Verified release tag on git repo.
> Verified build with rc3 bits.
> Verified UI with Quick Start data.
>
> Thanks  & Regards
> Nixon
>
>
>
> On Mon, Jul 13, 2020 at 12:44 PM Mandar Ambawane <
> mandar.ambaw...@freestoneinfotech.com> wrote:
>
> > +1 for Apache Atlas 2.1.0 RC3 release
> >
> > Validated the following:
> > 1. Verified the source SHA512 and MD5 checksum
> > 2. Verified the build with -Pdist,embedded-hbase-solr
> > 3. Started Atlas server successfully
> > 4. Verified quick_start.py, all entities and tag get created successfully
> > 5. Created Business metadata and associated with an entity.
> > 6. Checked Basic and advanced search
> >
> > Thanks,
> > Mandar
> >
> > On Mon, Jul 13, 2020 at 12:39 PM Jayendra Parab <
> jayendra.pa...@gmail.com>
> > wrote:
> >
> > > +1 for Apache Atlas 2.1.0 RC3 release
> > >
> > > Validated the following:
> > > 1. Verified the source SHA512 and MD5 checksum
> > > 2. Verified the build with -Pdist,embedded-hbase-solr
> > > 3. Started Atlas server successfully
> > > 4. Verified quick_start.py, all entities and tag get created
> successfully
> > > 5. Created entities, applied tags from UI
> > > 6. Checked Basic and advanced search
> > >
> > > Regards,
> > > Jayendra.
> > >
> > > On Mon, Jul 13, 2020 at 12:17 PM Sarath Subramanian  >
> > > wrote:
> > >
> > > > +1 for Apache Atlas 2.1 rc3
> > > >
> > > > Validated the following:
> > > > - Validated MD5 checksum
> > > > - Validated sha512 hash
> > > > - Verified PGP signature
> > > > - No binaries in extracted source
> > > > - Built successfully using embedded-hbase and solr profile
> > > > - Ran quick start and tested basic sanity - saved search,
> > basic/advanced
> > > > search, Glossary, tag propagation, Admin purge, system attribute
> search
> > > >
> > > >
> > > >
> > > > On Thu, Jul 9, 2020 at 9:59 PM Madhan Neethiraj 
> > > wrote:
> > > >
> > > > > Atlas team,
> > > > >
> > > > > Apache Atlas 2.1.0 rc3, with following fixes since rc2, is now
> > > available
> > > > > for vote within dev community.
> > > > >   ATLAS-3877: Purged entity audit throws 404 Entity not found error
> > > > >   ATLAS-3882: Classic UI: Loader not disappearing while assigning
> > > > category
> > > > > to term
> > > > >
> > > > > Links to the release artifacts are given below. Please review and
> > vote.
> > > > >
> > > > > The vote will be open for at least 72 hours or until necessary
> votes
> > > are
> > > > > reached.
> > > > >   [ ] +1 Approve
> > > > >   [ ] +0 No opinion
> > > > >   [ ] -1 Disapprove (and reason why)
> > > > >
> > > > > Thanks,
> > > > > Madhan
> > > > >
> > > > >
> > > > > List of all issues addressed in this release:
> > > > > https://issues.apache.org/jira/issues/?jql=project=ATLAS AND
> > > > > status=Resolved AND fixVersion=2.1.0 ORDER BY key DESC
> > > > >
> > > > > Git tag for the release:
> > > > > https://github.com/apache/atlas/tree/release-2.1.0-rc3
> > > > > Sources for the release:
> > > > >
> >

Re: [VOTE] Release Apache Atlas version 2.1.0 - rc2

[Sharmadha Sainath]

+1 for Apache Atlas 2.1.0 rc2 release

   - Validated MD5 and SHA512 checksum of source.
   - Verified PGP Signature
   - Brought up Atlas using embedded HBase and Solr.
   - Verified DSL , Basic Search , Quick search and Suggestions
   - Validated CRUD on labels, custom attributes , business metadata
   - Verified Basic search using system attributes filters (multiple
   classifications , labels , custom attributes , business metadata search)
   - Added labels , user defined properties (custom attributes) , business
   metadata to entities and verified the entity properties and audits.
   - Purged Soft Deleted entity.
   - Saved the Favorite searches and executed them.
   - Tested Atlas UI against XSS strings

Thanks,
Sharmadha Sainath

On Tue, Jul 7, 2020 at 5:58 PM mayank jain <
mayank.j...@freestoneinfotech.com> wrote:

> +1  for Apache Atlas 2.1.0 RC2 release
>
> I have verified the following scenarios:
> - The build with -Pdist,embedded-hbase-solr was successfully.
> - Verified the source SHA512 and MD5 checksum
> - Atlas server is starting properly
> - Verified quick_start.py, all entities and tags are getting created
> successfully.
> - Verified basic and advanced search flow.
> - Tried creating various entities and also applied classifications on them
> from UI and it worked fine.
>
>
> Regards,
> Mayank Jain
>
> On Tue, Jul 7, 2020 at 3:56 PM Keval Bhatt  wrote:
>
> > Thanks, Madhan for putting Apache Atlas 2.1.0 release candidate #2 for
> the
> > vote.
> >
> > +1 (binding) for Apache Atlas 2.1.0 RC2
> >
> > Validated the following:
> >
> >
> >- Verified the md5/sha checksum of the source bundle
> >- Verified the build with -Pdist,embedded-hbase-solr
> >- Created classification, updated the attributes and associated with
> the
> >entity and term
> >- Tested basic search with the type, classification, term and their
> >attribute filters
> >- Tested advance search
> >- Saved the search for later use.
> >- Created Business metadata and associated with an entity.
> >- Create Labels and user-define properties
> >- Tested Lineage and applied filter hide/show deleted entities and
> >process
> >- Checked the relationship diagram
> >- Entity create/update test from UI
> >- Checked the statistics page.
> >
> >
> > Thanks,
> > Keval Bhatt
> >
> >
> > On Tue, Jul 7, 2020 at 3:38 PM Nixon Rodrigues <
> > nixon.rodrig...@freestoneinfotech.com> wrote:
> >
> > > Thanks Madhan for putting 2.1 RC2 together for the vote.
> > >
> > > +1 (binding) for Apache Atlas 2.1 RC2
> > >
> > > Validated the following items.
> > >
> > >1. verified the md5/sha checksum of source bundle.
> > >2. Validated Signature for release source
> > >3. packaging with -Pdist,embedded-hbase-solr is good.
> > >4. Unit testcase passes.
> > >5. Run quickstart and all the types and entities created are loading
> > >correctly on the UI.
> > >6. Create tags, glossary, term and its apply correctly on entities.
> > >7. Created business metadata with attributes and applied it to
> > entities.
> > >8. tested basic and quick search flow.
> > >9. Verified statistics page details
> > >
> > > Thanks & Regards
> > > Nixon
> > >
> > > On Tue, Jul 7, 2020 at 2:13 PM Mandar Ambawane <
> > > mandar.ambaw...@freestoneinfotech.com> wrote:
> > >
> > > > +1 for Apache Atlas 2.1.0 RC2 release
> > > >
> > > > Validated the following:
> > > > 1. Verified the source SHA512 and MD5 checksum
> > > > 2. Verified the build with -Pdist,embedded-hbase-solr
> > > > 3. Started Atlas server successfully
> > > > 4. Verified quick_start.py, all entities and tag get created
> > successfully
> > > > 5. Created Business metadata and associated with an entity.
> > > > 6. Checked Basic and advanced search
> > > >
> > > > Thanks,
> > > > Mandar
> > > >
> > > > On Tue, Jul 7, 2020 at 12:37 PM vishal suvagia
> > > >  wrote:
> > > >
> > > > >  Thank-you Madhan for putting Apache Atlas 2.1.0 release candidate
> > > #2.+1
> > > > > for Apache Atlas 2.1.0 RC#2.Verified clean compilation and
> > > > > rat-checks.Validated the source checksums and hash.
> > > > >
> > > > > RegardsVishal Suvagia.
> > > > >
> >

Re: [VOTE] Release Apache Atlas version 2.1.0 - rc1

[Sharmadha Sainath]

+1 for Apache Atlas 2.1 RC1


   - Validated MD5 and SHA512 checksum of source.
   - Brought up Atlas using embedded HBase and Solr.
   - Verified DSL , Basic Search , Quick search and Suggestions
   - Verified Basic search using system attributes filters (multiple
   classification search , labels , custom attributes , business metadata
   search)
   - Added labels , user defined properties (custom attributes) , business
   metadata to entities and verified the entity properties and audits.
   - Purged Soft Deleted entity and verified purge audits.
   - Saved the Favorite searches and executed them.

Thanks,
Sharmadha S.



On Mon, Jun 8, 2020 at 6:23 PM Nixon Rodrigues <
nixon.rodrig...@freestoneinfotech.com> wrote:

> Thanks Madhan for putting 2.1 RC1 together for the vote.
>
> +1 for Apache Atlas 2.1 RC1
>
> Validated the following items.
>
>1. verified the md5/sha checksum of source bundle.
>2. packaging with -Pdist,embedded-hbase-solr is good.
>3. Unit testcase passes.
>4. Run quickstart and all the types and entities created are loading
>correctly on the UI.
>5. Create tags, glossary, term and its apply correctly on entities.
>6. Created business metadata with attributes and applied it to entities.
>7. tested basic and quick search flow.
>8. Verified statistics page details
>
>
> Thanks & Regards
> Nixon
>
>
>
> On Mon, Jun 8, 2020 at 11:17 AM Sarath Subramanian 
> wrote:
>
> > +1 for Apache Atlas 2.1 RC1
> >
> > Validated the following:
> >
> >- No binaries in source
> >- Verified source checksum - md5 and sha512
> >- Verified signature
> >- Build was successful on the source (mvn clean -DskipTests package
> >-Pdist,embedded-hbase-solr)
> >- Ran quickStart and validated types and entities were created
> >successfully.
> >- Validated tag propagation works
> >- Added/removed labels to an entity and verified audit is getting
> >updated correctly
> >- Added user-defined properties and business metadata attributes.
> >- Deleted few entities and purged those entities - validated if purge
> >audit recorded correctly.
> >- Basic sanity tests - basic search (with system attributes), advanced
> >search, quick search.
> >
> >
> >
> > Thanks,
> > Sarath
> >
> >
> >
> > On Sat, Jun 6, 2020 at 10:22 AM Madhan Neethiraj 
> > wrote:
> >
> > > (resending with plain-text format)
> > >
> > > Atlas team,
> > >
> > > Apache Atlas 2.1.0 rc1, with following fixes since rc0, is now
> available
> > > for vote within dev community.
> > >
> > > ATLAS-3770: UI(Classic): Active and Deleted hyperlinks for certain
> > > entities throwing error on click
> > > ATLAS-3766: Stats modal not close issue #2
> > > ATLAS-3674: ZipFileMigationImporter: Migration status display fix.
> > > Part 2
> > >
> > > Links to the release artifacts are given below. Please review and vote.
> > >
> > > The vote will be open for at least 72 hours or until necessary votes
> are
> > > reached.
> > >   [ ] +1 Approve
> > >   [ ] +0 No opinion
> > >   [ ] -1 Disapprove (and reason why)
> > >
> > > Thanks,
> > > Madhan
> > >
> > >
> > > List of all issues addressed in this release:
> > > https://issues.apache.org/jira/issues/?jql=project=ATLAS AND
> > > status=Resolved AND fixVersion=2.1.0 ORDER BY key DESC
> > >
> > > Git tag for the release:
> > > https://github.com/apache/atlas/tree/release-2.1.0-rc1
> > > Sources for the release:
> > >
> >
> https://dist.apache.org/repos/dist/dev/atlas/2.1.0-rc1/apache-atlas-2.1.0-sources.tar.gz
> > >
> > > Source release verification:
> > >   PGP Signature:
> > >
> >
> https://dist.apache.org/repos/dist/dev/atlas/2.1.0-rc1/apache-atlas-2.1.0-sources.tar.gz.asc
> > >   SHA512 Hash:
> > >
> >
> https://dist.apache.org/repos/dist/dev/atlas/2.1.0-rc1/apache-atlas-2.1.0-sources.tar.gz.sha512
> > >   MD5 Hash:
> > >
> >
> https://dist.apache.org/repos/dist/dev/atlas/2.1.0-rc1/apache-atlas-2.1.0-sources.tar.gz.md5
> > >
> > > Keys to verify the signature of the release artifacts are available at:
> > > https://dist.apache.org/repos/dist/release/atlas/KEYS
> > >
> > > New features/enhancements:
> > >   - Quick Search: provides a simpler search experience with type-ahead
> > > suggestions
> > >   - Business Metadata: enables augmenting entity-types with additional
> > > attributes, search entities using these attributes
> > >   - Labels: ability to add/remove labels on entities, and search
> entities
> > > using labels
> > >   - Custom Attributes: ability to add entity instance specific custom
> > > attributes i.e. attributes not defined in entity-def or business
> metadata
> > >   - Entity Purge: added REST APIs to purge deleted entities
> > >
> > > Enhancements:
> > >   - Search: ability to find entities by more than one classification
> > >   - Performance: improvements in lineage retrieval and
> > > classification-propagation
> > >   - Notification: ability to process notifications from multiple Kafka
> > > topics
> > 

Re: Apache Atlas: Delete/clean soft deleted entities after enabling hard delete

[Sharmadha Sainath]

Hi Ravindran,

Purging soft deleted entities feature is in 2.1.0 . More details on the
JIRA (https://issues.apache.org/jira/browse/ATLAS-3477).


Usage :
API : DELETE /api/atlas/admin/purge

body : [ "guid_1", "guid_2" ]


Thanks,
Sharmadha S.

On Fri, Feb 14, 2020 at 1:33 AM Sivalingam, Ravindran <
ravindran.sivalin...@epsilon.com> wrote:

> Hi,
>
> We used to have soft delete and recently enabled hard delete in atlas 1.1.
> Now we are trying to clean up the soft deleted entities via delete by guid
> api and not able to clear those.
>
> Is there a way to delete/clean soft deleted entities after enabling hard
> delete?
>
> Even I tried updating the entities with active status to make it active,
> but the status is still "DELETED".
>
> Apache Atlas Version: 1.1
>
> API: DELETE /v2/entity/guid/{guid}
> Thanks
> Ravi
>
>

[jira] [Created] (ATLAS-3350) Add better logging in AtlasAuthenticationFilter

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-3350:


 Summary: Add better logging in AtlasAuthenticationFilter
 Key: ATLAS-3350
 URL: https://issues.apache.org/jira/browse/ATLAS-3350
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Sharmadha Sainath


Need better/more logging for AtlasAuthenticationFilter. 

Certain scenario for which Atlas throws 500 server error , Atlas debug logs say 
triggering authentication but no other logs follow that:

{code}
2019-07-26 07:08:51,327 DEBUG - [pool-2-thread-1:] ~ Request 
[http://host:21000/api/atlas/admin/server/aasha$mycluster0] triggering 
authentication (AtlasAuthenticationFilter:410)
2019-07-26 07:08:51,471 DEBUG - [pool-2-thread-3:] ~ Cleaning stale 
transactions (StaleTransactionCleanupFilter:53)
2019-07-26 07:08:51,472 DEBUG - [pool-2-thread-3:] ~ Request 
[http://host:21000/api/atlas/admin/server/aasha$mycluster0] triggering 
authentication (AtlasAuthenticationFilter:410)
2019-07-26 07:08:52,781 DEBUG - [main-SendThread(master0.cloudera.site:2181):] 
~ Got ping response for sessionid: 0x16c1852da6bfe40 after 0ms 
(ClientCnxn$SendThread:742)
2019-07-26 07:08:52,907 DEBUG - [Connection evictor:] ~ Closing expired 
connections (PoolingHttpClientConnectionManager:414)
{code}


CC : [~nixonrodrigues]





--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

[jira] [Created] (ATLAS-3310) Relationships : After updating a bigint attribute , any operation on relationship instance,entity throws 500 internal server exception.

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-3310:


 Summary: Relationships : After updating a bigint attribute , any 
operation on relationship instance,entity throws 500 internal server exception.
 Key: ATLAS-3310
 URL: https://issues.apache.org/jira/browse/ATLAS-3310
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Sharmadha Sainath


After updating bigint attribute , any operation (example : GET) on the 
relationship fails throwing 500 internal server exception with the following 
stack trace.

Stack trace :
{code:java}

2019-05-20 06:19:28,592 ERROR - [pool-2-thread-3 - 
74ed4949-00ff-4f6d-87cb-e287684b55b8:] ~ Error handling a request: 
aceb2d520cb74b37 (ExceptionMapperUtil:32)
java.lang.ArrayIndexOutOfBoundsException: Required size [1] exceeds actual 
remaining size [0]
at 
org.janusgraph.diskstorage.util.StaticArrayBuffer.require(StaticArrayBuffer.java:94)
at 
org.janusgraph.diskstorage.util.StaticArrayBuffer.getByte(StaticArrayBuffer.java:170)
at 
org.janusgraph.diskstorage.util.StaticArrayBuffer.getBytes(StaticArrayBuffer.java:253)
at 
org.janusgraph.diskstorage.util.ReadArrayBuffer.getBytes(ReadArrayBuffer.java:120)
at 
org.janusgraph.graphdb.database.serialize.attribute.ByteArraySerializer.read(ByteArraySerializer.java:46)
at 
org.apache.atlas.repository.graphdb.janus.serializer.BigIntegerSerializer.read(BigIntegerSerializer.java:36)
at 
org.apache.atlas.repository.graphdb.janus.serializer.BigIntegerSerializer.read(BigIntegerSerializer.java:30)
at 
org.janusgraph.graphdb.database.serialize.StandardSerializer.readObjectNotNullInternal(StandardSerializer.java:265)
at 
org.janusgraph.graphdb.database.serialize.StandardSerializer.readObjectInternal(StandardSerializer.java:255)
at 
org.janusgraph.graphdb.database.serialize.StandardSerializer.readObject(StandardSerializer.java:235)
at 
org.janusgraph.graphdb.database.EdgeSerializer.readPropertyValue(EdgeSerializer.java:205)
at 
org.janusgraph.graphdb.database.EdgeSerializer.readInline(EdgeSerializer.java:191)
at 
org.janusgraph.graphdb.database.EdgeSerializer.parseRelation(EdgeSerializer.java:162)
at 
org.janusgraph.graphdb.database.EdgeSerializer.readRelation(EdgeSerializer.java:73)
at 
org.janusgraph.graphdb.transaction.RelationConstructor.readRelationCache(RelationConstructor.java:41)
at 
org.janusgraph.graphdb.relations.CacheEdge.getPropertyMap(CacheEdge.java:101)
at 
org.janusgraph.graphdb.relations.CacheEdge.getValueDirect(CacheEdge.java:108)
at 
org.janusgraph.graphdb.relations.AbstractTypedRelation.lambda$properties$1(AbstractTypedRelation.java:166)
at 
java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:174)
at 
java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
at 
java.util.Spliterators$ArraySpliterator.tryAdvance(Spliterators.java:958)
at 
java.util.stream.StreamSpliterators$WrappingSpliterator.lambda$initPartialTraversalState$0(StreamSpliterators.java:294)
at 
java.util.stream.StreamSpliterators$AbstractWrappingSpliterator.fillBuffer(StreamSpliterators.java:206)
at 
java.util.stream.StreamSpliterators$AbstractWrappingSpliterator.doAdvance(StreamSpliterators.java:161)
at 
java.util.stream.StreamSpliterators$WrappingSpliterator.tryAdvance(StreamSpliterators.java:300)
at java.util.Spliterators$1Adapter.hasNext(Spliterators.java:681)
at 
org.apache.tinkerpop.gremlin.structure.Element.property(Element.java:79)
at 
org.apache.atlas.repository.graphdb.janus.AtlasJanusElement.getProperty(AtlasJanusElement.java:65)
at 
org.apache.atlas.repository.store.graph.v2.AtlasGraphUtilsV2.getTypeName(AtlasGraphUtilsV2.java:126)
at 
org.apache.atlas.repository.store.graph.v2.AtlasRelationshipStoreV2.update(AtlasRelationshipStoreV2.java:148)
at 
org.apache.atlas.repository.store.graph.v2.AtlasRelationshipStoreV2$$FastClassBySpringCGLIB$$a8165974.invoke()
at 
org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
at 
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:736)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
at 
org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:80)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at 
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:671)
at 
org.apache.atlas.repository.store.graph.v2.AtlasRelationshipStoreV2$$EnhancerBySpringCGLIB$$a12f9384.update

[jira] [Comment Edited] (ATLAS-3177) Regression , Export : changeMarker is not set right - set to older value compared to entity's lastModifedTime

[Sharmadha Sainath (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16850538#comment-16850538
 ] 

Sharmadha Sainath edited comment on ATLAS-3177 at 5/29/19 6:31 AM:
---

[~ashutoshm] , But changeMarker is always set to value even older than the 
entity's creation timestamp.I tried quite many times. Due to this , incremental 
export is not adding any value. 

Also could you please explain what is request timestamp ? Is it the latest time 
stamp the entity was accessed / requested ?


was (Author: ssainath):
[~ashutoshm] , But changeMarker is always set to value even older than the 
entity's creation timestamp.I tried quite many times. Due to this , incremental 
export is not adding any value. 

> Regression , Export : changeMarker is not set right - set to older value 
> compared to entity's lastModifedTime
> -
>
> Key: ATLAS-3177
> URL: https://issues.apache.org/jira/browse/ATLAS-3177
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.1.0
>    Reporter: Sharmadha Sainath
>Priority: Major
> Fix For: 1.1.0, trunk
>
> Attachments: db_axyz.zip, db_def.json
>
>
> Export request body :
> {code}
> {"itemsToExport": [{"typeName": "hive_db", "uniqueAttributes": 
> {"qualifiedName": "database_rbltx@mycluster0"}}], "options": {"fetchType": 
> "incremental", "changeMarker": 0, "replicatedTo": "mycluster1"}}
> {code}
> The db's createTime is 1556276114134 (Friday, April 26, 2019 4:25:14.134 PM 
> GMT+05:30)
> updatedTime is 1556276125588 (Friday, April 26, 2019 4:25:25.588 PM GMT+05:30)
> The changeMarker in exported zip file is 1556187028462 (Thursday, April 25, 
> 2019 3:40:28.462 PM GMT+05:30)
> due to this unmodified entities are also exported everytime due to 
> incremental export.
> Attaching the entity definition of db entity and the exported zip.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-3177) Regression , Export : changeMarker is not set right - set to older value compared to entity's lastModifedTime

[Sharmadha Sainath (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16850538#comment-16850538
 ] 

Sharmadha Sainath commented on ATLAS-3177:
--

[~ashutoshm] , But changeMarker is always set to value even older than the 
entity's creation timestamp.I tried quite many times. Due to this , incremental 
export is not adding any value. 

> Regression , Export : changeMarker is not set right - set to older value 
> compared to entity's lastModifedTime
> -
>
> Key: ATLAS-3177
> URL: https://issues.apache.org/jira/browse/ATLAS-3177
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.1.0
>    Reporter: Sharmadha Sainath
>Priority: Major
> Fix For: 1.1.0, trunk
>
> Attachments: db_axyz.zip, db_def.json
>
>
> Export request body :
> {code}
> {"itemsToExport": [{"typeName": "hive_db", "uniqueAttributes": 
> {"qualifiedName": "database_rbltx@mycluster0"}}], "options": {"fetchType": 
> "incremental", "changeMarker": 0, "replicatedTo": "mycluster1"}}
> {code}
> The db's createTime is 1556276114134 (Friday, April 26, 2019 4:25:14.134 PM 
> GMT+05:30)
> updatedTime is 1556276125588 (Friday, April 26, 2019 4:25:25.588 PM GMT+05:30)
> The changeMarker in exported zip file is 1556187028462 (Thursday, April 25, 
> 2019 3:40:28.462 PM GMT+05:30)
> due to this unmodified entities are also exported everytime due to 
> incremental export.
> Attaching the entity definition of db entity and the exported zip.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ATLAS-3233) Relationships, Export & Import : Issue with ACTIVE and DELETED relationship-def instances

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-3233:


 Summary: Relationships, Export & Import : Issue with ACTIVE and 
DELETED relationship-def instances
 Key: ATLAS-3233
 URL: https://issues.apache.org/jira/browse/ATLAS-3233
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 1.0.0
Reporter: Sharmadha Sainath
 Fix For: 2.0.0


1. In source cluster , create 2 types and a relationship-def between them.
2. Create 2 entities and create relationship instance between them. 
(relationship_guid_1 is created and it is ACTIVE)
3. Export & Import entity1.
4. On target cluster , relationship_guid_1 is imported and it is ACTIVE.
5. Now, on source cluster , delete relationship_guid_1 and create a new 
relationship between entity1 and entity2.
6. In source cluster , relationship_guid_1 is DELETED and new 
relationship_guid_2 is ACTIVE.
7. Export and Import the entity1 to target cluster.
8. In target cluster , relationship_guid_1 is still ACTIVE and 
relationship_guid_2 is not imported at all . (GET on relationship_guid_2 throws 
404 on target cluster)
9. In the exported zip , there is no information about relationship_guid_1 but 
only about relationship_guid_2.

CC : [~ashutoshm]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-3232) Relationships, Export & Import : Updates to relationshipDef are not honored during import

[Sharmadha Sainath (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-3232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sharmadha Sainath updated ATLAS-3232:
-
Description: 
1. In source cluster , updated relationshipDef "hive_table_db" propagateTags to 
"ONE_TO_TWO" from NONE and exported.
2.In export zip  , atlas-typesdef.json has "ONE_TO_TWO" propagateTags value for 
"hive_table_db" . 
3. But in the import cluster, propagateTags value for hive_table_db is NONE 
still. In the import options , provided updateTypeDefinition to True too.

CC : [~ashutoshm] 

  was:
1. In source cluster , updated relationshipDef "hive_db_columns" propagateTags 
to "ONE_TO_TWO" from NONE and exported.
2.In export zip  , atlas-typesdef.json has "ONE_TO_TWO" propagateTags value for 
"hive_db_columns" . 
3. But in the import cluster, propagateTags value for hive_db_columns is NONE 
still. In the import options , provided updateTypeDefinition to True too.

CC : [~ashutoshm] 


> Relationships, Export & Import : Updates to relationshipDef are not honored 
> during import
> -
>
> Key: ATLAS-3232
> URL: https://issues.apache.org/jira/browse/ATLAS-3232
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Sharmadha Sainath
>Priority: Major
> Fix For: 2.0.0
>
>
> 1. In source cluster , updated relationshipDef "hive_table_db" propagateTags 
> to "ONE_TO_TWO" from NONE and exported.
> 2.In export zip  , atlas-typesdef.json has "ONE_TO_TWO" propagateTags value 
> for "hive_table_db" . 
> 3. But in the import cluster, propagateTags value for hive_table_db is NONE 
> still. In the import options , provided updateTypeDefinition to True too.
> CC : [~ashutoshm] 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ATLAS-3232) Relationships, Export & Import : Updates to relationshipDef are not honored during import

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-3232:


 Summary: Relationships, Export & Import : Updates to 
relationshipDef are not honored during import
 Key: ATLAS-3232
 URL: https://issues.apache.org/jira/browse/ATLAS-3232
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Sharmadha Sainath
 Fix For: 2.0.0


1. In source cluster , updated relationshipDef "hive_db_columns" propagateTags 
to "ONE_TO_TWO" from NONE and exported.
2.In export zip  , atlas-typesdef.json has "ONE_TO_TWO" propagateTags value for 
"hive_db_columns" . 
3. But in the import cluster, propagateTags value for hive_db_columns is NONE 
still. In the import options , provided updateTypeDefinition to True too.

CC : [~ashutoshm] 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] Release Apache Atlas version 2.0.0 - rc2

[Sharmadha Sainath]

+1 for Apache Atlas 2.0.0 release candidate #2

Thanks Sarath for the updated release candidate.

- Started Atlas with external HBase , Solr.
- Verified the new relationship changes of removing ownedRef and handling
them with Relationship categories
- Created Entity in UI , Created tags associated them to entities and
verified Tag Propagation.
- Performed Basic/DSL Search.
- Verified the new table format of displaying relationships.


Regards,
Sharmadha S.

On Wed, May 8, 2019 at 9:24 AM Ramesh Mani 
wrote:

> +1 for Apache Atlas Version 2.0.0-rc2
>
> Verified the build from the source
>
> https://dist.apache.org/repos/dist/dev/atlas/2.0.0-rc2/apache-atlas-2.0.0-sources.tar.gz
>
> Thanks,
> Ramesh
>
>
> On Tue, May 7, 2019 at 7:08 AM Nixon Rodrigues <
> nixon.rodrig...@freestoneinfotech.com> wrote:
>
> > Thanks Sarath for updated release candidate.
> >
> > +1 for Apache Atlas release candidate #2
> >
> > Verified following items:-
> >
> > Maven Rat check is fine.
> > Unit test runs fine
> > Tested Atlas UI by packaging in embedded-hbase mode.
> > Quick start data looks good.
> >
> > Looks good to me.
> >
> > Regards
> > Nixon Rodrigues
> >
> >
> >
> > On Tue, May 7, 2019 at 3:08 AM Sarath Subramanian 
> > wrote:
> >
> > > Atlas team,
> > >
> > > Apache Atlas 2.0.0 Release Candidate #2 is now available for a vote
> > within
> > > dev community.
> > >
> > > Following commits went into branch-2.0 since the last release candidate
> > > (rc1):
> > >  - ATLAS-3190: UI - Allow user to refresh metric data inside popup
> > >  - ATLAS-3155: UI - IE-11 - Name entry not clickable (#2)
> > >  - ATLAS-3188: Regression: Simple insert queries are being captured in
> > > ATLAS_HOOK topic
> > >  - ATLAS-3033: Skip hive temp table while getting Table object details
> > from
> > > hiveContext.
> > >  - ATLAS-3187: columns attribute is empty for deleted hive_table entity
> > >
> > > Links to the release artifacts are given below. Please review and vote.
> > >
> > > The vote will be open for at least 72 hours or until necessary votes
> are
> > > reached.
> > >   [ ] +1 approve
> > >   [ ] +0 no opinion
> > >   [ ] -1 disapprove (and reason why)
> > >
> > >
> > > Thanks,
> > > Sarath
> > >
> > >
> > > List of issues addressed in this release:
> > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ATLAS%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20%3D%202.0.0%20ORDER%20BY%20updated%20DESC%2C%20priority%20DESC
> > >
> > > Git tag for the release:
> > > https://github.com/apache/atlas/tree/release-2.0.0-rc2
> > > Sources for the release:
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/atlas/2.0.0-rc2/apache-atlas-2.0.0-sources.tar.gz
> > >
> > > Source release verification:
> > > PGP Signature:
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/atlas/2.0.0-rc2/apache-atlas-2.0.0-sources.tar.gz.asc
> > > SHA512
> > > <
> >
> https://dist.apache.org/repos/dist/dev/atlas/2.0.0-rc2/apache-atlas-2.0.0-sources.tar.gz.ascSHA512
> > >
> > > Hash:
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/atlas/2.0.0-rc2/apache-atlas-2.0.0-sources.tar.gz.sha512
> > > MD5
> > > <
> >
> https://dist.apache.org/repos/dist/dev/atlas/2.0.0-rc2/apache-atlas-2.0.0-sources.tar.gz.sha512MD5
> > >
> > > Hash:
> > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/atlas/2.0.0-rc2/apache-atlas-2.0.0-sources.tar.gz.md5
> > >
> > > Keys to verify the signature of the release artifacts are available at:
> > > https://dist.apache.org/repos/dist/release/atlas/KEYS
> > >
> >
>

Re: [VOTE] Release Apache Atlas version 2.0.0 - rc1

[Sharmadha Sainath]

+1 for Apache Atlas 2.0.0 release candidate #1


- Started Atlas with external HBase , Solr.
- Verified the new relationship changes of removing ownedRef and handling them 
with Relationship categories
- Created Entity in UI , Created tags associated them to entities and verified 
Tag Propagation.
- Performed Basic/DSL Search.
- Verified the new table format of displaying relationships.

Thanks Sarath for the release candidate.

Regards,
Sharmadha S.



On 5/3/19, 6:32 PM, "Nixon Rodrigues"  
wrote:

>Thanks Sarath for putting rc1 together for Atlas 2.0 release.
>
>Verified following things.
>
>   - The source code has no binaries present it.
>   - Checksum hash and Signature looks good.
>   - The tag for rc1 exists on branch2.0 repo.
>   - Unit test run was fine.
>   - The maven build was fine and was up & running with berkeley db elastic
>   profile.
>   - QuickStart data was loaded correctly on UI.
>   - Performed Sanity test for UI feature.
>
>*+1* for the rc1 for Atlas 2.0 release.
>
>Regards
>Nixon Rodrigues
>
>
>On Thu, May 2, 2019 at 1:24 PM Madhan Neethiraj  wrote:
>
>> Sarath - thanks for the updated release candidate.
>>
>> +1 for Apache Atlas 2.0.0 release candidate #1
>>
>> Performed the following:
>> - downloaded tar.gz and verified the signature
>> - built and installed Atlas for embedded HBase, Solr profile
>> - started Atlas with embedded HBase and Solr
>> - ran QuickStart successfully
>> - added/updated/deleted few 'Favorite Searches' - both basic and DSL
>> - performed number of searches - both basic and DSL
>> - created glossaries with number of terms, associated terms with entities,
>> associated terms with classifications
>> - verified classification propagations
>>
>> Thanks,
>> Madhan
>>
>>
>>
>>
>> On 4/29/19, 11:56 PM, "Sarath Subramanian"  wrote:
>>
>> Atlas team,
>>
>> Apache Atlas 2.0.0 Release Candidate #1 is now available for a vote
>> within
>> dev community.
>>
>> Following commits went into branch-2.0 since the last release candidate
>> (rc0):
>>
>>  - ATLAS-3168: Fix Intermittent UT failure:
>> KafkaNotificationTest.initNotificationService()
>>  - ATLAS-3148: Implement Hive Metastore hook for Atlas
>>  - ATLAS-3167: Exception while starting Atlas with Cassandra
>>  - ATLAS-3160: Remove unthrown exception specified in
>> AtlasRelationshipDef
>> constructors
>>  - ATLAS-3157: Add Integration tests for Hive metastore hook
>>  - ATLAS-3174: UI - Exclude process or deleted entity from search
>> drop-down
>> if respective options are chosen
>>  - ATLAS-3155: UI - IE-11 - Name entry not clickable
>>  - ATLAS-3168: PatchFix: Unit test fixes and optimization.
>>  - ATLAS-3168: PatchFix: Support for HA Mode
>>  - ATLAS-3129: Fix SSL Truststore reloader leak from AtlasBaseClient
>>  - ATLAS-3159: UI - Add Reset button for Lienage
>>  - ATLAS-3154: UI - Lineage PNG export not working on Firefox
>>  - ATLAS-3158: UI - Render schema tab using relationshipAttributes
>> (Columns)
>>  - ATLAS-3145: UI - Entity showing Active even if the
>> relationshipStatus is
>> Deleted.
>>
>> Links to the release artifacts are given below. Please review and vote.
>>
>> The vote will be open for at least 72 hours or until necessary votes
>> are
>> reached.
>>   [ ] +1 approve
>>   [ ] +0 no opinion
>>   [ ] -1 disapprove (and reason why)
>>
>>
>> Thanks,
>> Sarath
>>
>> List of issues addressed in this release:
>>
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20ATLAS%20AND%20status%20%3D%20Resolved%20AND%20fixVersion%20%3D%202.0.0%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC
>> Git tag for the release:
>> https://github.com/apache/atlas/tree/release-2.0.0-rc1
>> Sources for the release:
>>
>> https://dist.apache.org/repos/dist/dev/atlas/2.0.0-rc1/apache-atlas-2.0.0-sources.tar.gz
>>
>> Source release verification:
>> PGP Signature:
>>
>> https://dist.apache.org/repos/dist/dev/atlas/2.0.0-rc1/apache-atlas-2.0.0-sources.tar.gz.asc
>> SHA512 Hash:
>>
>> https://dist.apache.org/repos/dist/dev/atlas/2.0.0-rc1/apache-atlas-2.0.0-sources.tar.gz.sha512
>> MD5 Hash:
>>
>> https://dist.apache.org/repos/dist/dev/atlas/2.0.0-rc1/apache-atlas-2.0.0-sources.tar.gz.md5
>>
>> Keys to verify the signature of the release artifacts are available at:
>> https://dist.apache.org/repos/dist/release/atlas/KEYS
>>
>>
>>
>>

[jira] [Created] (ATLAS-3187) Regression, Relationship updates : In GET entity definition of a deleted table, columns,sd etc., are empty

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-3187:


 Summary: Regression, Relationship updates : In GET entity 
definition of a deleted table, columns,sd etc., are empty
 Key: ATLAS-3187
 URL: https://issues.apache.org/jira/browse/ATLAS-3187
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 2.0.0
Reporter: Sharmadha Sainath
 Fix For: 2.0.0
 Attachments: table_entity_def.json

Adding the table_entity_def["entity"]["attributes"]:

Here , table is deleted , but the columns array and sd are [] and null 
respectively. Expected is all entities in DELETED  state.

Attaching the complete table definition :
{code}
attributes: {
owner: "hrt_qa",
temporary: false,
lastAccessTime: 1556788686000,
aliases: null,
replicatedTo: null,
replicatedFrom: null,
qualifiedName: "default.table1@cl1",
columns: [ ],
description: null,
viewExpandedText: null,
tableType: "MANAGED_TABLE",
sd: null,
createTime: 1556788686000,
name: "table1",
comment: null,
partitionKeys: [ ],
parameters: {
totalSize: "0",
numRows: "0",
rawDataSize: "0",
transactional_properties: "default",
COLUMN_STATS_ACCURATE: "{"BASIC_STATS":"true","COLUMN_STATS":{"id":"true"}}",
numFiles: "0",
transient_lastDdlTime: "1556788686",
bucketing_version: "2",
transactional: "true"
},
retention: 0,
viewOriginalText: null,
db: {
guid: "ab02dd3b-1d1c-4522-8c2c-0fa60d82fcbe",
typeName: "hive_db"
}
}
{code}




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ATLAS-3177) Regression , Export : changeMarker is not set right - set to older value compared to entity's lastModifedTime

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-3177:


 Summary: Regression , Export : changeMarker is not set right - set 
to older value compared to entity's lastModifedTime
 Key: ATLAS-3177
 URL: https://issues.apache.org/jira/browse/ATLAS-3177
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 1.1.0
Reporter: Sharmadha Sainath
 Fix For: 2.0.0, 1.1.0
 Attachments: db_axyz.zip, db_def.json

Export request body :

{code}
{"itemsToExport": [{"typeName": "hive_db", "uniqueAttributes": 
{"qualifiedName": "database_rbltx@mycluster0"}}], "options": {"fetchType": 
"incremental", "changeMarker": 0, "replicatedTo": "mycluster1"}}
{code}

The db's createTime is 1556276114134 (Friday, April 26, 2019 4:25:14.134 PM 
GMT+05:30)
updatedTime is 1556276125588 (Friday, April 26, 2019 4:25:25.588 PM GMT+05:30)

The changeMarker in exported zip file is 1556187028462 (Thursday, April 25, 
2019 3:40:28.462 PM GMT+05:30)

due to this unmodified entities are also exported everytime due to incremental 
export.

Attaching the entity definition of db entity and the exported zip.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ATLAS-3176) Regression , Export : Export zip doesn't contain all entities which are listed in atlas-export-order.json

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-3176:


 Summary: Regression , Export : Export zip doesn't contain all 
entities which are listed in atlas-export-order.json
 Key: ATLAS-3176
 URL: https://issues.apache.org/jira/browse/ATLAS-3176
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 1.1.0, 2.0.0
Reporter: Sharmadha Sainath
 Fix For: 2.0.0
 Attachments: export.zip

In Previous versions , entities listed in atlas-export-order.json are present 
in zip as .json. In recent versions, hive_column_lineage entities 
are missing. But this doesn't affect import. The lineage is created between the 
columns without any issue. The hive_column_lineage information is present in 
entity definition of hive_table and hive_process so it creates the 
hive_column_lineage.
Attaching the zip file.

CC : [~ashutoshm]





--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (ATLAS-3108) Unable search terms at a subcategory glossary

[Sharmadha Sainath (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16806400#comment-16806400
 ] 

Sharmadha Sainath edited comment on ATLAS-3108 at 4/1/19 5:42 AM:
--

[~Raymond_C] , 

>> After creating category and subcategory via AtlasUI 
>> (http://sandbox-hdp.hortonworks.com:21000/), at the one subcategory, unable 
>> to search any terms.

In the attached screenshot ,I see that there is no sub category created yet for 
"2nd deliveryLeadTime". Here ,Time is the Glossary and "2nd deliveryLeadTime" 
is the category.

I see you're trying to search "deliveryLeadTime" - which is a Glossary.

So , if you want to create a term under Time , switch to "Terms" in the toggle 
, Create a term under the Glossary.

Now to assign Term to Category, you can either do that in "Terms" or toggle 
back to "Category".

By your example , toggle to "Category" , you will see "Terms +" (Terms Assign) 
button . Click on that and search the term you want to assign the category to.

Please let me know if you still find issues. Also , refer to 
http://atlas.apache.org/Glossary.html for more detailed information.





was (Author: ssainath):
[~Raymond_C] , 

>> After creating category and subcategory via AtlasUI 
>> (http://sandbox-hdp.hortonworks.com:21000/), at the one subcategory, unable 
>> to search any terms.

In the attached screenshot ,I see that there is no sub category created yet for 
"2nd deliveryLeadTime". Here ,Time is the Glossary and 2nd "deliveryLeadTime" 
is the category.

I see you're trying to search "deliveryLeadTime" - which is a Glossary.

So , if you want to create a term under Time , switch to "Terms" in the toggle 
, Create a term under the Glossary.

Now to assign Term to Category, you can either do that in "Terms" or toggle 
back to "Category".

By your example , toggle to "Category" , you will see "Terms +" (Terms Assign) 
button . Click on that and search the term you want to assign the category to.

Please let me know if you still find issues. Also , refer to 
http://atlas.apache.org/Glossary.html for more detailed information.




> Unable search terms at a subcategory glossary
> -
>
> Key: ATLAS-3108
> URL: https://issues.apache.org/jira/browse/ATLAS-3108
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 1.1.0
>Reporter: Raymond C
>Priority: Major
>  Labels: beginner
> Attachments: image-2019-03-31-12-51-55-042.png
>
>
> 1 Launching HDP Sandbox 3.0.
> 2 After creating category and subcategory via AtlasUI 
> ([http://sandbox-hdp.hortonworks.com:21000/]), at the one subcategory, unable 
> to search any terms. 
> 3 Typed one existing term, but did not show any term on the search bar. Also 
> the Assign button is invalid.
> !image-2019-03-31-12-51-55-042.png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-3108) Unable search terms at a subcategory glossary

[Sharmadha Sainath (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16806400#comment-16806400
 ] 

Sharmadha Sainath commented on ATLAS-3108:
--

[~Raymond_C] , 

>> After creating category and subcategory via AtlasUI 
>> (http://sandbox-hdp.hortonworks.com:21000/), at the one subcategory, unable 
>> to search any terms.

In the attached screenshot ,I see that there is no sub category created yet for 
"2nd deliveryLeadTime". Here ,Time is the Glossary and 2nd "deliveryLeadTime" 
is the category.

I see you're trying to search "deliveryLeadTime" - which is a Glossary.

So , if you want to create a term under Time , switch to "Terms" in the toggle 
, Create a term under the Glossary.

Now to assign Term to Category, you can either do that in "Terms" or toggle 
back to "Category".

By your example , toggle to "Category" , you will see "Terms +" (Terms Assign) 
button . Click on that and search the term you want to assign the category to.

Please let me know if you still find issues. Also , refer to 
http://atlas.apache.org/Glossary.html for more detailed information.




> Unable search terms at a subcategory glossary
> -
>
> Key: ATLAS-3108
> URL: https://issues.apache.org/jira/browse/ATLAS-3108
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 1.1.0
>Reporter: Raymond C
>Priority: Major
>  Labels: beginner
> Attachments: image-2019-03-31-12-51-55-042.png
>
>
> 1 Launching HDP Sandbox 3.0.
> 2 After creating category and subcategory via AtlasUI 
> ([http://sandbox-hdp.hortonworks.com:21000/]), at the one subcategory, unable 
> to search any terms. 
> 3 Typed one existing term, but did not show any term on the search bar. Also 
> the Assign button is invalid.
> !image-2019-03-31-12-51-55-042.png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ATLAS-3101) UI,Regression : Unable to search by _CLASSIFIED

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-3101:


 Summary: UI,Regression : Unable to search by _CLASSIFIED
 Key: ATLAS-3101
 URL: https://issues.apache.org/jira/browse/ATLAS-3101
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Reporter: Sharmadha Sainath


On selecting _CLASSIFIED in classifications dropdown , "Search" button is not 
enabled.

After selecting _CLASSIFIED in classifications dropdown, selecting a type (say 
hive_table) from types list , clears the _CLASSIFIED in classifications.

CC : [~kevalbhatt]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ATLAS-3086) Regression : Atlas Hive Hook doesn't capture insert into table values() queries

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-3086:


 Summary: Regression : Atlas Hive Hook doesn't capture insert into 
table values() queries
 Key: ATLAS-3086
 URL: https://issues.apache.org/jira/browse/ATLAS-3086
 Project: Atlas
  Issue Type: Bug
  Components: atlas-intg
Affects Versions: 1.0.0
Reporter: Sharmadha Sainath
 Fix For: 2.0.0


Atlas Hive Hook doesn't capture the query "insert into table values()" . This 
is a regression as this event was captured in 0.8

Other queries like 
"from table1 a insert overwrite table bkp_table select a.id",
"insert into tableB select c1,c2 from tableA" , information is captured and 
lineage is created in 1.0



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ATLAS-3068) Regression : Removal of ownedRef/inverseRef constraints in hive types causes related entities missing from the response's "attributes"

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-3068:


 Summary: Regression : Removal of ownedRef/inverseRef constraints 
in hive types causes related entities missing from the response's "attributes"
 Key: ATLAS-3068
 URL: https://issues.apache.org/jira/browse/ATLAS-3068
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 1.2.0, 2.0.0
Reporter: Sharmadha Sainath
 Fix For: 1.2.0, 2.0.0


In GET entity response of hive_table , "attributes" doesn't have table, column 
attributes anymore due to recent change 
[ATLAS-3067|https://issues.apache.org/jira/browse/ATLAS-3067].

Example :
{code}
attributes: {
owner: "admin",
temporary: false,
lastAccessTime: 769588200,
aliases: null,
replicatedTo: null,
replicatedFrom: null,
qualifiedName: "default.hive_table_nogsc_9@cl1",
description: null,
viewExpandedText: null,
tableType: "MANAGED_TABLE",
createTime: 1552306685000,
name: "hive_table_nogsc_9",
comment: null,
parameters: {
totalSize: "0",
numRows: "0",
rawDataSize: "0",
transactional_properties: "default",
COLUMN_STATS_ACCURATE: 
"{"BASIC_STATS":"true","COLUMN_STATS":{"id":"true","name":"true"}}",
numFiles: "0",
transient_lastDdlTime: "1552306685",
bucketing_version: "2",
transactional: "true"
},
retention: 1,
viewOriginalText: null
},
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] Release Apache Atlas v 0.8.3 - RC0

[Sharmadha Sainath]

+1 for the release


1.Verified the existing export & import functionality, incremental export, new 
options in the import , AtlasServer datatype and audits.
2.Verified Basic Search , DSL Search.
3.Verified the Basic UI functionalities such as search , navigate to entities , 
tag creation/association/disassociation.

Thanks,
Sharmadha S.




On 10/21/18, 8:26 AM, "Apoorv Naik"  wrote:

>+1 for the release Ashutosh.
>
>1. Verified signature
>2. Built with embedded hbase and solr profile
>3. Basic search and DSL works as expected
>
>Thanks for putting in the effort towards this release.
>
>*Apoorv Naik*
>
>
>On Sat, Oct 20, 2018 at 11:35 AM Sarath Subramanian 
>wrote:
>
>> Thanks Ashutosh for putting together release candidate #0 for Apache Atlas
>> 0.8.3
>>
>> Verified the following:
>>
>>- Verified PGP Signature and hash
>>- Build the source using embedded HBase and Solr profile, build was
>>successful
>>- Ran quick start and validated basic functionality - basic search,
>>import-export, advanced search.
>>
>> +1 for release of Apache Atlas 0.8.3 rc0
>>
>> Thanks,
>> Sarath
>>
>> On Wed, Oct 17, 2018 at 4:14 PM Ashutosh Mestry 
>> wrote:
>>
>> > Apache Atlas 0.8.3 Release Candidate #0 is now available for a vote
>> within
>> > dev community.
>> >
>> > Links to the release artifacts are given below. Please review and vote.
>> >
>> > The vote will be open for at least 72 hours or until necessary votes are
>> > reached.
>> >   [ ] +1 approve
>> >   [ ] +0 no opinion
>> >   [ ] -1 disapprove (and reason why)
>> >
>> > Ashutosh Mestry
>> >
>> > List of issues addressed in this release:
>> >
>> https://issues.apache.org/jira/browse/ATLAS-2924?jql=project%20%3D%20ATLAS%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%200.8.3%20ORDER%20BY%20key%20DESC
>> >
>> > Git tag for the release:
>> > https://github.com/apache/atlas/tree/release-0.8.3-rc0
>> >
>> > Sources for the release:
>> >
>> https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc0/apache-atlas-0.8.3-sources.tar.gz
>> >
>> > Source release verification:
>> > PGP Signature:
>> >
>> https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc0/apache-atlas-0.8.3-sources.tar.gz.asc
>> > SHA512
>> > <
>> https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc0/apache-atlas-0.8.3-sources.tar.gz.ascSHA512
>> >
>> > Hash:
>> >
>> https://dist.apache.org/repos/dist/dev/atlas/0.8.3-rc0/apache-atlas-0.8.3-sources.tar.gz.sha512
>> >
>> > Keys to verify the signature of the release artifacts are available at:
>> > https://dist.apache.org/repos/dist/dev/atlas/KEYS
>> >
>> >
>> >
>>

Re: Referring existing entities in Atlas using Rest API

[Sharmadha Sainath]

Hi Anshu ,

Yes, array should be used.
Example:

   "Locations":[
  {  
 guid:"",
 typeName:“"
  },
  {  
 guid:"",
 typeName:“"
  },
  {  
 guid:"",
 typeName:“"
  }
…...
   ]


Thanks,
Sharmadha S.







On 10/13/18, 11:03 AM, "anshu shukla"  wrote:

>Hi,
>
>Thanks for replying this thing works perfectly for the single referential
>entity but *what format to be used for an array of already existing
>entities. *
>*Can we use an array of JSON for that attribute?*
>
>On Thu, Oct 11, 2018 at 2:58 PM Nixon Rodrigues <
>nixon.rodrig...@freestoneinfotech.com> wrote:
>
>> Hi Anshu,
>>
>> You can connect to existing entity be referring the guid of already
>> created entity.
>> Below is the format of JSON.
>>
>>  {
>>
>> "entity": {
>>  ...
>>  ...
>> "Location" : {
>> "guid": "<%Existing entity guid)%>",
>> "typeName": ""
>> ...
>> ...
>> }
>>
>> }
>>
>>
>>
>> On Thu, Oct 11, 2018 at 2:21 PM Anshu Shukla 
>> wrote:
>>
>>> Hi,
>>>
>>> I have used Atlas-scripts in dev-support folder to create entities using
>>> the given json example file.
>>> But there is no example to guide and show how to connect to an already
>>> existing entity in case new entity have attribute of that type.
>>>
>>> Example-
>>>
>>>  Location is an attribute inside the  Source
>>> type.   [Using Rest API's]
>>>
>>
>
>-- 
>Thanks & Regards,
>Anshu Shukla

[jira] [Created] (ATLAS-2900) Regression : Import fails with Error converting file to JSON

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2900:


 Summary: Regression : Import fails with Error converting file to 
JSON
 Key: ATLAS-2900
 URL: https://issues.apache.org/jira/browse/ATLAS-2900
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Sharmadha Sainath
 Attachments: uPqvN.zip

On Importing the attached zip file , request fails with 
{code}
2018-09-26 23:02:50,705 INFO  - [pool-2-thread-18 - 
84ea8d84-ead8-428d-a4db-4451812dd241:] ~ ==> import(user=admin, 
from=10.22.16.153, request=AtlasImportRequest{options={}}) (ImportService:89)
2018-09-26 23:02:50,864 INFO  - [pool-2-thread-18 - 
84ea8d84-ead8-428d-a4db-4451812dd241:] ~ bulkImport(): progress: 14% (of 7) - 
entity:last-imported:hive_table:[1]:(d7773c32-ce56-4d8a-96c1-5a4aa97e982e) 
(AtlasEntityStoreV1:146)
2018-09-26 23:02:50,865 ERROR - [pool-2-thread-18 - 
84ea8d84-ead8-428d-a4db-4451812dd241:] ~ getNextEntityWithExtInfo 
(ZipSource:213)
org.apache.atlas.exception.AtlasBaseException: Error converting file to JSON.
at 
org.apache.atlas.repository.impexp.ZipSource.convertFromJson(ZipSource.java:177)
at 
org.apache.atlas.repository.impexp.ZipSource.getEntityWithExtInfo(ZipSource.java:139)
at 
org.apache.atlas.repository.impexp.ZipSource.getNextEntityWithExtInfo(ZipSource.java:211)
at 
org.apache.atlas.repository.store.graph.v1.BulkImporterImpl$EntityImportStreamWithResidualList.getNextEntityWithExtInfo(BulkImporterImpl.java:183)
at 
org.apache.atlas.repository.store.graph.v1.BulkImporterImpl.bulkImport(BulkImporterImpl.java:72)
at 
org.apache.atlas.repository.impexp.ImportService.processEntities(ImportService.java:213)
at 
org.apache.atlas.repository.impexp.ImportService.run(ImportService.java:100)
at 
org.apache.atlas.web.resources.AdminResource.importData(AdminResource.java:390)
at sun.reflect.GeneratedMethodAccessor227.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
at 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at 
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1507)
at 
org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:76)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1495)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:317)
at 
org.apache.atlas.web.filters.AtlasAuthorizationFilter.doFilter(AtlasAuthorizationFilter.java:157)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
at 
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:127)
at 
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java

[jira] [Created] (ATLAS-2899) Regression : When export "options" is provided null , export fails with NPE at getSkipLineageOptionValue

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2899:


 Summary: Regression : When export "options" is provided null , 
export fails with NPE at getSkipLineageOptionValue
 Key: ATLAS-2899
 URL: https://issues.apache.org/jira/browse/ATLAS-2899
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Sharmadha Sainath


With the following export "options" , export fails with NPE at 
getSkipLineageOptionValue(AtlasExportRequest.java:97) :

{code}
{  
   "itemsToExport":[  
  {  
 "typeName":"hdfs_path",
 "uniqueAttributes":{  
"qualifiedName":"/atlas"
 }
  }
   ],
   "options":null
}
{code}
whereas , when no options key is specified or some valid options are provided , 
export succeeds.

Complete exception stack trace :
{code}
2018-09-26 20:23:30,967 ERROR - [pool-2-thread-18 - 
76af7fbc-cdc6-4196-9273-bc8b40b62d15:] ~ Error handling a request: 
eca69d150a7a5b5c (ExceptionMapperUtil:32)
java.lang.NullPointerException
at 
org.apache.atlas.model.impexp.AtlasExportRequest.getSkipLineageOptionValue(AtlasExportRequest.java:97)
at 
org.apache.atlas.repository.impexp.ExportService$ExportContext.(ExportService.java:633)
at 
org.apache.atlas.repository.impexp.ExportService.run(ExportService.java:97)
at 
org.apache.atlas.web.resources.AdminResource.export(AdminResource.java:342)
at sun.reflect.GeneratedMethodAccessor200.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at 
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at 
com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at 
com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at 
com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at 
com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1542)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1473)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1419)
at 
com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1409)
at 
com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:409)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:558)
at 
com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:733)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1507)
at 
org.apache.atlas.web.filters.AuditFilter.doFilter(AuditFilter.java:76)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1495)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:317)
at 
org.apache.atlas.web.filters.AtlasAuthorizationFilter.doFilter(AtlasAuthorizationFilter.java:157)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
at 
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:127)
at 
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:91)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
at 
org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:114)
at 
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
at 
org.springframework.security.web.session.SessionManagementFilter.doFilter(Sessi

Re: [VOTE] Release Apache Atlas version 1.1.0 - rc2

[Sharmadha Sainath]

Verified the following functionalities:

- Hooks - Hive , HBase.
- Verified tag propagation change with respect to deleted entities.
- UI functionalities like Creating , Associating tag , Search,Update 
relationship for tag propagation, Update flag to propagate tag incase of entity 
deletion.
- Verified the hard delete feature.
- Verified Basic and DSL search , Save search.

+1 for Apache Atlas 1.1.0 rc2.


Thanks,
Sharmadha S.






On 9/6/18, 12:44 PM, "Nixon Rodrigues"  
wrote:

>Atlas team,
>
>Apache Atlas 1.1.0 release candidate #2 is now available for a vote within
>dev community.
>
>Following 1 commits went into branch-1.0 since the last release candidate,
>#1, was sent 3 days back.
>
>  ATLAS-2857:Fix Atlas release version in /api/atlas/version API.
>
>Links to the release artifacts are given below. Please review and vote.
>
>The vote will be open for at least 72 hours or until necessary votes are
>reached.
>  [ ] +1 approve
>  [ ] +0 no opinion
>  [ ] -1 disapprove (and reason why)
>
>Here is my +1
>
>Thanks,
>Nixon Rodrigues
>
>List of issues addressed in this release:
>https://issues.apache.org/jira/issues/?jql=project%3DAtlas%20AND%20resolution%3DFixed%20AND%20fixVersion%3D1.1.0%20ORDER%20BY%20key%20DESC=50
>
>Git tag for the release:
>https://github.com/apache/atlas/tree/release-1.1.0-rc2
>
>Sources for the release:
>https://dist.apache.org/repos/dist/dev/atlas/1.1.0-rc2/apache-atlas-1.1.0-sources.tar.gz
>
>Source release verification:
>  PGP Signature:
>https://dist.apache.org/repos/dist/dev/atlas/1.1.0-rc2/apache-atlas-1.1.0-sources.tar.gz.asc
>  SHA512 Hash:
>https://dist.apache.org/repos/dist/dev/atlas/1.1.0-rc2/apache-atlas-1.1.0-sources.tar.gz.sha512
>
>Keys to verify the signature of the release artifacts are available at:
>https://dist.apache.org/repos/dist/dev/atlas/KEYS

[jira] [Created] (ATLAS-2826) Saving Search fails with 403 auth error after the new relationship auth changes

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2826:


 Summary: Saving Search fails with 403 auth error after the new 
relationship auth changes
 Key: ATLAS-2826
 URL: https://issues.apache.org/jira/browse/ATLAS-2826
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 1.1.0
Reporter: Sharmadha Sainath
 Attachments: SaveSearchLog.txt

Saving search as any user fails with 403 after new fine grained authorization 
support added for relationship.

Attached the complete stack trace.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Atlas Typesystem

[Sharmadha Sainath]

Hi Anshul ,

Predefined type models are found in 
https://github.com/apache/atlas/blob/master/addons/models . 

For Storm specifically , please refer 
https://github.com/apache/atlas/blob/master/addons/models/1000-Hadoop/1080-storm_model.json
 


Thanks,
Sharmadha S.



On 7/23/18, 12:16 PM, "Anshu Shukla"  wrote:

>Hi,
>
>I was going thru the Apache atlas code and unable to find that how default 
>type system in created in Atlas.
>
>The one I can see thru query at - http://:21000/api/atlas/types/storm_node
>
>But unable to find which part of code have populated that.
>
>
>Thanks

Re: [VOTE] Release Apache Atlas version 1.0.0 - rc2

[Sharmadha Sainath]

+1 for Apache Atlas 1.0.0 rc2

Downloaded source tar file and able to build it successfully from 
https://dist.apache.org/repos/dist/dev/atlas/1.0.0-rc2/apache-atlas-1.0.0-sources.tar.gz
Verified Tag propagation feature.
Verified HBase Hook functionality.
Verified UI updates with respect to Relationships , Tag Propagation.

Thanks,
Sharmadha S.


On 5/30/18, 1:01 PM, "Madhan Neethiraj"  wrote:

>Atlas team,
> 
>Apache Atlas 1.0.0 release candidate #2 is now available for a vote within dev 
>community.
> 
>Following commit went into branch-1.0 since the last release candidate, #1, 
>was sent yesterday.
>  ATLAS-2726: updated migration-import to add __name property to 
> classification edges
> 
>Links to the release artifacts are given below. Please review and vote.
> 
>The vote will be open for at least 72 hours or until necessary votes are 
>reached.
>  [ ] +1 approve
>  [ ] +0 no opinion
>  [ ] -1 disapprove (and reason why)
> 
>Thanks,
>Madhan
> 
> 
>List of issues addressed in this release: 
>https://issues.apache.org/jira/issues/?jql=project%20%3D%20Atlas%20AND%20resolution%20!%3D%20Unresolved%20%20AND%20fixVersion%20%3D%201.0.0%20ORDER%20BY%20key%20DESC
> 
>Git tag for the release: https://github.com/apache/atlas/tree/release-1.0.0-rc2
> 
>Sources for the release: 
>https://dist.apache.org/repos/dist/dev/atlas/1.0.0-rc2/apache-atlas-1.0.0-sources.tar.gz
> 
>Documentation for the release: http://atlas.apache.org/1.0.0-rc0/index.html
> 
>Source release verification:
>  PGP Signature: 
> https://dist.apache.org/repos/dist/dev/atlas/1.0.0-rc2/apache-atlas-1.0.0-sources.tar.gz.asc
>  SHA512 Hash: 
> https://dist.apache.org/repos/dist/dev/atlas/1.0.0-rc2/apache-atlas-1.0.0-sources.tar.gz.sha512
> 
>Keys to verify the signature of the release artifacts are available at: 
>https://dist.apache.org/repos/dist/dev/atlas/KEYS
>
>
>

[jira] [Created] (ATLAS-2697) V2 Notifications : "Propagated classification added" audit message is present instead of "classification added"

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2697:


 Summary: V2 Notifications : "Propagated classification added" 
audit message is present instead of "classification added"
 Key: ATLAS-2697
 URL: https://issues.apache.org/jira/browse/ATLAS-2697
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 1.0.0
    Reporter: Sharmadha Sainath


With V2 notifications ,when tag is added to an entity , instead of 
"classification added" audit  , "Propagated classification added" audit message 
is present.

CC : [~sarath.ku...@gmail.com] [~nixonrodrigues]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Review Request 65937: ATLAS-2475:HBase Atlas import utility : importing using -t default:table fails when namespace is default

[Sharmadha Sainath]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/65937/#review198768
---


Ship it!




Ship It!

- Sharmadha Sainath


On March 6, 2018, 11:43 p.m., Ramesh Mani wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65937/
> ---
> 
> (Updated March 6, 2018, 11:43 p.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj and Sharmadha Sainath.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-2475:HBase Atlas import utility : importing using -t default:table 
> fails when namespace is default
> 
> 
> Diffs
> -
> 
>   
> addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/util/ImportHBaseEntities.java
>  cf3a9fc 
> 
> 
> Diff: https://reviews.apache.org/r/65937/diff/1/
> 
> 
> Testing
> ---
> 
> Tested with local VM
> 
> 
> Thanks,
> 
> Ramesh Mani
> 
>

[jira] [Created] (ATLAS-2475) HBase Atlas import utility : importing using -t default:table fails when namespace is default

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2475:


 Summary: HBase Atlas import utility : importing using -t 
default:table fails when namespace is default
 Key: ATLAS-2475
 URL: https://issues.apache.org/jira/browse/ATLAS-2475
 Project: Atlas
  Issue Type: Bug
  Components: atlas-intg
Affects Versions: 1.0.0
Reporter: Sharmadha Sainath
 Fix For: 1.0.0


Running following scripts work :

./import-hbase.sh -t ns1:table5
./import-hbase.sh -t table2

But following import script specifying default namespace doesn't work :

./import-hbase.sh -t default:table2

and throws following exception :
{code}
Exception in thread "main" org.apache.atlas.hook.AtlasHookException: 
ImportHBaseEntities failed.
at 
org.apache.atlas.hbase.util.ImportHBaseEntities.main(ImportHBaseEntities.java:57)
Caused by: java.lang.NullPointerException
at 
org.apache.atlas.hbase.util.ImportHBaseEntities.importTable(ImportHBaseEntities.java:115)
at 
org.apache.atlas.hbase.util.ImportHBaseEntities.execute(ImportHBaseEntities.java:88)
at 
org.apache.atlas.hbase.util.ImportHBaseEntities.main(ImportHBaseEntities.java:54)
Failed to import HBase Data Model!!!
{code}

In HBase shell , it is possible to create table in default namespace by 
specifying the default namespace explicitly :
> create 'default:table2,'cf1'

so ,expectation is that importing by explicitly specifying default namespace 
also should work.

CC : [~rmani]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Review Request 65697: ATLAS-2455:HBase Atlas Hook: ColumnFamily attribute cacheDataOnWrite has wrong value assigned

[Sharmadha Sainath]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/65697/#review197716
---


Ship it!




Ship It!

- Sharmadha Sainath


On Feb. 17, 2018, 1:10 a.m., Ramesh Mani wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/65697/
> ---
> 
> (Updated Feb. 17, 2018, 1:10 a.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj and Sharmadha Sainath.
> 
> 
> Bugs: ATLAS-2455
> https://issues.apache.org/jira/browse/ATLAS-2455
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-2455:HBase Atlas Hook: ColumnFamily attribute cacheDataOnWrite has 
> wrong value assigned
> 
> 
> Diffs
> -
> 
>   
> addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/bridge/HBaseAtlasHook.java
>  11f24a7 
> 
> 
> Diff: https://reviews.apache.org/r/65697/diff/1/
> 
> 
> Testing
> ---
> 
> testing done in local vm
> 
> 
> Thanks,
> 
> Ramesh Mani
> 
>

[jira] [Comment Edited] (ATLAS-2453) Atlas HBase Hook : Datatype of maxFileSize should be Long instead of Integer

[Sharmadha Sainath (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16367478#comment-16367478
 ] 

Sharmadha Sainath edited comment on ATLAS-2453 at 2/16/18 3:38 PM:
---

Review Request : https://reviews.apache.org/r/65688/

CC : [~rmani]


was (Author: ssainath):
Review Request : https://reviews.apache.org/r/65688/

> Atlas HBase Hook : Datatype of maxFileSize should be Long instead of Integer
> 
>
> Key: ATLAS-2453
> URL: https://issues.apache.org/jira/browse/ATLAS-2453
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>    Reporter: Sharmadha Sainath
>Priority: Major
> Attachments: ATLAS-2453.patch
>
>
> maxFileSize attribute of hbase_table should be of type long.
> Currently it is an Integer , hence , when creating/updating hbase_table with 
> maxFileSize value more than integer's range , data between HBase and Atlas is 
> inconsistent.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2453) Atlas HBase Hook : Datatype of maxFileSize should be Long instead of Integer

[Sharmadha Sainath (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16367478#comment-16367478
 ] 

Sharmadha Sainath commented on ATLAS-2453:
--

Review Request : https://reviews.apache.org/r/65688/

> Atlas HBase Hook : Datatype of maxFileSize should be Long instead of Integer
> 
>
> Key: ATLAS-2453
> URL: https://issues.apache.org/jira/browse/ATLAS-2453
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>    Reporter: Sharmadha Sainath
>Priority: Major
> Attachments: ATLAS-2453.patch
>
>
> maxFileSize attribute of hbase_table should be of type long.
> Currently it is an Integer , hence , when creating/updating hbase_table with 
> maxFileSize value more than integer's range , data between HBase and Atlas is 
> inconsistent.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2453) Atlas HBase Hook : Datatype of maxFileSize should be Long instead of Integer

[Sharmadha Sainath (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sharmadha Sainath updated ATLAS-2453:
-
Attachment: ATLAS-2453.patch

> Atlas HBase Hook : Datatype of maxFileSize should be Long instead of Integer
> 
>
> Key: ATLAS-2453
> URL: https://issues.apache.org/jira/browse/ATLAS-2453
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>    Reporter: Sharmadha Sainath
>Priority: Major
> Attachments: ATLAS-2453.patch
>
>
> maxFileSize attribute of hbase_table should be of type long.
> Currently it is an Integer , hence , when creating/updating hbase_table with 
> maxFileSize value more than integer's range , data between HBase and Atlas is 
> inconsistent.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ATLAS-2453) Atlas HBase Hook : Datatype of maxFileSize should be Long instead of Integer

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2453:


 Summary: Atlas HBase Hook : Datatype of maxFileSize should be Long 
instead of Integer
 Key: ATLAS-2453
 URL: https://issues.apache.org/jira/browse/ATLAS-2453
 Project: Atlas
  Issue Type: Bug
  Components: atlas-intg
Reporter: Sharmadha Sainath


maxFileSize attribute of hbase_table should be of type long.

Currently it is an Integer , hence , when creating/updating hbase_table with 
maxFileSize value more than integer's range , data between HBase and Atlas is 
inconsistent.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2452) HBase Atlas Hook : isReadOnly hbase_table parameter is always false

[Sharmadha Sainath (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16367305#comment-16367305
 ] 

Sharmadha Sainath commented on ATLAS-2452:
--

Review request : https://reviews.apache.org/r/65684/

> HBase Atlas Hook : isReadOnly hbase_table parameter is always false
> ---
>
> Key: ATLAS-2452
> URL: https://issues.apache.org/jira/browse/ATLAS-2452
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>    Reporter: Sharmadha Sainath
>Priority: Major
> Attachments: ATLAS-2452.patch
>
>
> isReadOnly hbase_table attribute is always set as -1 because of :
> table.setAttribute(ATTR_TABLE_ISREADONLY, htableDescriptor.getMaxFileSize()); 
> (https://github.com/apache/atlas/blob/master/addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/bridge/HBaseAtlasHook.java#L453)
> Change needed to use htableDescriptor.isReadOnly() instead of 
> htableDescriptor.getMaxFileSize().
> CC : [~rmani]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2452) HBase Atlas Hook : isReadOnly hbase_table parameter is always false

[Sharmadha Sainath (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sharmadha Sainath updated ATLAS-2452:
-
Attachment: ATLAS-2452.patch

> HBase Atlas Hook : isReadOnly hbase_table parameter is always false
> ---
>
> Key: ATLAS-2452
> URL: https://issues.apache.org/jira/browse/ATLAS-2452
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>    Reporter: Sharmadha Sainath
>Priority: Major
> Attachments: ATLAS-2452.patch
>
>
> isReadOnly hbase_table attribute is always set as -1 because of :
> table.setAttribute(ATTR_TABLE_ISREADONLY, htableDescriptor.getMaxFileSize()); 
> (https://github.com/apache/atlas/blob/master/addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/bridge/HBaseAtlasHook.java#L453)
> Change needed to use htableDescriptor.isReadOnly() instead of 
> htableDescriptor.getMaxFileSize().
> CC : [~rmani]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ATLAS-2452) HBase Atlas Hook : isReadOnly hbase_table parameter is always false

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2452:


 Summary: HBase Atlas Hook : isReadOnly hbase_table parameter is 
always false
 Key: ATLAS-2452
 URL: https://issues.apache.org/jira/browse/ATLAS-2452
 Project: Atlas
  Issue Type: Bug
  Components: atlas-intg
Reporter: Sharmadha Sainath


isReadOnly hbase_table attribute is always set as -1 because of :

table.setAttribute(ATTR_TABLE_ISREADONLY, htableDescriptor.getMaxFileSize()); 
(https://github.com/apache/atlas/blob/master/addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/bridge/HBaseAtlasHook.java#L453)

Change needed to use htableDescriptor.isReadOnly() instead of 
htableDescriptor.getMaxFileSize().

CC : [~rmani]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ATLAS-2423) UI : Min values for Double and Float require modification

[Sharmadha Sainath (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16344503#comment-16344503
 ] 

Sharmadha Sainath commented on ATLAS-2423:
--

Review request : https://reviews.apache.org/r/65417/

> UI : Min values for Double and Float require modification
> -
>
> Key: ATLAS-2423
> URL: https://issues.apache.org/jira/browse/ATLAS-2423
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>    Reporter: Sharmadha Sainath
>Priority: Major
> Attachments: ATLAS-2423.patch
>
>
> https://github.com/apache/atlas/blob/master/dashboardv2/public/js/utils/Enums.js
>  has hard coded values for min and max values for double and float :
> {code}
>  "float": {
> min: 1.4E-45,
> max: 3.4028235E38
> },
> "double": {
> min: 4.9E-324,
> max: 1.7976931348623157E308
> }
> {code}
> Hence UI doesn't allow negative values at all in faceted search.
> Values should be -3.4028235E38 and -1.7976931348623157E308 for min value of 
> float and double respectively.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ATLAS-2423) UI : Min values for Double and Float require modification

[Sharmadha Sainath (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sharmadha Sainath updated ATLAS-2423:
-
Attachment: ATLAS-2423.patch

> UI : Min values for Double and Float require modification
> -
>
> Key: ATLAS-2423
> URL: https://issues.apache.org/jira/browse/ATLAS-2423
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>    Reporter: Sharmadha Sainath
>Priority: Major
> Attachments: ATLAS-2423.patch
>
>
> https://github.com/apache/atlas/blob/master/dashboardv2/public/js/utils/Enums.js
>  has hard coded values for min and max values for double and float :
> {code}
>  "float": {
> min: 1.4E-45,
> max: 3.4028235E38
> },
> "double": {
> min: 4.9E-324,
> max: 1.7976931348623157E308
> }
> {code}
> Hence UI doesn't allow negative values at all in faceted search.
> Values should be -3.4028235E38 and -1.7976931348623157E308 for min value of 
> float and double respectively.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (ATLAS-2423) UI : Min values for Double and Float require modification

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2423:


 Summary: UI : Min values for Double and Float require modification
 Key: ATLAS-2423
 URL: https://issues.apache.org/jira/browse/ATLAS-2423
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Reporter: Sharmadha Sainath


https://github.com/apache/atlas/blob/master/dashboardv2/public/js/utils/Enums.js
 has hard coded values for min and max values for double and float :
{code}
 "float": {
min: 1.4E-45,
max: 3.4028235E38
},
"double": {
min: 4.9E-324,
max: 1.7976931348623157E308
}
{code}

Hence UI doesn't allow negative values at all in faceted search.
Values should be -3.4028235E38 and -1.7976931348623157E308 for min value of 
float and double respectively.




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] Release Apache Atlas version 1.0.0-alpha release candidate 2

[Sharmadha Sainath]

+1 for 1.0.0-alpha-rc2


Verification done :
1. New DSL search changes.
2. UI functionality - Search , Tag creation , Tag 
Association/Disassociation/modification of attributes , Entity 
Creation/Modification on UI , Navigating to entities , detailsPage of entity, 
Saving search.
3. Type and entity creation,update using V1 and V2 APIs. 

Thanks,
Sharmadha S.



On 1/24/18, 2:04 AM, "Ramesh Mani"  wrote:

>+1 for 1.0.0-alpha release candidate 2
>
>Verified build from the source
>https://dist.apache.org/repos/dist/dev/atlas/1.0.0-alpha-rc2/apache-atlas-1
>.0.0-alpha-sources.tar.gz
>Verified some of the source files.
>
>Thanks,
>Ramesh
>
>
>
>On 1/19/18, 5:36 AM, "Keval Bhatt"  wrote:
>
>>Atlas team,
>>
>>
>>Apache Atlas 1.0.0-alpha release candidate #2 is now available for a vote
>>within dev community.
>>Links to the release artifacts are given below. Please review and vote.
>>
>>
>>The vote will be open for at least 72 hours or until the required number
>>of
>>votes are obtained.
>>
>>
>>[ ] +1 approve
>>
>>[ ] +0 no opinion
>>
>>[ ] -1 disapprove (and reason why)
>>
>>
>>+1 from my side for the release.
>>
>>
>>Changes since the last release candidate:
>>
>>ATLAS-2365: updated README for 1.0.0-alpha release
>>>ee14c8>
>>
>>
>>Thanks,
>>Keval Bhatt
>>
>>
>>Git tag for the release: https://github.com/apache/atlas/tree/release-1.0.
>>0-alpha-rc2
>>
>>
>>
>>Sources for the release: https://dist.apache.org/repos/dist/dev/atlas/1.0.
>>0-alpha-rc2/apache-atlas-1.0.0-alpha-sources.tar.gz
>>
>>
>>Source release verification:
>>  PGP Signature: https://dist.apache.org/repos/dist/dev/
>>atlas/1.0.0-alpha-rc2/apache-atlas-1.0.0-alpha-sources.tar.gz.asc
>>  MD5 Hash: https://dist.apache.org/repos/dist/dev/atlas/1.0.0-
>>alpha-rc2/apache-atlas-1.0.0-alpha-sources.tar.gz.md5
>>
>>Keys to verify the signature of the release artifacts are available at
>>https://dist.apache.org/repos/dist/dev/atlas/KEYS
>>
>>List of improvements and issues addressed in this release:
>>https://issues.apache.org/jira/issues/?jql=project%
>>20%3D%20Atlas%20AND%20resolution%20IN%20%20(Fixed%2CResolved
>>)%20AND%20fixVersion%20IN%20(1.0.0%2C1.0.0-alpha)
>

[jira] [Created] (ATLAS-2328) Regression : Request body with invalid JSON gets accepted by Atlas

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2328:


 Summary: Regression : Request body with invalid JSON gets accepted 
by Atlas
 Key: ATLAS-2328
 URL: https://issues.apache.org/jira/browse/ATLAS-2328
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Sharmadha Sainath
Priority: Minor


{code}
{
"tagFilters": null,
"classification": "*", 
"entityFilters": null,
"excludeDeletedEntities": true, 
"typeName": "hdfs_path",
"limit": 100,
"offset": 0,
"includeClassificationAttributes": false, 
"attributes": []
}}
{code}
s a wrong JSON with extra braces at the end.
Atlas accepts such JSONs and returns 20X code.

Options




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2327) Regression : Creating entity using V1 APIs with invalid values for attribute types succeeds

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2327:


 Summary: Regression : Creating entity using V1 APIs with invalid 
values for attribute types succeeds
 Key: ATLAS-2327
 URL: https://issues.apache.org/jira/browse/ATLAS-2327
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Sharmadha Sainath


Creating an entity with invalid values using V1 APIs succeeds with 201. 
Expected is 400 Bad Request. 
This doesn't happen with V2 APIs. 
Example :
1.Create type by posting JSON to /api/atlas/types
2.Create entity with random string value for float attribute by posting JSON to 
/api/atlas/entities
3. Request succeeds with 201.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2326) V1 API /api/atlas/entities/ throws 500 Internal exception

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2326:


 Summary: V1 API /api/atlas/entities/ throws 500 
Internal exception
 Key: ATLAS-2326
 URL: https://issues.apache.org/jira/browse/ATLAS-2326
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Sharmadha Sainath
 Attachments: invalid_guid_exception.txt

V1 API /api/atlas/entities/ throws 500 Internal server exception 
but with expected error message :
{code}
{
error: "Given instance guid invalidGUIDkqDFDFNyb2zs5 is invalid\/not found"
}
{code}
>From application logs, we could see that it throws the Atlas Base Exception 
>first , but later WebApplicationException is thrown.

V2 API /api/atlas/v2/entity/ throws 404.
Attached the complete stack trace.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2325) Creating entity containing attribute of type set with duplicate values

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2325:


 Summary: Creating entity containing attribute of type set with 
duplicate values
 Key: ATLAS-2325
 URL: https://issues.apache.org/jira/browse/ATLAS-2325
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Sharmadha Sainath


Creating an entity having an attribute of type set with duplicate values is 
expected to have only unique values. But duplicate values are retained.

Example : POSTing [1,2,3,1] stored as [1,2,3,1]. Expected is [1,2,3]

Repro :
1. POST the following JSON to /api/atlas/v2/types/typedefs
{code}
{
   "enumDefs":[

   ],
   "structDefs":[

   ],
   "classificationDefs":[

   ],
   "entityDefs":[
  {
 "superTypes":[

 ],
 "attributeDefs":[
{
   "name":"type_set",
   "typeName":"array",
   "isOptional":true,
   "cardinality":"SET",
   "valuesMinCount":-1,
   "valuesMaxCount":-1,
   "isUnique":false,
   "isIndexable":false
}

 ],
 "category":"ENTITY",
 "guid":"kcdnvdsvsdvidnvidsonvosid",
 "createdBy":"USER",
 "updatedBy":"USER",
 "createTime":12345,
 "updateTime":12345,
 "version":12345,
 "name":"simple_entity_type_set",
 "description":"simple_entity_type_set",
 "typeVersion":"0.1"
  }
   ]
}
{code}
2. Create entity of the type
{code}
   "referredEntities":{},
   "entity":{
  "typeName":"simple_entity_type_set",
  "attributes":{
 "type_set":["a","a","b"]
  },
  "guid":"-1",
  "status":"ACTIVE",
  "createdBy":"admin",
  "updatedBy":"admin",
  "createTime":1489585008165,
  "updateTime":1489585008801,
  "version":0,
  "classifications":[],
  "superTypes":[]
   }
}
{code}
3. entity is created with value for type_set as [a,a,b] instead of [a,b]

This is a regression in V1 APIs and seen in V2 APIs too.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2324) Regression : Entity update by PUT using V1 APIs throws 500 Internal server exception

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2324:


 Summary: Regression : Entity update by PUT using V1 APIs throws 
500 Internal server exception
 Key: ATLAS-2324
 URL: https://issues.apache.org/jira/browse/ATLAS-2324
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Sharmadha Sainath
 Attachments: NPE_during_PUT_update.txt, ent_v1, put_v1, type_v1

Steps to repro :
1. Create type using JSON type_v1 by POSTing to /api/atlas/types
2. Create entity for the type using JSON ent_v1 by POSTing to 
/api/atlas/entities
3. Update the entity using JSON put_v1 (guid to be changed in the JSON) by 
PUTting to /api/atlas/entities.

Update using PUT using V1 APIs throws NPE.
Attached the complete exception stack trace .

in V2 APIs , full entity update is done using POST and not PUT.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2320) classification "*" with query throws 500 Internal server exception.

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2320:


 Summary: classification "*" with query throws 500 Internal server 
exception.
 Key: ATLAS-2320
 URL: https://issues.apache.org/jira/browse/ATLAS-2320
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Sharmadha Sainath
 Attachments: query_and_classification_asterisk.txt

Following basic post query throws 500 internal server exception :
{code}
{
"query":"hive_table",
"classification":"*"

}
{code}
Exception:
{code}
Request to collection fulltext_index failed due to (400) 
org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error 
from server at http://172.27.58.128:8886/solr/fulltext_index: 
org.apache.solr.search.SyntaxError: Cannot parse 'sg5_t:(hive_table AND ())': 
Encountered " ")" ") "" at line 1, column 16.
Was expecting one of:
 ...
"+" ...
"-" ...
 ...
"(" ...
"*" ...
 ...
 ...
 ...
 ...
 ...
"[" ...
"{" ...
 ...
"filter(" ...
 ...
 ...
"*" ...
, retry? 0 (CloudSolrClient:903)
{code}

Attached the complete exception stack trace.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2319) UI : Deleting a tag which at 25+ position in the tag list in both Flat and Tree structure needs a refresh to remove the tag from the list.

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2319:


 Summary: UI : Deleting a tag which at 25+ position in the tag list 
in both Flat and Tree structure needs a refresh to remove the tag from the list.
 Key: ATLAS-2319
 URL: https://issues.apache.org/jira/browse/ATLAS-2319
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Reporter: Sharmadha Sainath


Created a tag tag26 which is the 26th tag in the list. On deleting tag26 from 
UI , tag26 is successfully deleted , but the entry is still present in the list 
in both Flat and Tree list structure.
After clicking refresh button for tags , tag26 is removed.
This doesn't happen with tags which are at position 25 or less.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2318) UI : Clicking on child tag twice , parent tag is selected

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2318:


 Summary: UI : Clicking on child tag twice , parent tag is selected
 Key: ATLAS-2318
 URL: https://issues.apache.org/jira/browse/ATLAS-2318
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Reporter: Sharmadha Sainath


1.Created tags super_tag and child_tag with supertag as super_tag.
2.Navigated to child_tag in Tree structure.
3.Clicked on child_tag. The child_tag was selected.
4.Clicked on child_tag again. Now its parent tag (super_tag) was selected.
5.Now any operation performed on super_tag is applied to child_tag (like 
deleting tag) which is confusing. 
6. But if super_tag is selected , operations are applied to super_tag only.

CC : [~kevalbhatt]




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2301) Concurrent modification exception when saving the search

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2301:


 Summary: Concurrent modification exception when saving the search 
 Key: ATLAS-2301
 URL: https://issues.apache.org/jira/browse/ATLAS-2301
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Sharmadha Sainath
Priority: Critical
 Attachments: ConModExceptionSaveSearch.txt

The Atlas instance has 626 types , 332 saved searches. (Search queries are 
large).

Post 332 saved searches ,when trying to save a query , ConcurrentModification 
exception is thrown with
{code}
audit record too long: entityType=__AtlasUserProfile, 
guid=8b9f8e79-30e5-4bfe-afca-cc3adc2a97c6, size=1048743; maxSize=1048576. 
entity attribute values not stored in audit (EntityAuditListener:156)
{code}

Attached the complete exception stack trace.

Other functionalities like creating tag  , entity ,hive hook functionalities , 
tag association , tag deletion , basic search , faceted basic search works well.

On other instance of Atlas , less types are created and 350+ saved searches are 
created (The save search attributes content differ in first instance and second 
instance. Former has more filters).





--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2294) Extra parameter "description" added when creating a type

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2294:


 Summary: Extra parameter "description" added when creating a type
 Key: ATLAS-2294
 URL: https://issues.apache.org/jira/browse/ATLAS-2294
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 1.0.0
Reporter: Sharmadha Sainath


When creating a type , there is inconsistency with "description" parameter of 
the attributes in the type definition.

For example :
1.Adding no description parameter in the POST adds “description” :”” in the 
created type.
2.Adding “description” : “null" in the POST , no description parameter is found 
in the created type.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2285) UI : Renamed saved search with date attribute.

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2285:


 Summary: UI : Renamed saved search with date attribute.
 Key: ATLAS-2285
 URL: https://issues.apache.org/jira/browse/ATLAS-2285
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 1.0.0
Reporter: Sharmadha Sainath
Priority: Critical
 Attachments: saved_search_with_date_renamed.mov

1. Fired basic search typename = hive_table , filter CreateTime = 08/02/2017 
9:10 PM and saved search as date_search
2. Clicked on the saved search "date_search" and verified the filters. filter 
CreateTime = 08/02/2017 9:10 PM is rightly set.
3. Clicked on the "date_search"  and renamed it to "date_search_renamed" 
without modifying the filters .
4.PUT REST call to update the search had the correct filter value.
5. Refreshed the page and clicked on the "date_search_renamed". Now , the date 
filter was modified to CreateTime =  01/01/1970 5:30 AM .
6. /api/atlas/v2/search/saved GET response had  08/02/2017 9:10 PM filter value 
for "date_search_renamed" but UI shows 01/01/1970 5:30 AM.

Attached the video recording.

CC : [~kevalbhatt] [~praik24mac]





--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2284) Import hive fails with "java.lang.NoClassDefFoundError: com/sun/jersey/multipart/BodyPart"

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2284:


 Summary: Import hive fails with "java.lang.NoClassDefFoundError: 
com/sun/jersey/multipart/BodyPart"
 Key: ATLAS-2284
 URL: https://issues.apache.org/jira/browse/ATLAS-2284
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 1.0.0
Reporter: Sharmadha Sainath
Priority: Blocker


Import hive fails with following error :
{code}
java.io.FileNotFoundException: 
/usr/hdp/current/atlas-server/logs/import-hive.log (No such file or directory)
at java.io.FileOutputStream.open0(Native Method)
at java.io.FileOutputStream.open(FileOutputStream.java:270)
at java.io.FileOutputStream.(FileOutputStream.java:213)
at java.io.FileOutputStream.(FileOutputStream.java:133)
at org.apache.log4j.FileAppender.setFile(FileAppender.java:294)
at 
org.apache.log4j.RollingFileAppender.setFile(RollingFileAppender.java:207)
at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:165)
at 
org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:307)
at 
org.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:295)
at 
org.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:176)
at 
org.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:191)
at 
org.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:523)
at 
org.apache.log4j.xml.DOMConfigurator.parseCategory(DOMConfigurator.java:436)
at org.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:1004)
at 
org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:872)
at 
org.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:778)
at 
org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:483)
at org.apache.log4j.LogManager.(LogManager.java:127)
at 
org.slf4j.impl.Log4jLoggerFactory.getLogger(Log4jLoggerFactory.java:64)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:281)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:301)
at 
org.apache.atlas.hive.bridge.HiveMetaStoreBridge.(HiveMetaStoreBridge.java:97)
Exception in thread "main" java.lang.NoClassDefFoundError: 
com/sun/jersey/multipart/BodyPart
at 
org.apache.atlas.hive.bridge.HiveMetaStoreBridge.main(HiveMetaStoreBridge.java:634)
Caused by: java.lang.ClassNotFoundException: com.sun.jersey.multipart.BodyPart
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 1 more
Failed to import Hive Data Model!!
{code}




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2282) Saved favorite search appears only on refresh after creation when there are many favorite search .

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2282:


 Summary: Saved favorite search appears only on refresh after 
creation when there are many favorite search .
 Key: ATLAS-2282
 URL: https://issues.apache.org/jira/browse/ATLAS-2282
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 1.0.0
Reporter: Sharmadha Sainath


1. Created 24 basic favorite search .
2. Created 25th basic favorite search. Popup notification displayed that the 
search is successfully created.Without any refresh , 25th favorite search 
appeared in the favorite search list.
3. Created 26th basic favorite search. Popup notification displayed that the 
search is successfully created.
4.But the favorite search list didn't display the 26th basic favorite search 
but only the ld 25 searches,
5.On page refresh , the 26th favorite search was displayed.

Thus , when more than 25 Basic/Advanced favorite searches (Basic and Advanced 
separately 25) are created , the newly created favorite search is displayed 
only on page refresh.

CC : [~kevalbhatt]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2282) Saved favorite search appears only on refresh after creation when there are 25+ favorite searches .

[Sharmadha Sainath (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sharmadha Sainath updated ATLAS-2282:
-
Summary: Saved favorite search appears only on refresh after creation when 
there are 25+ favorite searches .  (was: Saved favorite search appears only on 
refresh after creation when there are many favorite search .)

> Saved favorite search appears only on refresh after creation when there are 
> 25+ favorite searches .
> ---
>
> Key: ATLAS-2282
> URL: https://issues.apache.org/jira/browse/ATLAS-2282
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 1.0.0
>    Reporter: Sharmadha Sainath
>
> 1. Created 24 basic favorite search .
> 2. Created 25th basic favorite search. Popup notification displayed that the 
> search is successfully created.Without any refresh , 25th favorite search 
> appeared in the favorite search list.
> 3. Created 26th basic favorite search. Popup notification displayed that the 
> search is successfully created.
> 4.But the favorite search list didn't display the 26th basic favorite search 
> but only the ld 25 searches,
> 5.On page refresh , the 26th favorite search was displayed.
> Thus , when more than 25 Basic/Advanced favorite searches (Basic and Advanced 
> separately 25) are created , the newly created favorite search is displayed 
> only on page refresh.
> CC : [~kevalbhatt]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2281) Saving Tag/Type attribute filter queries with null/not null filters.

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2281:


 Summary: Saving Tag/Type attribute filter queries with null/not 
null filters.
 Key: ATLAS-2281
 URL: https://issues.apache.org/jira/browse/ATLAS-2281
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Reporter: Sharmadha Sainath
Priority: Critical


1. Fired Basic Search 
   typename = hive_table , 
   filter : "Name" condition : "is not null".
2. Saved the query.
3. Executed the saved query which fetched all the correct tables.
4. Now to modify the search , clicked on the saved search and clicked on the 
type filter. 
5. The Attribute filter window didn't load.
 " Error: Undefined operator "notNull" " was thrown in browser's console logs.

Same happens when clicking the saved search containing "is null" filter. 
"Error: Undefined operator "isNull" " is thrown in console.log. But the saved 
search can be executed without any issues. 

Also seen in tag attributes filters.

This is not seen with other filters for all data types.
CC : [~kevalbhatt] 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2277) Search using entity and trait attributes - excludeDeletedEntities parameter doesn't take effect when classification is "*"

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2277:


 Summary: Search using entity and trait attributes - 
excludeDeletedEntities parameter doesn't take effect when classification is "*"
 Key: ATLAS-2277
 URL: https://issues.apache.org/jira/browse/ATLAS-2277
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 1.0.0
Reporter: Sharmadha Sainath


POST request body to /api/atlas/v2/search/basic :
{code}
{
"excludeDeletedEntities":true,
"includeClassificationAttributes": true,
"entityFilters":null,
"tagFilters":null,
"attributes":[],
"limit":100,
"offset":0,
"classification":"*"
}
{code}
though excludeDeletedEntities is True , when classification is "*" , the result 
has the DELETED entities too.
When any tag name is provided and excludeDeletedEntities when set to True , 
response doesn't have DELETED entities.
Hence incorrect results only when classification is "*".

CC : [~sarath.ku...@gmail.com] [~nixonrodrigues]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2274) Search using entity and trait attributes - typename and "*" in classificationName throws Invalid condition exception

[Sharmadha Sainath (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sharmadha Sainath updated ATLAS-2274:
-
Attachment: Atlas_asterisk_in_classification_and type_name_exception.txt

> Search using entity and trait attributes - typename and "*" in 
> classificationName throws Invalid condition exception
> 
>
> Key: ATLAS-2274
> URL: https://issues.apache.org/jira/browse/ATLAS-2274
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
> Attachments: Atlas_asterisk_in_classification_and 
> type_name_exception.txt
>
>
> Following is the POST request body to /api/atlas/v2/search/basic
> {code}
> {
> "excludeDeletedEntities":true,
> "entityFilters":null,
> "tagFilters":null,
> "attributes":[],
> "limit":25,
> "offset":0,
> "typeName":"hive_table",
> "classification":"*"
> }
> {code}
> When any typeName is provided , Atlas throws 500 Internal server 
> exception.Attached the exception stack trace.
> When typeName parameter is removed ,or is given "null" value , response is 
> 200 OK.
> When a tag name is provided instead of "*" , and typeName is given ,no issues 
> are seen.
> Hence , issue with * in classificationName and typeName provided together.
> CC : [~sarath.ku...@gmail.com]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-1116) Performance monitoring of backend methods in API requests

[Sharmadha Sainath (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sharmadha Sainath updated ATLAS-1116:
-
Attachment: (was: Atlas_asterisk_in_classification_and 
type_name_exception.txt)

> Performance monitoring of backend methods in API requests
> -
>
> Key: ATLAS-1116
> URL: https://issues.apache.org/jira/browse/ATLAS-1116
> Project: Atlas
>  Issue Type: Bug
>Reporter: Vimal Sharma
>Assignee: Shwetha G S
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1116-v2.patch, ATLAS-1116-v3.patch, 
> ATLAS-1116.patch
>
>
> Time taken by methods used in API calls for add/update/delete entities and 
> traits need to be monitored for performance



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2274) Search using entity and trait attributes - typename and "*" in classificationName throws Invalid condition exception

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2274:


 Summary: Search using entity and trait attributes - typename and 
"*" in classificationName throws Invalid condition exception
 Key: ATLAS-2274
 URL: https://issues.apache.org/jira/browse/ATLAS-2274
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 1.0.0
Reporter: Sharmadha Sainath


Following is the POST request body to /api/atlas/v2/search/basic
{code}
{
"excludeDeletedEntities":true,
"entityFilters":null,
"tagFilters":null,
"attributes":[],
"limit":25,
"offset":0,
"typeName":"hive_table",
"classification":"*"
}
{code}
When any typeName is provided , Atlas throws 500 Internal server 
exception.Attached the exception stack trace.

When typeName parameter is removed ,or is given "null" value , response is 200 
OK.

When a tag name is provided instead of "*" , and typeName is given ,no issues 
are seen.

Hence , issue with * in classificationName and typeName provided together.

CC : [~sarath.ku...@gmail.com]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-1116) Performance monitoring of backend methods in API requests

[Sharmadha Sainath (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sharmadha Sainath updated ATLAS-1116:
-
Attachment: Atlas_asterisk_in_classification_and type_name_exception.txt

> Performance monitoring of backend methods in API requests
> -
>
> Key: ATLAS-1116
> URL: https://issues.apache.org/jira/browse/ATLAS-1116
> Project: Atlas
>  Issue Type: Bug
>Reporter: Vimal Sharma
>Assignee: Shwetha G S
> Fix For: 0.8-incubating
>
> Attachments: ATLAS-1116-v2.patch, ATLAS-1116-v3.patch, 
> ATLAS-1116.patch, Atlas_asterisk_in_classification_and type_name_exception.txt
>
>
> Time taken by methods used in API calls for add/update/delete entities and 
> traits need to be monitored for performance



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2268) UI : Faceted Search : Filters are not removed when not cleared between searches.

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2268:


 Summary: UI : Faceted Search : Filters are not removed when not 
cleared between searches.
 Key: ATLAS-2268
 URL: https://issues.apache.org/jira/browse/ATLAS-2268
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Reporter: Sharmadha Sainath


1. In Basic search , fire search type = hive_table , filter = name contains 
hive. Apply Search
2.Fire another search ,type = kafka_topic (without clicking clear button).
3.Now fire search  again : type = hive_table without any filters (without 
clicking clear button). 

Though only type name is searched , last filter "name contains hive" is applied 
still.

Expected that the type search would be cleared completely when other type 
search is made. 




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2257) hive_column type definition changes for position and table attributes when updated

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2257:


 Summary: hive_column type definition changes for position and 
table attributes when updated
 Key: ATLAS-2257
 URL: https://issues.apache.org/jira/browse/ATLAS-2257
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Sharmadha Sainath


On a fresh instance of Atlas , following is the type definition of hive_column :
{code}
{  
   category:"ENTITY",
   guid:"076ceac2-5c0d-400f-8f89-ab455125191d",
   createdBy:"atlas",
   updatedBy:"atlas",
   createTime:1510294855527,
   updateTime:1510294855527,
   version:1,
   name:"hive_column",
   description:"hive_column",
   typeVersion:"1.3",
   options:{  
  schemaAttributes:"["  name",
  "description",
  "owner",
  "type",
  "comment",
  "position"
   ]   " 
}, 
attributeDefs: [ 
{ 
name: "   type",
   typeName:"string",
   isOptional:false,
   cardinality:"SINGLE",
   valuesMinCount:1,
   valuesMaxCount:1,
   isUnique:false,
   isIndexable:true
},
{  
   name:"comment",
   typeName:"string",
   isOptional:true,
   cardinality:"SINGLE",
   valuesMinCount:0,
   valuesMaxCount:1,
   isUnique:false,
   isIndexable:false
},
{  
   name:"position",
   typeName:"int",
   isOptional:true,
   cardinality:"SINGLE",
   valuesMinCount:-1,
   valuesMaxCount:-1,
   isUnique:false,
   isIndexable:false
},
{  
   name:"table",
   typeName:"hive_table",
   isOptional:true,
   cardinality:"SINGLE",
   valuesMinCount:-1,
   valuesMaxCount:-1,
   isUnique:false,
   isIndexable:false
}
],
superTypes:[  
"DataSet"
]
}
{code}

fired an update PUT request to update the hive_column type definition without 
changing the definition . Update is successful. After update , following is the 
type definition of hive_column :
{code}
{  
   category:"ENTITY",
   guid:"076ceac2-5c0d-400f-8f89-ab455125191d",
   createdBy:"atlas",
   updatedBy:"admin",
   createTime:1510294855527,
   updateTime:1510294918066,
   version:5,
   name:"hive_column",
   description:"hive_column",
   typeVersion:"1.3",
   options:{  
  schemaAttributes:"["  name",
  "description",
  "owner",
  "type",
  "comment",
  "position"
   ]   " 
}, 
attributeDefs: [ 
{ 
name: "   type",
   typeName:"string",
   isOptional:false,
   cardinality:"SINGLE",
   valuesMinCount:1,
   valuesMaxCount:1,
   isUnique:false,
   isIndexable:true
},
{  
   name:"comment",
   typeName:"string",
   isOptional:true,
   cardinality:"SINGLE",
   valuesMinCount:0,
   valuesMaxCount:1,
   isUnique:false,
   isIndexable:false
},
{  
   name:"position",
   typeName:"int",
   isOptional:true,
   cardinality:"SINGLE",
   valuesMinCount:0,
   valuesMaxCount:1,
   isUnique:false,
   isIndexable:false
},
{  
   name:"table",
   typeName:"hive_table",
   isOptional:true,
   cardinality:"SINGLE",
   valuesMinCount:0,
   valuesMaxCount:1,
   isUnique:false,
   isIndexable:false
}
],
superTypes:[  
"DataSet"
]
}
{code}

valuesMinCount and valuesMaxCount values differ for "position" and "table" 
attributes post update.

Thanks [~ayubkhan] for helping to reproduce the issue .

This issue is not seen in other data types in hive model.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2237) Exponential values for tag attribute values for float, double are stored differently.

[Sharmadha Sainath (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sharmadha Sainath updated ATLAS-2237:
-
Description: 
On providing 
1. 3.4e+10 to a float tag attribute value , it is stored as 3399000 .
2. 34e+10 to a float tag attribute value , it is stored as 34014000.

But 3.4e+9 for a float attribute is stored as 34 correctly.

The POST body is sent with the exponential values but stored differently.



  was:
On providing 
1. 3.4e+10 to a float tag attribute value , it is stored as 3399000 .
2. 34e+10 to a float tag attribute value , it is stored as 34014000.

The POST body is sent with the exponential values but stored differently.




> Exponential values for tag attribute values for float, double are stored 
> differently.
> -
>
> Key: ATLAS-2237
> URL: https://issues.apache.org/jira/browse/ATLAS-2237
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>        Reporter: Sharmadha Sainath
>
> On providing 
> 1. 3.4e+10 to a float tag attribute value , it is stored as 3399000 .
> 2. 34e+10 to a float tag attribute value , it is stored as 34014000.
> But 3.4e+9 for a float attribute is stored as 34 correctly.
> The POST body is sent with the exponential values but stored differently.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2237) Exponential values for tag attribute values for float, double are stored differently.

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2237:


 Summary: Exponential values for tag attribute values for float, 
double are stored differently.
 Key: ATLAS-2237
 URL: https://issues.apache.org/jira/browse/ATLAS-2237
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Sharmadha Sainath


On providing 
1. 3.4e+10 to a float tag attribute value , it is stored as 3399000 .
2. 34e+10 to a float tag attribute value , it is stored as 34014000.

The POST body is sent with the exponential values but stored differently.





--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2231) UI: Unable to provide f,d notation for float and double tag attribute values respectively.

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2231:


 Summary: UI: Unable to provide f,d notation for float and double 
tag attribute values respectively.
 Key: ATLAS-2231
 URL: https://issues.apache.org/jira/browse/ATLAS-2231
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 1.0.0
Reporter: Sharmadha Sainath


Input box for float and double doesn't accept f and d notations respectively . 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2222) UI: Search using entity and trait attributes - "," in string attribute filter throws 400 Bad request

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-:


 Summary: UI: Search using entity and trait attributes - "," in 
string attribute filter throws 400 Bad request
 Key: ATLAS-
 URL: https://issues.apache.org/jira/browse/ATLAS-
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Reporter: Sharmadha Sainath
Priority: Critical


In UI , When string attribute filter contains comma , it is taken as separate 
attribute filter.
For example basic search : hive_table , filter : description = a , b 
POST request body :
{code}
{  
   "excludeDeletedEntities":true,
   "entityFilters":{  
  "condition":"AND",
  "criterion":[  
 {  
"attributeName":"description",
"operator":"eq",
"attributeValue":"a"
 },
 {  
"attributeName":"b",
"operator":"string"
 }
  ]
   },
   "tagFilters":null,
   "attributes":[  

   ],
   "limit":25,
   "offset":0,
   "typeName":"hive_table",
   "classification":null
}

{code}

The search throws 400 Bad request with error notification "Attribute b not 
found for type hive_table".

This is seen only in UI ,as when search is fired with attributeValue given as 
"a,b" using REST API , fetches correct results.
{code}
{  
   "excludeDeletedEntities":true,
   "entityFilters":{  
  "condition":"AND",
  "criterion":[  
 {  
"attributeName":"description",
"operator":"eq",
"attributeValue":"a,b"
 }
  ]
   },
   "tagFilters":null,
   "attributes":[  

   ],
   "limit":25,
   "offset":0,
   "typeName":"hdfs_path",
   "classification":null
}
{code}

CC : [~kevalbhatt] [~madhan.neethiraj] [~apoorvnaik]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2219) UI Regression : Unable to provide exponential values for tag attribute values in UI.

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2219:


 Summary: UI Regression : Unable to provide exponential values for 
tag attribute values in UI.
 Key: ATLAS-2219
 URL: https://issues.apache.org/jira/browse/ATLAS-2219
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Reporter: Sharmadha Sainath
Assignee: Keval Bhatt
Priority: Critical


For tag attributes of data type double , float etc, the corresponding text box 
is not accepting 'E' character for providing exponential values.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2214) Search using trait attributes "!=" and "is not null" together and in order in string,boolean tag attribute filter comparison

[Sharmadha Sainath (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sharmadha Sainath updated ATLAS-2214:
-
Summary: Search using trait attributes  "!=" and "is not null"  together 
and in order in string,boolean tag attribute filter comparison  (was: Search 
using entity and trait attributes  "!=" and "is not null"  together and in 
order in string,boolean tag filter attribute comparison)

> Search using trait attributes  "!=" and "is not null"  together and in order 
> in string,boolean tag attribute filter comparison
> --
>
> Key: ATLAS-2214
> URL: https://issues.apache.org/jira/browse/ATLAS-2214
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Sharmadha Sainath
>Priority: Critical
> Attachments: not_equals_and_not_null_tag_filter_exception.txt
>
>
> 1. Created a tag tag1 with attributes of all data types.
> 2. Fired a basic search with tag1 and following tag filters of type string:
> a)string  != rand
> b)string is not null
> POST body 
> {code}
> {  
>"excludeDeletedEntities":true,
>"entityFilters":null,
>"tagFilters":{  
>   "condition":"AND",
>   "criterion":[  
>  {  
> "attributeName":"string",
> "operator":"neq",
> "attributeValue":"rand"
>  },
>  {  
> "attributeName":"string",
> "operator":"not_null",
> "attributeValue":""
>  }
>   ]
>},
>"attributes":null,
>"limit":25,
>"offset":0,
>"typeName":null,
>"classification":"tag1"
> }
> {code}
> The search threw 500 Internal server exception. Attached the stack trace .
> Note :
> 1)This exception is not seen if order is reversed (i.e) , in the order
>a)string is not null
>b)string  != rand 
> In this order , correct results are fetched.
> 2)For string and boolean data types , this exception is seen. This was not 
> seen with int , float, short , double , date , enum .
>
> 3)Also , this issue is seen only in tag attribute filters and not in type 
> attribute filters.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2214) Search using entity and trait attributes "!=" and "is not null" together and in order in string,boolean tag filter attribute comparison

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2214:


 Summary: Search using entity and trait attributes  "!=" and "is 
not null"  together and in order in string,boolean tag filter attribute 
comparison
 Key: ATLAS-2214
 URL: https://issues.apache.org/jira/browse/ATLAS-2214
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
    Reporter: Sharmadha Sainath
Priority: Critical
 Attachments: not_equals_and_not_null_tag_filter_exception.txt

1. Created a tag tag1 with attributes of all data types.
2. Fired a basic search with tag1 and following tag filters of type string:
a)string  != rand
b)string is not null
POST body 
{code}
{  
   "excludeDeletedEntities":true,
   "entityFilters":null,
   "tagFilters":{  
  "condition":"AND",
  "criterion":[  
 {  
"attributeName":"string",
"operator":"neq",
"attributeValue":"rand"
 },
 {  
"attributeName":"string",
"operator":"not_null",
"attributeValue":""
 }
  ]
   },
   "attributes":null,
   "limit":25,
   "offset":0,
   "typeName":null,
   "classification":"tag1"
}
{code}

The search threw 500 Internal server exception. Attached the stack trace .

Note :
1)This exception is not seen if order is reversed (i.e) , in the order
   a)string is not null
   b)string  != rand 
In this order , correct results are fetched.

2)For string and boolean data types , this exception is seen. This was not seen 
with int , float, short , double , date , enum .
   
3)Also , this issue is seen only in tag attribute filters and not in type 
attribute filters.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2212) Regression : Unable to provide negative values directly for tag attributes of data type int.

[Sharmadha Sainath (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sharmadha Sainath updated ATLAS-2212:
-
Summary: Regression : Unable to provide negative values directly for tag 
attributes of data type int.  (was: Unable to provide negative values directly 
for tag attributes of data type int.)

> Regression : Unable to provide negative values directly for tag attributes of 
> data type int.
> 
>
> Key: ATLAS-2212
> URL: https://issues.apache.org/jira/browse/ATLAS-2212
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 1.0.0
>    Reporter: Sharmadha Sainath
>Assignee: pratik pandey
>
> 1. Created a tag with int attribute.
> 2. Tried to associate the tag to an entity with tag attribute value as -1. 
> Unable to provide negative value.(i.e) minus sign is not accepted. 
> 3. Able to set negative value for int if value is changed using Up and Down 
> Arrow .
> 4. This behavior is not observed for short,byte,float,double attribute 
> values. Able to provide negative value directly for datatypes other than int.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2212) Unable to provide negative values directly for tag attributes of data type int.

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2212:


 Summary: Unable to provide negative values directly for tag 
attributes of data type int.
 Key: ATLAS-2212
 URL: https://issues.apache.org/jira/browse/ATLAS-2212
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 1.0.0
Reporter: Sharmadha Sainath


1. Created a tag with int attribute.
2. Tried to associate the tag to an entity with tag attribute value as -1. 
Unable to provide negative value.(i.e) minus sign is not accepted. 
3. Able to set negative value for int if value is changed using Up and Down 
Arrow .
4. This behavior is not observed for short,byte,float,double attribute values. 
Able to provide negative value directly for datatypes other than int.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (ATLAS-2212) Unable to provide negative values directly for tag attributes of data type int.

[Sharmadha Sainath (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sharmadha Sainath reassigned ATLAS-2212:


Assignee: Keval Bhatt

> Unable to provide negative values directly for tag attributes of data type 
> int.
> ---
>
> Key: ATLAS-2212
> URL: https://issues.apache.org/jira/browse/ATLAS-2212
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 1.0.0
>    Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>
> 1. Created a tag with int attribute.
> 2. Tried to associate the tag to an entity with tag attribute value as -1. 
> Unable to provide negative value.(i.e) minus sign is not accepted. 
> 3. Able to set negative value for int if value is changed using Up and Down 
> Arrow .
> 4. This behavior is not observed for short,byte,float,double attribute 
> values. Able to provide negative value directly for datatypes other than int.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2208) Include historical entities in Schema tab checked by default for DELETED tables

[Sharmadha Sainath (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sharmadha Sainath updated ATLAS-2208:
-
Attachment: SchemaTab of Deleted table.png

> Include historical entities in Schema tab checked by default for DELETED 
> tables
> ---
>
> Key: ATLAS-2208
> URL: https://issues.apache.org/jira/browse/ATLAS-2208
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>        Reporter: Sharmadha Sainath
> Attachments: SchemaTab of Deleted table.png
>
>
> 1. Created and dropped hive_table table1 with columns col1 , col2
> 2. Fired basic search hive_table and checked "Show historical entities" which 
> listed the DELETED table.
> 3. Clicked on the DELETED table and clicked on the Schema Tab for the table.
> 4. Include historical entities was checked by default (I suppose it is 
> displaying the Show historical entities value checked in the Search page ).
> 5. Though it is checked , no columns were listed.
> 6. Toggled the value twice. Now Include historical entities is checked again 
> , and now DELETED columns were listed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2208) Include historical entities in Schema tab checked by default for DELETED tables

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2208:


 Summary: Include historical entities in Schema tab checked by 
default for DELETED tables
 Key: ATLAS-2208
 URL: https://issues.apache.org/jira/browse/ATLAS-2208
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Reporter: Sharmadha Sainath


1. Created and dropped hive_table table1 with columns col1 , col2
2. Fired basic search hive_table and checked "Show historical entities" which 
listed the DELETED table.
3. Clicked on the DELETED table and clicked on the Schema Tab for the table.
4. Include historical entities was checked by default (I suppose it is 
displaying the Show historical entities value checked in the Search page ).
5. Though it is checked , no columns were listed.
6. Toggled the value twice. Now Include historical entities is checked again , 
and now DELETED columns were listed.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2203) Regression Atlas Knox Proxy : j_spring_security_check not found during login

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2203:


 Summary: Regression Atlas Knox Proxy  : j_spring_security_check 
not found during login
 Key: ATLAS-2203
 URL: https://issues.apache.org/jira/browse/ATLAS-2203
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Reporter: Sharmadha Sainath
Priority: Blocker


1.Enabled knox proxy for Atlas.
2. On accessing https://knox_gateway:8443/gateway/ui/atlas/login.jsp , 404 is 
thrown with the following  :
{code}
POST
404 Not Found
https://knox_gateway:8443/gateway/j_spring_security_check
{code}
and 
{code}
GET
404 Not Found
https://knox_gateway:8443/favicon.ico
{code}

which should ideally go to 
{code}
https://knox_gateway:8443/gateway/ui/atlas/j_spring_security_check
{code}



CC : [~nixonrodrigues]




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2171) Error in parsing API when accessing Atlas via knox proxy without "/" at the end

[Sharmadha Sainath (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sharmadha Sainath updated ATLAS-2171:
-
Summary: Error in parsing API when accessing Atlas via knox proxy without 
"/" at the end  (was: Accessing atlas via knox proxy without "/" at the end 
logs in as UNKNOWN user)

> Error in parsing API when accessing Atlas via knox proxy without "/" at the 
> end
> ---
>
> Key: ATLAS-2171
> URL: https://issues.apache.org/jira/browse/ATLAS-2171
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>    Affects Versions: 1.0.0
>Reporter: Sharmadha Sainath
>Assignee: Keval Bhatt
>Priority: Critical
> Attachments: ATLAS-2171.patch
>
>
> 1. Enabled knox proxy for atlas.
> 2.Accessed Atlas UI via proxy using https://knox_gateway:8443/gateway/ui/atlas
> 3. Provided admin username and password and logged into Atlas
> 4. Now, opened another tab in browser with URL
> {code}
> https://knox_gateway:8443/gateway/ui/atlas
> {code}
> I was not logged in as admin but as an unknown user.No read/write operations 
> were allowed. Found the following application logs :
> {code}
> 2017-09-26 05:39:31,467 ERROR - [pool-2-thread-9:] ~ Unable to find Atlas 
> Resource corresponding to :
> Setting UNKNOWN (AtlasAuthorizationUtils:143)
> {code}
> If the URL is accessed with "/" at the end , logs in as admin user and all 
> operations work fine.
> Example :
> {code}
> https://knox_gateway:8443/gateway/ui/atlas/
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2182) UI : Web elements are hidden when zoomed in

[Sharmadha Sainath (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-2182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sharmadha Sainath updated ATLAS-2182:
-
Description: 
Opened Atlas UI on Chrome . On zooming at 150% , most of the elements on Search 
tab are not visible.
Attached the screenshot. At 200 % , complete left Search pane is not visible.

  was:
Opened Atlas UI on Chrome . On zooming at 150% , few elements on Search tab are 
not visible.
Attached the screenshot. At 200 % , complete left Search pane is not visible.


> UI : Web elements are hidden when zoomed in 
> 
>
> Key: ATLAS-2182
> URL: https://issues.apache.org/jira/browse/ATLAS-2182
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 1.0.0
>        Reporter: Sharmadha Sainath
> Attachments: Atlas_UI_zoomed_at_150%.png
>
>
> Opened Atlas UI on Chrome . On zooming at 150% , most of the elements on 
> Search tab are not visible.
> Attached the screenshot. At 200 % , complete left Search pane is not visible.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2182) UI : Web elements are hidden when zoomed in

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2182:


 Summary: UI : Web elements are hidden when zoomed in 
 Key: ATLAS-2182
 URL: https://issues.apache.org/jira/browse/ATLAS-2182
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 1.0.0
Reporter: Sharmadha Sainath
 Attachments: Atlas_UI_zoomed_at_150%.png

Opened Atlas UI on Chrome . On zooming at 150% , few elements on Search tab are 
not visible.
Attached the screenshot. At 200 % , complete left Search pane is not visible.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (ATLAS-2180) Regression : Hive hook is broken

[Sharmadha Sainath (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182280#comment-16182280
 ] 

Sharmadha Sainath edited comment on ATLAS-2180 at 9/27/17 9:51 AM:
---

Falcon,Storm hooks are working well. Problem is with hive hook only. (Didn't 
test Sqoop hook as there is an already existing issue with Sqoop hive 
integration itself)


was (Author: ssainath):
Falcon,Storm hooks are working well. Problem is with hive hook only. (Didn't 
test Sqoop hook as there is an already existing issue with Sqoop component 
itself)

> Regression : Hive hook is broken
> 
>
> Key: ATLAS-2180
> URL: https://issues.apache.org/jira/browse/ATLAS-2180
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: 1.0.0
>        Reporter: Sharmadha Sainath
>Priority: Blocker
>
> Hive table creation succeeded but while invoking Atlas hook , following error 
> message seen in hive logs :
> {code}
> 2017-09-27 06:29:26,084 INFO  [Atlas Logger 0]: hook.HiveHook 
> (HiveHook.java:collect(244)) - Entered Atlas hook for hook type 
> POST_EXEC_HOOK, operation CREATETABLE , user null as hive
> 2017-09-27 06:29:26,084 INFO  [HiveServer2-Background-Pool: Thread-236]: 
> log.PerfLogger (PerfLogger.java:PerfLogBegin(149)) -  method=releaseLocks from=org.apache.hadoop.hive.ql.Driver>
> 2017-09-27 06:29:26,084 INFO  [HiveServer2-Background-Pool: Thread-236]: 
> log.PerfLogger (PerfLogger.java:PerfLogEnd(177)) -  method=releaseLocks start=1506493766084 end=1506493766084 duration=0 
> from=org.apache.hadoop.hive.ql.Driver>
> 2017-09-27 06:29:26,085 INFO  [HiveServer2-Background-Pool: Thread-236]: 
> log.PerfLogger (PerfLogger.java:PerfLogEnd(177)) -  method=Driver.run start=1506493763780 end=1506493766085 duration=2305 
> from=org.apache.hadoop.hive.ql.Driver>
> 2017-09-27 06:29:26,087 ERROR [Atlas Logger 0]: hook.HiveHook 
> (HiveHook.java:run(205)) - Atlas hook failed due to error 
> java.lang.NoClassDefFoundError: org/apache/atlas/AtlasServiceException
>   at org.apache.atlas.hive.hook.HiveHook.collect(HiveHook.java:246)
>   at org.apache.atlas.hive.hook.HiveHook.access$200(HiveHook.java:83)
>   at org.apache.atlas.hive.hook.HiveHook$2$1.run(HiveHook.java:198)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:422)
>   at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1866)
>   at org.apache.atlas.hive.hook.HiveHook$2.run(HiveHook.java:195)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.atlas.AtlasServiceException
>   at java.lang.ClassLoader.findClass(ClassLoader.java:530)
>   at 
> org.apache.atlas.plugin.classloader.AtlasPluginClassLoader$MyClassLoader.findClass(AtlasPluginClassLoader.java:328)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at 
> org.apache.atlas.plugin.classloader.AtlasPluginClassLoader.loadClass(AtlasPluginClassLoader.java:136)
>   ... 12 more
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ATLAS-2180) Regression : Hive hook is broken

[Sharmadha Sainath (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16182280#comment-16182280
 ] 

Sharmadha Sainath commented on ATLAS-2180:
--

Falcon,Storm hooks are working well. Problem is with hive hook only. (Didn't 
test Sqoop hook as there is an already existing issue with Sqoop component 
itself)

> Regression : Hive hook is broken
> 
>
> Key: ATLAS-2180
> URL: https://issues.apache.org/jira/browse/ATLAS-2180
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: 1.0.0
>        Reporter: Sharmadha Sainath
>Priority: Blocker
>
> Hive table creation succeeded but while invoking Atlas hook , following error 
> message seen in hive logs :
> {code}
> 2017-09-27 06:29:26,084 INFO  [Atlas Logger 0]: hook.HiveHook 
> (HiveHook.java:collect(244)) - Entered Atlas hook for hook type 
> POST_EXEC_HOOK, operation CREATETABLE , user null as hive
> 2017-09-27 06:29:26,084 INFO  [HiveServer2-Background-Pool: Thread-236]: 
> log.PerfLogger (PerfLogger.java:PerfLogBegin(149)) -  method=releaseLocks from=org.apache.hadoop.hive.ql.Driver>
> 2017-09-27 06:29:26,084 INFO  [HiveServer2-Background-Pool: Thread-236]: 
> log.PerfLogger (PerfLogger.java:PerfLogEnd(177)) -  method=releaseLocks start=1506493766084 end=1506493766084 duration=0 
> from=org.apache.hadoop.hive.ql.Driver>
> 2017-09-27 06:29:26,085 INFO  [HiveServer2-Background-Pool: Thread-236]: 
> log.PerfLogger (PerfLogger.java:PerfLogEnd(177)) -  method=Driver.run start=1506493763780 end=1506493766085 duration=2305 
> from=org.apache.hadoop.hive.ql.Driver>
> 2017-09-27 06:29:26,087 ERROR [Atlas Logger 0]: hook.HiveHook 
> (HiveHook.java:run(205)) - Atlas hook failed due to error 
> java.lang.NoClassDefFoundError: org/apache/atlas/AtlasServiceException
>   at org.apache.atlas.hive.hook.HiveHook.collect(HiveHook.java:246)
>   at org.apache.atlas.hive.hook.HiveHook.access$200(HiveHook.java:83)
>   at org.apache.atlas.hive.hook.HiveHook$2$1.run(HiveHook.java:198)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at javax.security.auth.Subject.doAs(Subject.java:422)
>   at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1866)
>   at org.apache.atlas.hive.hook.HiveHook$2.run(HiveHook.java:195)
>   at 
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.atlas.AtlasServiceException
>   at java.lang.ClassLoader.findClass(ClassLoader.java:530)
>   at 
> org.apache.atlas.plugin.classloader.AtlasPluginClassLoader$MyClassLoader.findClass(AtlasPluginClassLoader.java:328)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at 
> org.apache.atlas.plugin.classloader.AtlasPluginClassLoader.loadClass(AtlasPluginClassLoader.java:136)
>   ... 12 more
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2180) Regression : Hive hook is broken

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2180:


 Summary: Regression : Hive hook is broken
 Key: ATLAS-2180
 URL: https://issues.apache.org/jira/browse/ATLAS-2180
 Project: Atlas
  Issue Type: Bug
  Components: atlas-intg
Affects Versions: 1.0.0
Reporter: Sharmadha Sainath
Priority: Blocker


Hive table creation succeeded but while invoking Atlas hook , following error 
message seen in hive logs :

{code}
2017-09-27 06:29:26,084 INFO  [Atlas Logger 0]: hook.HiveHook 
(HiveHook.java:collect(244)) - Entered Atlas hook for hook type POST_EXEC_HOOK, 
operation CREATETABLE , user null as hive
2017-09-27 06:29:26,084 INFO  [HiveServer2-Background-Pool: Thread-236]: 
log.PerfLogger (PerfLogger.java:PerfLogBegin(149)) - 
2017-09-27 06:29:26,084 INFO  [HiveServer2-Background-Pool: Thread-236]: 
log.PerfLogger (PerfLogger.java:PerfLogEnd(177)) - 
2017-09-27 06:29:26,085 INFO  [HiveServer2-Background-Pool: Thread-236]: 
log.PerfLogger (PerfLogger.java:PerfLogEnd(177)) - 
2017-09-27 06:29:26,087 ERROR [Atlas Logger 0]: hook.HiveHook 
(HiveHook.java:run(205)) - Atlas hook failed due to error 
java.lang.NoClassDefFoundError: org/apache/atlas/AtlasServiceException
at org.apache.atlas.hive.hook.HiveHook.collect(HiveHook.java:246)
at org.apache.atlas.hive.hook.HiveHook.access$200(HiveHook.java:83)
at org.apache.atlas.hive.hook.HiveHook$2$1.run(HiveHook.java:198)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1866)
at org.apache.atlas.hive.hook.HiveHook$2.run(HiveHook.java:195)
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.ClassNotFoundException: 
org.apache.atlas.AtlasServiceException
at java.lang.ClassLoader.findClass(ClassLoader.java:530)
at 
org.apache.atlas.plugin.classloader.AtlasPluginClassLoader$MyClassLoader.findClass(AtlasPluginClassLoader.java:328)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at 
org.apache.atlas.plugin.classloader.AtlasPluginClassLoader.loadClass(AtlasPluginClassLoader.java:136)
... 12 more
{code}





--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ATLAS-2177) offset is not reset when search by type is changed, leads to undesired results.

[Sharmadha Sainath (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16180633#comment-16180633
 ] 

Sharmadha Sainath commented on ATLAS-2177:
--

[~ayubkhan] Looks like duplicate of 
[ATLAS-2168|https://issues.apache.org/jira/browse/ATLAS-2168]

> offset is not reset when search by type is changed, leads to undesired 
> results.
> ---
>
> Key: ATLAS-2177
> URL: https://issues.apache.org/jira/browse/ATLAS-2177
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-webui
>Affects Versions: 0.9-incubating
>Reporter: Ayub Pathan
>Priority: Critical
> Fix For: 0.9-incubating
>
> Attachments: bug-snap2.mp4
>
>
> Attaching recording for reference.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2171) Accessing atlas via knox proxy without "/" at the end logs in as UNKNOWN user

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2171:


 Summary: Accessing atlas via knox proxy without "/" at the end 
logs in as UNKNOWN user
 Key: ATLAS-2171
 URL: https://issues.apache.org/jira/browse/ATLAS-2171
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 0.9-incubating
Reporter: Sharmadha Sainath
Priority: Critical


1. Enabled knox proxy for atlas.
2.Accessed Atlas UI via proxy using https://knox_gateway:8443/gateway/ui/atlas
3. Provided admin username and password and logged into Atlas
4. Now, opened another tab in browser with URL
{code}
https://knox_gateway:8443/gateway/ui/atlas
{code}
I was not logged in as admin but as an unknown user.No read/write operations 
were allowed. Found the following application logs :
{code}
2017-09-26 05:39:31,467 ERROR - [pool-2-thread-9:] ~ Unable to find Atlas 
Resource corresponding to :
Setting UNKNOWN (AtlasAuthorizationUtils:143)
{code}

If the URL is accessed with "/" at the end , logs in as admin user and all 
operations work fine.
Example :
{code}
https://knox_gateway:8443/gateway/ui/atlas/
{code}





--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (ATLAS-2164) Unable to execute the saved search query using its GUID

[Sharmadha Sainath (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sharmadha Sainath resolved ATLAS-2164.
--
Resolution: Invalid

> Unable to execute the saved search query using its GUID
> ---
>
> Key: ATLAS-2164
> URL: https://issues.apache.org/jira/browse/ATLAS-2164
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>        Reporter: Sharmadha Sainath
>Priority: Critical
>
> 1.Created and saved 2 searches - one basic , one Advanced.
> Following is the response of  /api/atlas/v2/search/saved :
> {code}
> [  
>{  
>   "guid":"153e89bb-eabb-4cc6-9cda-07c7ed084bac",
>   "ownerName":"admin",
>   "name":"basic_search1",
>   "searchType":"BASIC",
>   "searchParameters":{  
>  "query":"default",
>  "typeName":"Asset",
>  "classification":"tag3",
>  "excludeDeletedEntities":true,
>  "limit":0,
>  "offset":0
>   }
>},
>{  
>   "guid":"19be50af-bba1-424f-80e1-c49681b2bdeb",
>   "ownerName":"admin",
>   "name":"dsl_search_1",
>   "searchType":"ADVANCED",
>   "searchParameters":{  
>  "query":"where name=\"h1\"",
>  "typeName":"hdfs_path",
>  "excludeDeletedEntities":true,
>  "limit":0,
>  "offset":0
>   }
>}
> ]
> {code}
> 2.Fired the following to execute basic saved query using its GUID:
> {code}
> http://localhost:21000/api/atlas/v2/search/saved/execute/153e89bb-eabb-4cc6-9cda-07c7ed084bac
> {code}
> Response :
> {code}
> {
> errorCode: "ATLAS-404-00-009",
> errorMessage: "Instance __AtlasUserSavedSearch with unique attribute 
> {uniqueName=admin:153e89bb-eabb-4cc6-9cda-07c7ed084bac:BASIC} does not exist"
> }
> {code}
> Note : Logged in as admin while executing the "execute" query.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (ATLAS-2165) Limit set to 0 while executing saved query hence no results are fetched.

[Sharmadha Sainath (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sharmadha Sainath resolved ATLAS-2165.
--
Resolution: Invalid

> Limit set to 0 while executing saved query hence no results are fetched.
> 
>
> Key: ATLAS-2165
> URL: https://issues.apache.org/jira/browse/ATLAS-2165
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>        Reporter: Sharmadha Sainath
>Priority: Blocker
>
> Fired REST call to execute a saved query using its name :
> {code}
> http://localhost:21000/api/atlas/v2/search/saved/execute/basic_search1
> {code}
> Following was the response :
> {code}
> {  
>guid:"153e89bb-eabb-4cc6-9cda-07c7ed084bac",
>ownerName:"admin",
>name:"basic_search1",
>searchType:"BASIC",
>searchParameters:{  
>   query:"default",
>   typeName:"Asset",
>   classification:"tag3",
>   excludeDeletedEntities:true,
>   limit:0,
>   offset:0
>}
> }
> {code}
> limit is set to 0 hence no entities are fetched though the query has many 
> resulting entities.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2165) Limit set to 0 while executing saved query hence no results are fetched.

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2165:


 Summary: Limit set to 0 while executing saved query hence no 
results are fetched.
 Key: ATLAS-2165
 URL: https://issues.apache.org/jira/browse/ATLAS-2165
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 0.9.1
Reporter: Sharmadha Sainath
Priority: Blocker


Fired REST call to execute a saved query using its name :
{code}
http://localhost:21000/api/atlas/v2/search/saved/execute/basic_search1
{code}

Following was the response :
{code}
{  
   guid:"153e89bb-eabb-4cc6-9cda-07c7ed084bac",
   ownerName:"admin",
   name:"basic_search1",
   searchType:"BASIC",
   searchParameters:{  
  query:"default",
  typeName:"Asset",
  classification:"tag3",
  excludeDeletedEntities:true,
  limit:0,
  offset:0
   }
}
{code}

limit is set to 0 hence no entities are fetched though the query has many 
resulting entities.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2164) Unable to execute the saved search query using its GUID

[Sharmadha Sainath (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sharmadha Sainath updated ATLAS-2164:
-
Description: 
1.Created and saved 2 searches - one basic , one Advanced.
Following is the response of  /api/atlas/v2/search/saved :
{code}
[  
   {  
  "guid":"153e89bb-eabb-4cc6-9cda-07c7ed084bac",
  "ownerName":"admin",
  "name":"basic_search1",
  "searchType":"BASIC",
  "searchParameters":{  
 "query":"default",
 "typeName":"Asset",
 "classification":"tag3",
 "excludeDeletedEntities":true,
 "limit":0,
 "offset":0
  }
   },
   {  
  "guid":"19be50af-bba1-424f-80e1-c49681b2bdeb",
  "ownerName":"admin",
  "name":"dsl_search_1",
  "searchType":"ADVANCED",
  "searchParameters":{  
 "query":"where name=\"h1\"",
 "typeName":"hdfs_path",
 "excludeDeletedEntities":true,
 "limit":0,
 "offset":0
  }
   }
]

{code}

2.Fired the following to execute basic saved query using its GUID:
{code}
http://localhost:21000/api/atlas/v2/search/saved/execute/153e89bb-eabb-4cc6-9cda-07c7ed084bac
{code}

Response :
{code}
{
errorCode: "ATLAS-404-00-009",
errorMessage: "Instance __AtlasUserSavedSearch with unique attribute 
{uniqueName=admin:153e89bb-eabb-4cc6-9cda-07c7ed084bac:BASIC} does not exist"
}
{code}


Note : Logged in as admin while executing the "execute" query.

  was:
1.Created and saved 2 searches - one basic , one Advanced.
Following is the response of  /api/atlas/v2/search/saved :
{code}
[  
   {  
  "guid":"153e89bb-eabb-4cc6-9cda-07c7ed084bac",
  "ownerName":"admin",
  "name":"basic_search1",
  "searchType":"BASIC",
  "searchParameters":{  
 "query":"default",
 "typeName":"Asset",
 "classification":"tag3",
 "excludeDeletedEntities":true,
 "limit":0,
 "offset":0
  }
   },
   {  
  "guid":"19be50af-bba1-424f-80e1-c49681b2bdeb",
  "ownerName":"admin",
  "name":"dsl_search_1",
  "searchType":"ADVANCED",
  "searchParameters":{  
 "query":"where name=\"h1\"",
 "typeName":"hdfs_path",
 "excludeDeletedEntities":true,
 "limit":0,
 "offset":0
  }
   }
]

{code}

2.Fired the following to execute basic saved query using its GUID:
{code}
http://localhost:21000/api/atlas/v2/search/saved/execute/153e89bb-eabb-4cc6-9cda-07c7ed084bac
{code}

Response :
{code}
{
errorCode: "ATLAS-404-00-009",
errorMessage: "Instance __AtlasUserSavedSearch with unique attribute 
{uniqueName=admin:153e89bb-eabb-4cc6-9cda-07c7ed084bac:BASIC} does not exist"
}
{code}



> Unable to execute the saved search query using its GUID
> ---
>
> Key: ATLAS-2164
> URL: https://issues.apache.org/jira/browse/ATLAS-2164
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9.1
>Reporter: Sharmadha Sainath
>Priority: Critical
>
> 1.Created and saved 2 searches - one basic , one Advanced.
> Following is the response of  /api/atlas/v2/search/saved :
> {code}
> [  
>{  
>   "guid":"153e89bb-eabb-4cc6-9cda-07c7ed084bac",
>   "ownerName":"admin",
>   "name":"basic_search1",
>   "searchType":"BASIC",
>   "searchParameters":{  
>  "query":"default",
>  "typeName":"Asset",
>  "classification":"tag3",
>  "excludeDeletedEntities":true,
>  "limit":0,
>  "offset":0
>   }
>},
>{  
>   "guid":"19be50af-bba1-424f-80e1-c49681b2bdeb",
>   "ownerName":"admin",
>   "name":"dsl_search_1",
>   "searchType":"ADVANCED",
>   "searchParameters":{  
>  "query":"where name=\"h1\"",
>  "typeName":"hdfs_path",
>  "excludeDeletedEntities":true,
>  "limit":0,
>  "offset":0
>   }
>}
> ]
> {code}
> 2.Fired the following to execute basic saved query using its GUID:
> {code}
> http://localhost:21000/api/atlas/v2/search/saved/execute/153e89bb-eabb-4cc6-9cda-07c7ed084bac
> {code}
> Response :
> {code}
> {
> errorCode: "ATLAS-404-00-009",
> errorMessage: "Instance __AtlasUserSavedSearch with unique attribute 
> {uniqueName=admin:153e89bb-eabb-4cc6-9cda-07c7ed084bac:BASIC} does not exist"
> }
> {code}
> Note : Logged in as admin while executing the "execute" query.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2164) Unable to execute the saved search query using its GUID

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2164:


 Summary: Unable to execute the saved search query using its GUID
 Key: ATLAS-2164
 URL: https://issues.apache.org/jira/browse/ATLAS-2164
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 0.9.1
Reporter: Sharmadha Sainath
Priority: Critical


1.Created and saved 2 searches - one basic , one Advanced.
Following is the response of  /api/atlas/v2/search/saved :
{code}
[  
   {  
  "guid":"153e89bb-eabb-4cc6-9cda-07c7ed084bac",
  "ownerName":"admin",
  "name":"basic_search1",
  "searchType":"BASIC",
  "searchParameters":{  
 "query":"default",
 "typeName":"Asset",
 "classification":"tag3",
 "excludeDeletedEntities":true,
 "limit":0,
 "offset":0
  }
   },
   {  
  "guid":"19be50af-bba1-424f-80e1-c49681b2bdeb",
  "ownerName":"admin",
  "name":"dsl_search_1",
  "searchType":"ADVANCED",
  "searchParameters":{  
 "query":"where name=\"h1\"",
 "typeName":"hdfs_path",
 "excludeDeletedEntities":true,
 "limit":0,
 "offset":0
  }
   }
]

{code}

2.Fired the following to execute basic saved query using its GUID:
{code}
http://localhost:21000/api/atlas/v2/search/saved/execute/153e89bb-eabb-4cc6-9cda-07c7ed084bac
{code}

Response :
{code}
{
errorCode: "ATLAS-404-00-009",
errorMessage: "Instance __AtlasUserSavedSearch with unique attribute 
{uniqueName=admin:153e89bb-eabb-4cc6-9cda-07c7ed084bac:BASIC} does not exist"
}
{code}




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2161) UI : Save Search Query: Search button is not enabled when a saved search has only "Query" without typename / classification

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2161:


 Summary: UI : Save Search Query: Search button is not enabled when 
a saved search has only "Query" without typename / classification
 Key: ATLAS-2161
 URL: https://issues.apache.org/jira/browse/ATLAS-2161
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 0.9.1
Reporter: Sharmadha Sainath
Priority: Minor


1.Fired a basic search :
query = table1 (without typename and classification name). Now Search button 
was enabled.
2.Saved the search as hive_table_search.
3.Cleared the search.
4.Clicked on the saved search - hive_table_search.
5.table1 was populated in the query text box. But Search button was not enabled.
6.But on clicking the "..." on the hive_table_search and selecting "Search" 
option fired the search and fetched the entity.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2153) UI : Adding more columns to the search table masks the "Remove tag" button

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2153:


 Summary: UI : Adding more columns to the search table masks the 
"Remove tag" button 
 Key: ATLAS-2153
 URL: https://issues.apache.org/jira/browse/ATLAS-2153
 Project: Atlas
  Issue Type: Bug
  Components: atlas-webui
Affects Versions: 0.9-incubating, 0.9.1
Reporter: Sharmadha Sainath
Priority: Minor


For basic search typename = hive_table , 20 attributes can be added in the 
columns filter. When more attributes are added , "Remove Tag" (Cross button) on 
the Tag under Tags column  is masked. This happens when the screen size is less 
and more columns are added. When columns are removed , Remove button shows up 
again.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2151) Search using entity and trait attributes - OR condition considers only the first criterion in the list

[Sharmadha Sainath (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sharmadha Sainath updated ATLAS-2151:
-
Summary: Search using entity and trait attributes - OR condition considers 
only the first criterion in the list   (was: Search using entity and trait 
attributes - OR condition takes only the first parameter)

> Search using entity and trait attributes - OR condition considers only the 
> first criterion in the list 
> ---
>
> Key: ATLAS-2151
> URL: https://issues.apache.org/jira/browse/ATLAS-2151
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating, 0.9.1
>    Reporter: Sharmadha Sainath
>Priority: Critical
>
> 1.Created 2 hive_table entities by name : table1 and table2.
> 2. Fired basic search query with following POST body :
> {code}
> {  
>"entityFilters":{  
>   "condition":"OR",
>   "criterion":[ 
>  {  
> "attributeName":"name",
> "operator":"=",
> "attributeValue":"table1"
>  },
>  {  
> "attributeName":"name",
> "operator":"=",
> "attributeValue":"table2"
>  }
>   ]
>},
>"tagFilters":null,
>"attributes":[  
>],
>"query":null,
>"limit":25,
>"offset":0,
>"typeName":"hive_table",
>"classification":null,
>"excludeDeletedEntities": false
> }
> {code}
> 2. Expected the response would return both table1 and table2.
> 3. Only table1 (first filter) is returned. Any filter other than "!=" in the 
> second condition doesn't fetch expected results.
> 4. Also when "excludeDeletedEntities" is set to true , though table1 and 
> table2 are ACTIVE , no entity is returned.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2151) Search using entity and trait attributes - OR condition takes only the first parameter

[Sharmadha Sainath (JIRA)]

Sharmadha Sainath created ATLAS-2151:


 Summary: Search using entity and trait attributes - OR condition 
takes only the first parameter
 Key: ATLAS-2151
 URL: https://issues.apache.org/jira/browse/ATLAS-2151
 Project: Atlas
  Issue Type: Bug
  Components:  atlas-core
Affects Versions: 0.9-incubating, 0.9.1
Reporter: Sharmadha Sainath
Priority: Critical


1.Created 2 hive_table entities by name : table1 and table2.
2. Fired basic search query with following POST body :
{code}
{  
   "entityFilters":{  
  "condition":"OR",
  "criterion":[ 
 {  
"attributeName":"name",
"operator":"=",
"attributeValue":"table1"
 },
 {  
"attributeName":"name",
"operator":"=",
"attributeValue":"table2"
 }
  ]
   },
   "tagFilters":null,
   "attributes":[  
   ],
   "query":null,
   "limit":25,
   "offset":0,
   "typeName":"hive_table",
   "classification":null,
   "excludeDeletedEntities": false
}
{code}

2. Expected the response would return both table1 and table2.
3. Only table1 (first filter) is returned. Any filter other than "!=" in the 
second condition doesn't fetch expected results.
4. Also when "excludeDeletedEntities" is set to true , though table1 and table2 
are ACTIVE , no entity is returned.






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (ATLAS-2142) Regression : Disassociating tag from Entity and Editing tag attributes associated to an entity throw NPE

[Sharmadha Sainath (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sharmadha Sainath resolved ATLAS-2142.
--
Resolution: Duplicate

Duplicate of [ATLAS-2141|https://issues.apache.org/jira/browse/ATLAS-2142] . 
Filed twice by mistake when Apache was down for some time.

> Regression : Disassociating tag from Entity and Editing tag attributes 
> associated to an entity throw NPE
> 
>
> Key: ATLAS-2142
> URL: https://issues.apache.org/jira/browse/ATLAS-2142
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.9-incubating
>    Reporter: Sharmadha Sainath
>
> Editing tag attribute value associated to an entity throws 500 Internal 
> server error with NPE and with Error Notification "Tag  could not be 
> added".
> Disassociating a tag from an entity also throws 500 Internal server error 
> with NPE , and with Error Notification "Tag  could not be deleted". 
> Tag addition works fine.
> This is a regression caused after 
> [ATLAS-2100|https://issues.apache.org/jira/browse/ATLAS-2100].
> Attached the exception stack trace seen for both cases.
> CC :[~ashutoshm] [~madhan.neethiraj]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)