Jenkins build is back to normal : Atlas-master-UnitTests #1410

[Apache Jenkins Server]

See 

Re: Review Request 66928: Data Migration: Import: Infer Types that Store Edge Ids

[Madhan Neethiraj]

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




graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/AtlasGraphSONReader.java
Line 315 (original), 332 (patched)


shouldn't this return 'this.propertiesToPostProcess', instead of creating a 
new instance? If this method is used only to initialize, either rename it or 
avoid this method by directly initializing in line #252.



graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/GraphSONUtility.java
Line 67 (original), 74 (patched)


This one handles removal/updte of properties for map type attributes. 
Aren't similar updates needed for array type attributes as well 
(primitive/struct/entity-ref)?



graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/GraphSONUtility.java
Lines 152 (patched)


edges for all array elements will have __index set to 0. Does this get 
updated in subsequent processing?



graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/GraphSONUtility.java
Lines 340 (patched)


Method replaceReferencedEdgeIdForList() and postProcessListProperty don't 
seem to be used. Please review and remove.



graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/postProcess/PostProcessListProperty.java
Lines 43 (patched)


Should newIdPositionMap be cleared here?



graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/postProcess/PostProcessor.java
Lines 80 (patched)


doesNotHaveProperty() - the name doesn't seem to match the condition 
"return v.property(Constants.TYPENAME_PROPERTY_KEY).isPresent()", which will 
return true for all entity/classification vertices. Please review.



graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/postProcess/PostProcessor.java
Lines 84 (patched)


isVertexOfType() ==> isInstanceVertexOfType()


- Madhan Neethiraj


On May 17, 2018, 8:48 p.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/66928/
> ---
> 
> (Updated May 17, 2018, 8:48 p.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj, Ruchi Solani, and Sarath 
> Subramanian.
> 
> 
> Bugs: ATLAS-2637
> https://issues.apache.org/jira/browse/ATLAS-2637
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Approach**
> New class: _TypesStoringEdgeIds_: Navigates through all the types in the 
> _typeRegistry_, returns map of entity type and properties that store edge ids.
> Modified: _DataMigrationService_: Uses output from class above and passes it 
> down to migration.
> Modified: _PostProcessManager_: Uses the map generated above and uses it for 
> post processing.
> Modified: _GraphSONUtility_: Improvement to check for vertex of type. This 
> avoids potential exeception when a non-existent property is checked for 
> presence.
> 
> Added PostProcess framework.
> Added logic for handling new Array and Map representation.
> 
> 
> Diffs
> -
> 
>   
> graphdb/api/src/main/java/org/apache/atlas/repository/graphdb/AtlasGraph.java 
> 607baf664 
>   
> graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/AtlasJanusGraph.java
>  c0b9c1741 
>   
> graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/AtlasJanusGraphDatabase.java
>  16aecd5e2 
>   
> graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/AtlasGraphSONReader.java
>  ae119b0bc 
>   
> graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/GraphSONUtility.java
>  ec320b03e 
>   
> graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/PostProcessManager.java
>  d0a65f7b1 
>   
> graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/RelationshipTypeCache.java
>  e4e82649b 
>   
> graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/postProcess/PostProcessListProperty.java
>  PRE-CREATION 
>   
> graphdb/janus/src/main/java/org/apache/atlas/repository/graphdb/janus/migration/postProcess/PostProcessor.java
>  PRE-CREATION 
>   
> graphdb/janus/src/test/java/org/apache/atlas/repository/graphdb/janus/migration/BaseUtils.java
>  e863d9fae 
>   
> 

Build failed in Jenkins: PreCommit-ATLAS-Build-Test #421-master-0001-ATLAS-2705-Search-using-term-shouldn-t-show-deleted-.patch

[Apache Jenkins Server]

See 


Changes:

[madhan] ATLAS-2478: updates to support Elasticsearch 5.6.4 index backend (Tech

[madhan] ATLAS-2673: Decode query string for DSL search

[apoorvnaik] ATLAS-2700: Error message fix ATLAS-2701: Usage attribute not 
getting

[madhan] ATLAS-2699: updated UI to use V2 audit API

[madhan] ATLAS-2703: entity delete should not remove its term associations

--
[...truncated 224.74 KB...]
[INFO] Exclude: **/${sys:atlas.data}/**
[INFO] Exclude: **/policy-store.txt
[INFO] Exclude: **/*rebel*.xml
[INFO] Exclude: **/*rebel*.xml.bak
[INFO] Exclude: **/test/resources/**
[INFO] 174 resources included (use -debug for more details)
[INFO] Rat check: Summary over all files. Unapproved: 0, unknown: 0, generated: 
0, approved: 174 licenses.
[INFO] 
[INFO] --- maven-resources-plugin:2.7:copy-resources (copy-resources-solr) @ 
atlas-repository ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 9 resources
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ 
atlas-repository ---
[INFO] 
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
atlas-repository ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 2 resources to META-INF
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.7.0:compile (default-compile) @ 
atlas-repository ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 132 source files to 

[INFO] 
:
 Some input files use or override a deprecated API.
[INFO] 
:
 Recompile with -Xlint:deprecation for details.
[INFO] 
:
 Some input files use unchecked or unsafe operations.
[INFO] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ 
atlas-repository ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 35 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile) @ 
atlas-repository ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 45 source files to 

[INFO] 
:
 

 uses or overrides a deprecated API.
[INFO] 
:
 Recompile with -Xlint:deprecation for details.
[INFO] 
:
 Some input files use unchecked or unsafe operations.
[INFO] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ atlas-repository 
---
[INFO] Surefire report directory: 

[INFO] Using configured provider org.apache.maven.surefire.testng.TestNGProvider

---
 T E S T S
---
Running org.apache.atlas.repository.migration.HiveStocksTest
Running org.apache.atlas.repository.migration.MigrationProgressServiceTest
Running org.apache.atlas.repository.migration.PathTest
Running org.apache.atlas.utils.TestResourceFileUtils
Running org.apache.atlas.utils.ObjectUpdateSynchronizerTest
Running org.apache.atlas.repository.impexp.TypeAttributeDifferenceTest
Running org.apache.atlas.repository.migration.RelationshipMappingTest
Running org.apache.atlas.repository.impexp.UniqueListTest
Running 

Re: Review Request 67225: ATLAS-2705: Search using term shouldn't show deleted entity by default

[Madhan Neethiraj]

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


Ship it!




Ship It!

- Madhan Neethiraj


On May 18, 2018, 11:53 p.m., Apoorv Naik wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/67225/
> ---
> 
> (Updated May 18, 2018, 11:53 p.m.)
> 
> 
> Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, and Sarath 
> Subramanian.
> 
> 
> Bugs: ATLAS-2705
> https://issues.apache.org/jira/browse/ATLAS-2705
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Currently search using term shows deleted entities in the results this is not 
> expected behavior.
> 
> 
> Diffs
> -
> 
>   repository/src/main/java/org/apache/atlas/discovery/SearchContext.java 
> 1890b1da2 
>   
> repository/src/main/java/org/apache/atlas/discovery/TermSearchProcessor.java 
> 19d9bc413 
> 
> 
> Diff: https://reviews.apache.org/r/67225/diff/1/
> 
> 
> Testing
> ---
> 
> PreCommit: 
> https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/421/
> 
> 
> Thanks,
> 
> Apoorv Naik
> 
>

Review Request 67225: ATLAS-2705: Search using term shouldn't show deleted entity by default

[Apoorv Naik]

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

Review request for atlas, Ashutosh Mestry, Madhan Neethiraj, and Sarath 
Subramanian.


Bugs: ATLAS-2705
https://issues.apache.org/jira/browse/ATLAS-2705


Repository: atlas


Description
---

Currently search using term shows deleted entities in the results this is not 
expected behavior.


Diffs
-

  repository/src/main/java/org/apache/atlas/discovery/SearchContext.java 
1890b1da2 
  repository/src/main/java/org/apache/atlas/discovery/TermSearchProcessor.java 
19d9bc413 


Diff: https://reviews.apache.org/r/67225/diff/1/


Testing
---

PreCommit: 
https://builds.apache.org/view/A/view/Atlas/job/PreCommit-ATLAS-Build-Test/421/


Thanks,

Apoorv Naik

[jira] [Created] (ATLAS-2705) [Search] Term search shows deleted entities by default

[Apoorv Naik (JIRA)]

Apoorv Naik created ATLAS-2705:
--

 Summary: [Search] Term search shows deleted entities by default
 Key: ATLAS-2705
 URL: https://issues.apache.org/jira/browse/ATLAS-2705
 Project: Atlas
  Issue Type: Bug
Reporter: Apoorv Naik
Assignee: Apoorv Naik


Search should only show deleted entities if requested.



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

[jira] [Updated] (ATLAS-2705) [Search] Term search shows deleted entities by default

[Apoorv Naik (JIRA)]

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

Apoorv Naik updated ATLAS-2705:
---
Fix Version/s: 1.0.0

> [Search] Term search shows deleted entities by default
> --
>
> Key: ATLAS-2705
> URL: https://issues.apache.org/jira/browse/ATLAS-2705
> Project: Atlas
>  Issue Type: Bug
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.0.0
>
>
> Search should only show deleted entities if requested.



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

Build failed in Jenkins: Atlas-master-UnitTests #1409

[Apache Jenkins Server]

See 


Changes:

[madhan] ATLAS-2703: entity delete should not remove its term associations

--
[...truncated 170.58 KB...]
[INFO] Exclude: **/.externalToolBuilders/**
[INFO] Exclude: **/build.log
[INFO] Exclude: **/.bowerrc
[INFO] Exclude: *.json
[INFO] Exclude: **/overlays/**
[INFO] Exclude: dev-support/**
[INFO] Exclude: **/users-credentials.properties
[INFO] Exclude: **/public/css/animate.min.css
[INFO] Exclude: **/public/css/bootstrap-sidebar.css
[INFO] Exclude: **/public/js/external_lib/**
[INFO] Exclude: **/node_modules/**
[INFO] Exclude: **/public/js/libs/**
[INFO] Exclude: **/atlas.data/**
[INFO] Exclude: **/${sys:atlas.data}/**
[INFO] Exclude: **/policy-store.txt
[INFO] Exclude: **/*rebel*.xml
[INFO] Exclude: **/*rebel*.xml.bak
[INFO] Exclude: **/test/resources/**
[INFO] 174 resources included (use -debug for more details)
[INFO] Rat check: Summary over all files. Unapproved: 0, unknown: 0, generated: 
0, approved: 174 licenses.
[INFO] 
[INFO] --- maven-resources-plugin:2.7:copy-resources (copy-resources-solr) @ 
atlas-repository ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 9 resources
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ 
atlas-repository ---
[INFO] 
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
atlas-repository ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 2 resources to META-INF
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.7.0:compile (default-compile) @ 
atlas-repository ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 132 source files to 

[INFO] 
:
 Some input files use or override a deprecated API.
[INFO] 
:
 Recompile with -Xlint:deprecation for details.
[INFO] 
:
 Some input files use unchecked or unsafe operations.
[INFO] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ 
atlas-repository ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 35 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.7.0:testCompile (default-testCompile) @ 
atlas-repository ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 45 source files to 

[INFO] 
:
 

 uses or overrides a deprecated API.
[INFO] 
:
 Recompile with -Xlint:deprecation for details.
[INFO] 
:
 Some input files use unchecked or unsafe operations.
[INFO] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ atlas-repository 
---
[INFO] Surefire report directory: 

[INFO] Using configured provider org.apache.maven.surefire.testng.TestNGProvider

---
 T E S T S
---
Running org.apache.atlas.repository.impexp.ZipSourceTest
Running org.apache.atlas.query.DSLQueriesTest
Running org.apache.atlas.repository.impexp.ZipSinkTest
Running org.apache.atlas.services.MetricsServiceTest
Running org.apache.atlas.glossary.PaginationHelperTest
Running 

[jira] [Commented] (ATLAS-2703) [Glossary] Term relation edge shouldn't be deleted when entity is deleted

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj commented on ATLAS-2703:
-

+1 for the patch. Thanks [~apoorvnaik]!

> [Glossary] Term relation edge shouldn't be deleted when entity is deleted
> -
>
> Key: ATLAS-2703
> URL: https://issues.apache.org/jira/browse/ATLAS-2703
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: 
> 0001-ATLAS-2703-Term-to-Referenceable-edge-shouldn-t-be-a.patch
>
>
> With a recent hard delete change all internal relationship edges were 
> deleted, when an entity is deleted the desired behavior is to mark the 
> relation as DELETED (soft delete).



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

[jira] [Commented] (ATLAS-2703) [Glossary] Term relation edge shouldn't be deleted when entity is deleted

[genericqa (JIRA)]

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

genericqa commented on ATLAS-2703:
--

This is a test comment

> [Glossary] Term relation edge shouldn't be deleted when entity is deleted
> -
>
> Key: ATLAS-2703
> URL: https://issues.apache.org/jira/browse/ATLAS-2703
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: 
> 0001-ATLAS-2703-Term-to-Referenceable-edge-shouldn-t-be-a.patch
>
>
> With a recent hard delete change all internal relationship edges were 
> deleted, when an entity is deleted the desired behavior is to mark the 
> relation as DELETED (soft delete).



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

[jira] [Created] (ATLAS-2703) [Glossary] Term relation edge shouldn't be deleted when entity is deleted

[Apoorv Naik (JIRA)]

Apoorv Naik created ATLAS-2703:
--

 Summary: [Glossary] Term relation edge shouldn't be deleted when 
entity is deleted
 Key: ATLAS-2703
 URL: https://issues.apache.org/jira/browse/ATLAS-2703
 Project: Atlas
  Issue Type: Bug
Reporter: Apoorv Naik
Assignee: Apoorv Naik


With a recent hard delete change all internal relationship edges were deleted, 
when an entity is deleted the desired behavior is to mark the relation as 
DELETED (soft delete).



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

Re: request to be added as a contributor

[Madhan Neethiraj]

Barbara,

Thanks your interest in contributing to Apache Atlas; and for being a fan & 
supporter! You have been added as a contributor. Welcome to Apache Atlas 
community!

Regards,
Madhan



On 5/18/18, 12:54 PM, "Eckman, Barbara"  wrote:

Hi folks,

I’m the tech lead of a data governance/discovery/lineage project in the 
Technology & Product division of Comcast.   We have been using Apache Atlas for 
the past 1.5 years or so, and love it!  I speak at Strata and DataWorks, among 
others, about it frequently.

We are making great use of the extensibility feature, creating lots of new 
datatypes.  I’d like to submit them for consideration as additions to the code 
base.  Will you please add me as a contributor  
(barbara_eck...@cable.comcast.com)?

Thanks a lot,

Barbara
--
Barbara Eckman, Ph.D.
Principal Data Architect
DX Data Governance and Metadata
Comcast
Speaking at  #StrataData Conference in New York, Sep 11-13 
strataconf.com/ny

request to be added as a contributor

[Eckman, Barbara]

Hi folks,

I’m the tech lead of a data governance/discovery/lineage project in the 
Technology & Product division of Comcast.   We have been using Apache Atlas for 
the past 1.5 years or so, and love it!  I speak at Strata and DataWorks, among 
others, about it frequently.

We are making great use of the extensibility feature, creating lots of new 
datatypes.  I’d like to submit them for consideration as additions to the code 
base.  Will you please add me as a contributor  
(barbara_eck...@cable.comcast.com)?

Thanks a lot,

Barbara
--
Barbara Eckman, Ph.D.
Principal Data Architect
DX Data Governance and Metadata
Comcast
Speaking at  #StrataData Conference in New York, Sep 11-13 
strataconf.com/ny

[jira] [Comment Edited] (ATLAS-2701) [Glossary] Usage attribute not getting persisted for Term

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj edited comment on ATLAS-2701 at 5/18/18 5:20 PM:
--

Committed to following branches:
  - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/9044e037
  - branch-1.0: http://git-wip-us.apache.org/repos/asf/atlas/commit/49a4f964



was (Author: apoorvnaik):
Committed on master:

https://git-wip-us.apache.org/repos/asf?p=atlas.git;a=commit;h=9044e0375cea58641b0f54c1732980f1401fd845

> [Glossary] Usage attribute not getting persisted for Term
> -
>
> Key: ATLAS-2701
> URL: https://issues.apache.org/jira/browse/ATLAS-2701
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0-alpha, 1.0.0
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.0.0
>
>




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

[jira] [Comment Edited] (ATLAS-2700) [Glossary] Error code fixes

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj edited comment on ATLAS-2700 at 5/18/18 5:19 PM:
--

Committed to following branches:
 - master: http://git-wip-us.apache.org/repos/asf/atlas/commit/9044e037
 - branch-1.0: http://git-wip-us.apache.org/repos/asf/atlas/commit/49a4f964


was (Author: apoorvnaik):
Commited on master:

 

https://git-wip-us.apache.org/repos/asf?p=atlas.git;a=commit;h=9044e0375cea58641b0f54c1732980f1401fd845

> [Glossary] Error code fixes
> ---
>
> Key: ATLAS-2700
> URL: https://issues.apache.org/jira/browse/ATLAS-2700
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0-alpha, 1.0.0
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.0.0
>
>
> Fix error code messages  for certain cases.



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

[jira] [Commented] (ATLAS-2699) UI: Use new V2 api structure for Audit

[Madhan Neethiraj (JIRA)]

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

Madhan Neethiraj commented on ATLAS-2699:
-

+1 for the patch. Thanks [~kevalbhatt]!

> UI: Use new V2 api structure for Audit
> --
>
> Key: ATLAS-2699
> URL: https://issues.apache.org/jira/browse/ATLAS-2699
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-2699.patch
>
>




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

[jira] [Commented] (ATLAS-2702) [Glossary] Term's qualifiedName not persisted after anchor change

[Apoorv Naik (JIRA)]

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

Apoorv Naik commented on ATLAS-2702:


Committed on master:

https://git-wip-us.apache.org/repos/asf?p=atlas.git;a=commit;h=9044e0375cea58641b0f54c1732980f1401fd845

> [Glossary] Term's qualifiedName not persisted after anchor change
> -
>
> Key: ATLAS-2702
> URL: https://issues.apache.org/jira/browse/ATLAS-2702
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0-alpha, 1.0.0
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.0.0
>
>




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

[jira] [Resolved] (ATLAS-2702) [Glossary] Term's qualifiedName not persisted after anchor change

[Apoorv Naik (JIRA)]

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

Apoorv Naik resolved ATLAS-2702.

Resolution: Fixed

> [Glossary] Term's qualifiedName not persisted after anchor change
> -
>
> Key: ATLAS-2702
> URL: https://issues.apache.org/jira/browse/ATLAS-2702
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0-alpha, 1.0.0
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.0.0
>
>




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

[jira] [Resolved] (ATLAS-2701) [Glossary] Usage attribute not getting persisted for Term

[Apoorv Naik (JIRA)]

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

Apoorv Naik resolved ATLAS-2701.

Resolution: Fixed

Committed on master:

https://git-wip-us.apache.org/repos/asf?p=atlas.git;a=commit;h=9044e0375cea58641b0f54c1732980f1401fd845

> [Glossary] Usage attribute not getting persisted for Term
> -
>
> Key: ATLAS-2701
> URL: https://issues.apache.org/jira/browse/ATLAS-2701
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 1.0.0-alpha, 1.0.0
>Reporter: Apoorv Naik
>Assignee: Apoorv Naik
>Priority: Major
> Fix For: 1.0.0
>
>




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

Re: please add me as a contributor

[Madhan Neethiraj]

Constantin Nastase,

Thanks for your interest in contributing to Apache Atlas. You have been added 
as a contributor. Welcome to Apache Atlas community!

Regards,
Madhan




On 5/18/18, 9:29 AM, "Nastase, C. (Constantin)" 
 wrote:

Hello All,

Please add me as a contributor to Apache Atlas project. My username and 
email are constantin.nastase and 
constantin.nast...@ing.com.
I would like to be able to assign jiras to myself and others and be able to 
attach patches to jiras.

Thank you,
Constantin Nastase



---
ATTENTION:
The information in this electronic mail message is private and
confidential, and only intended for the addressee. 

The information in this e-mail does not constitute 
Investment Advice as defined in Art 4 of the Markets
in Financial Instruments Directive 2004/39/EC. The Markets
in Financial Instruments Directive 2004/39/EC is not applicable to 
Life insurance and Private pensions products.

Should you receive this message by mistake, you are hereby 
notified that any disclosure, reproduction, distribution or use of this
message is strictly prohibited. Please inform the sender by
reply transmission and delete the message without copying or
opening it.

Messages and attachments are scanned for all viruses known.
If this message contains password-protected attachments, the
files have NOT been scanned for viruses by the ING mail domain.
Always scan attachments before opening them.

---

[jira] [Created] (ATLAS-2701) [Glossary] Usage attribute not getting persisted for Term

[Apoorv Naik (JIRA)]

Apoorv Naik created ATLAS-2701:
--

 Summary: [Glossary] Usage attribute not getting persisted for Term
 Key: ATLAS-2701
 URL: https://issues.apache.org/jira/browse/ATLAS-2701
 Project: Atlas
  Issue Type: Bug
Affects Versions: 1.0.0-alpha, 1.0.0
Reporter: Apoorv Naik
Assignee: Apoorv Naik
 Fix For: 1.0.0






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

[jira] [Created] (ATLAS-2702) [Glossary] Term's qualifiedName not persisted after anchor change

[Apoorv Naik (JIRA)]

Apoorv Naik created ATLAS-2702:
--

 Summary: [Glossary] Term's qualifiedName not persisted after 
anchor change
 Key: ATLAS-2702
 URL: https://issues.apache.org/jira/browse/ATLAS-2702
 Project: Atlas
  Issue Type: Bug
Affects Versions: 1.0.0-alpha, 1.0.0
Reporter: Apoorv Naik
Assignee: Apoorv Naik
 Fix For: 1.0.0






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

[jira] [Created] (ATLAS-2700) [Glossary] Error code fixes

[Apoorv Naik (JIRA)]

Apoorv Naik created ATLAS-2700:
--

 Summary: [Glossary] Error code fixes
 Key: ATLAS-2700
 URL: https://issues.apache.org/jira/browse/ATLAS-2700
 Project: Atlas
  Issue Type: Bug
Affects Versions: 1.0.0-alpha, 1.0.0
Reporter: Apoorv Naik
Assignee: Apoorv Naik
 Fix For: 1.0.0


Fix error code messages  for certain cases.



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

please add me as a contributor

[Nastase, C. (Constantin)]

Hello All,

Please add me as a contributor to Apache Atlas project. My username and email 
are constantin.nastase and 
constantin.nast...@ing.com.
I would like to be able to assign jiras to myself and others and be able to 
attach patches to jiras.

Thank you,
Constantin Nastase


---
ATTENTION:
The information in this electronic mail message is private and
confidential, and only intended for the addressee.

The information in this e-mail does not constitute
Investment Advice as defined in Art 4 of the Markets
in Financial Instruments Directive 2004/39/EC. The Markets
in Financial Instruments Directive 2004/39/EC is not applicable to
Life insurance and Private pensions products.

Should you receive this message by mistake, you are hereby
notified that any disclosure, reproduction, distribution or use of this
message is strictly prohibited. Please inform the sender by
reply transmission and delete the message without copying or
opening it.

Messages and attachments are scanned for all viruses known.
If this message contains password-protected attachments, the
files have NOT been scanned for viruses by the ING mail domain.
Always scan attachments before opening them.
---

[jira] [Updated] (ATLAS-2699) UI: Use new V2 api structure for Audit

[Keval Bhatt (JIRA)]

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

Keval Bhatt updated ATLAS-2699:
---
Fix Version/s: 1.0.0

> UI: Use new V2 api structure for Audit
> --
>
> Key: ATLAS-2699
> URL: https://issues.apache.org/jira/browse/ATLAS-2699
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Fix For: 1.0.0
>
> Attachments: ATLAS-2699.patch
>
>




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

[jira] [Updated] (ATLAS-2699) UI: Use new V2 api structure for Audit

[Keval Bhatt (JIRA)]

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

Keval Bhatt updated ATLAS-2699:
---
Attachment: ATLAS-2699.patch

> UI: Use new V2 api structure for Audit
> --
>
> Key: ATLAS-2699
> URL: https://issues.apache.org/jira/browse/ATLAS-2699
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Keval Bhatt
>Assignee: Keval Bhatt
>Priority: Major
> Attachments: ATLAS-2699.patch
>
>




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

[jira] [Created] (ATLAS-2699) UI: Use new V2 api structure for Audit

[Keval Bhatt (JIRA)]

Keval Bhatt created ATLAS-2699:
--

 Summary: UI: Use new V2 api structure for Audit
 Key: ATLAS-2699
 URL: https://issues.apache.org/jira/browse/ATLAS-2699
 Project: Atlas
  Issue Type: Improvement
Reporter: Keval Bhatt
Assignee: Keval Bhatt






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

Re: Review Request 67083: ATLAS-2665 - Add OMAG-API in Atlas

[Bogdan Sava]

> On May 16, 2018, 1:48 p.m., Graham Wallis wrote:
> > omag-api/src/main/java/org/apache/atlas/omag/admin/server/spring/OMAGServerAdminResource.java
> > Lines 231 (patched)
> > 
> >
> > We also need a method for the LOCAL_GRAPH_REPOSITORY.
> > 
> > The URI should be "/local-repository/mode/local-graph-repository"
> > 
> > The method should be "setGraphLocalRepository" (even though that sounds 
> > a bit weird it would be consistent with the others - change then all to 
> > setLocalRepositoryXXX() if you prefer).
> > 
> > The body of the method should be:
> > return adminAPI.setLocalRepositoryMode(userId, serverName, 
> > LocalRepositoryMode.LOCAL_GRAPH_REPOSITORY);
> 
> Mandy Chessell wrote:
> The setting of the local graph repository should not be an external 
> callable API.  It is only valid in the Atlas server - and in which case it 
> should always be set as soon as the open metadata function is turned on - 
> basically we still need 2 APIs administration.

I am looking to create a configuration bean fo this


- Bogdan


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


On May 17, 2018, 2:56 p.m., Bogdan Sava wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/67083/
> ---
> 
> (Updated May 17, 2018, 2:56 p.m.)
> 
> 
> Review request for atlas, Daniela Otelea, David Radley, Graham Wallis, Mandy 
> Chessell, and Ruxandra Rosu.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Create configuration for OMAG API in Atlas
> 
> 
> Diffs
> -
> 
>   om-fwk-ocf/pom.xml 8b1cefd 
>   omag-api/pom.xml 2338286 
>   
> omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerAdministration.java
>  dd19018 
>   omag-api/src/main/java/org/apache/atlas/omag/admin/OMAGServerCategory.java 
> PRE-CREATION 
>   
> omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminRESTServices.java
>  PRE-CREATION 
>   
> omag-api/src/main/java/org/apache/atlas/omag/admin/server/OMAGServerAdminResource.java
>  ebc9f2a 
>   
> omag-api/src/main/java/org/apache/atlas/omag/admin/server/spring/OMAGServerAdminResource.java
>  PRE-CREATION 
>   
> omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceDescription.java
>  1a15215 
>   
> omag-api/src/main/java/org/apache/atlas/omag/configuration/registration/AccessServiceRegistration.java
>  c2950c4 
>   omag-server/pom.xml 527c5c3 
>   
> omag-server/src/main/java/org/apache/atlas/omag/application/OMAGApplication.java
>  88397de 
>   omag-server/src/main/resources/application.properties PRE-CREATION 
>   omas-assetconsumer/pom.xml 29935e7 
>   
> omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/client/AssetConsumer.java
>  80a98f5 
>   
> omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/publisher/AssetConsumerPublisher.java
>   
>   
> omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/AssetConsumerRESTServices.java
>  967be5a 
>   
> omas-assetconsumer/src/main/java/org/apache/atlas/omas/assetconsumer/server/spring/AssetConsumerOMASResource.java
>  PRE-CREATION 
>   omas-connectedasset/README.md 2f431df 
>   omas-connectedasset/pom.xml 219c972 
>   
> omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/ConnectedAssetRESTServices.java
>  8ae6c37 
>   
> omas-connectedasset/src/main/java/org/apache/atlas/omas/connectedasset/server/spring/ConnectedAssetOMASResource.java
>  PRE-CREATION 
>   omrs/pom.xml 50b9898 
>   
> omrs/src/main/java/org/apache/atlas/omrs/admin/OMRSConfigurationFactory.java 
> 7ae87c6 
>   
> omrs/src/main/java/org/apache/atlas/omrs/rest/server/OMRSRepositoryRESTServices.java
>  5948482 
>   
> omrs/src/main/java/org/apache/atlas/omrs/rest/server/spring/OMRSRepositoryResource.java
>  PRE-CREATION 
>   
> omrs/src/test/java/org/apache/atlas/omrs/archivemanager/opentypes/TestOpenMetadataTypesArchive.java
>  3f85317 
>   
> omrs/src/test/java/org/apache/atlas/omrs/archivemanager/store/TestOMRSArchiveBuilder.java
>  ccf0de6 
>   webapp/pom.xml 03b8408 
>   webapp/src/main/webapp/WEB-INF/applicationContext.xml 2ecd8d1 
>   webapp/src/main/webapp/WEB-INF/openMetadataContext.xml PRE-CREATION 
>   webapp/src/main/webapp/WEB-INF/web.xml 23dc063 
> 
> 
> Diff: https://reviews.apache.org/r/67083/diff/6/
> 
> 
> Testing
> ---
> 
> Create configuration for OMAG API in Atlas using Spring MVC Dispatcher 
> servlet.
> 
> 
> Change base URL for the API to "/open-metadata/access-services" 
> 
> 
> Clean maven unused dependenies
> 
> The Jira issue is 

[jira] [Commented] (ATLAS-2665) Add OMAG-API in Atlas

[Bogdan Sava (JIRA)]

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

Bogdan Sava commented on ATLAS-2665:


The code of ATLAS-2617 added to the patch

> Add OMAG-API in Atlas
> -
>
> Key: ATLAS-2665
> URL: https://issues.apache.org/jira/browse/ATLAS-2665
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Bogdan Sava
>Assignee: Bogdan Sava
>Priority: Major
> Attachments: 0001-ATLAS-2665-Add-OMAG-API-in-Atlas.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v2.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v3.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v4.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v5.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v6.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v7.patch
>
>
> Create configuration for OMAG API in Atlas using Spring MVC Dispatcher 
> servlet.
> Change base URL for the API to "/open-metadata" 
>  
> Add Spring mvc Dispatcher servlet to Atlas API in order to initialize rest 
> resources annotated with.
> Spring mvc has contextConfigLocation init param pointing to 
> /WEB-INF/openMetadataContext.xml which scans the packages:
> {code:java}
> 
> {code}
>  The base URIs will be:
>  - for OMAS: /open-metadata/access-services/
>  - for OMAG: /open-metadata/admin/
>  The omag server spring boot application will have /open-metadata as context 
> path also
>  
> As result:
> /api/* paths will be handled bu jersey-servlet ( 
> com.sun.jersey.spi.spring.container.servlet.SpringServlet )
> /openmetadata/* will be handled by openmetadata-servlet ( 
> org.springframework.web.servlet.DispatcherServlet )
>  
> {code:java}
> 
>  jersey-servlet
>  
>  com.sun.jersey.spi.spring.container.servlet.SpringServlet
>  
>  
>  com.sun.jersey.api.json.POJOMappingFeature
>  true
>  
>  1
> 
> 
>  jersey-servlet
>  /api/atlas/*
> 
> 
>  open-metadata
>  
>  org.springframework.web.servlet.DispatcherServlet
>  
>  
>  contextConfigLocation
>  /WEB-INF/openMetadataContext.xml
>  
>  2
> 
> 
>  open-metadata
>  /open-metadata/*
> 
> {code}
>  
> The review board is: [https://reviews.apache.org/r/67083/]
>  



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

[jira] [Updated] (ATLAS-2665) Add OMAG-API in Atlas

[Bogdan Sava (JIRA)]

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

Bogdan Sava updated ATLAS-2665:
---
Description: 
Create configuration for OMAG API in Atlas using Spring MVC Dispatcher servlet.

Change base URL for the API to "/open-metadata" 

 

Add Spring mvc Dispatcher servlet to Atlas API in order to initialize rest 
resources annotated with.

Spring mvc has contextConfigLocation init param pointing to 
/WEB-INF/openMetadataContext.xml which scans the packages:
{code:java}


{code}
 The base URIs will be:
 - for OMAS: /open-metadata/access-services/

 - for OMAG: /open-metadata/admin/

 The omag server spring boot application will have /open-metadata as context 
path also

 

As result:

/api/* paths will be handled bu jersey-servlet ( 
com.sun.jersey.spi.spring.container.servlet.SpringServlet )

/openmetadata/* will be handled by openmetadata-servlet ( 
org.springframework.web.servlet.DispatcherServlet )

 
{code:java}

 jersey-servlet
 
 com.sun.jersey.spi.spring.container.servlet.SpringServlet
 
 
 com.sun.jersey.api.json.POJOMappingFeature
 true
 
 1



 jersey-servlet
 /api/atlas/*



 open-metadata
 
 org.springframework.web.servlet.DispatcherServlet
 
 
 contextConfigLocation
 /WEB-INF/openMetadataContext.xml
 
 2



 open-metadata
 /open-metadata/*


{code}
 

The review board is: [https://reviews.apache.org/r/67083/]

 

  was:
Create configuration for OMAG API in Atlas using Spring MVC Dispatcher servlet.

Change base URL for the API to "/open-metadata" 

 

Add Spring mvc Dispatcher servlet to Atlas API in order to initialize rest 
resources annotated with.

Spring mvc has contextConfigLocation init param pointing to 
/WEB-INF/openMetadataContext.xml which scans the packages:
{code:java}


{code}
 The base URIs will be:
 - for OMAS: /open-metadata/access-services/

 - for OMAG: /open-metadata/admin/

 The omag server spring boot application will have /open-metadata as context 
path also

 

As result:

/api/* paths will be handled bu jersey-servlet ( 
com.sun.jersey.spi.spring.container.servlet.SpringServlet )

/openmetadata/* will be handled by openmetadata-servlet ( 
org.springframework.web.servlet.DispatcherServlet )

 
{code:java}

 jersey-servlet
 
 com.sun.jersey.spi.spring.container.servlet.SpringServlet
 
 
 com.sun.jersey.api.json.POJOMappingFeature
 true
 
 1



 jersey-servlet
 /api/atlas/*



 open-metadata
 
 org.springframework.web.servlet.DispatcherServlet
 
 
 contextConfigLocation
 /WEB-INF/openMetadataContext.xml
 
 2



 open-metadata
 /open-metadata/*


{code}
 

The review board is: [https://reviews.apache.org/r/67083/]

 


> Add OMAG-API in Atlas
> -
>
> Key: ATLAS-2665
> URL: https://issues.apache.org/jira/browse/ATLAS-2665
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Bogdan Sava
>Assignee: Bogdan Sava
>Priority: Major
> Attachments: 0001-ATLAS-2665-Add-OMAG-API-in-Atlas.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v2.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v3.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v4.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v5.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v6.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v7.patch
>
>
> Create configuration for OMAG API in Atlas using Spring MVC Dispatcher 
> servlet.
> Change base URL for the API to "/open-metadata" 
>  
> Add Spring mvc Dispatcher servlet to Atlas API in order to initialize rest 
> resources annotated with.
> Spring mvc has contextConfigLocation init param pointing to 
> /WEB-INF/openMetadataContext.xml which scans the packages:
> {code:java}
> 
> {code}
>  The base URIs will be:
>  - for OMAS: /open-metadata/access-services/
>  - for OMAG: /open-metadata/admin/
>  The omag server spring boot application will have /open-metadata as context 
> path also
>  
> As result:
> /api/* paths will be handled bu jersey-servlet ( 
> com.sun.jersey.spi.spring.container.servlet.SpringServlet )
> /openmetadata/* will be handled by openmetadata-servlet ( 
> org.springframework.web.servlet.DispatcherServlet )
>  
> {code:java}
> 
>  jersey-servlet
>  
>  com.sun.jersey.spi.spring.container.servlet.SpringServlet
>  
>  
>  com.sun.jersey.api.json.POJOMappingFeature
>  true
>  
>  1
> 
> 
>  jersey-servlet
>  /api/atlas/*
> 
> 
>  open-metadata
>  
>  org.springframework.web.servlet.DispatcherServlet
>  
>  
>  contextConfigLocation
>  /WEB-INF/openMetadataContext.xml
>  
>  2
> 
> 
>  open-metadata
>  /open-metadata/*
> 
> {code}
>  
> The review board is: [https://reviews.apache.org/r/67083/]
>  



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

[jira] [Updated] (ATLAS-2665) Add OMAG-API in Atlas

[Bogdan Sava (JIRA)]

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

Bogdan Sava updated ATLAS-2665:
---
Description: 
Create configuration for OMAG API in Atlas using Spring MVC Dispatcher servlet.

Change base URL for the API to "/open-metadata" 

 

Add Spring mvc Dispatcher servlet to Atlas API in order to initialize rest 
resources annotated with.

Spring mvc has contextConfigLocation init param pointing to 
/WEB-INF/openMetadataContext.xml which scans the packages:
{code:java}


{code}
 The base URIs will be:

- for OMAS: /open-metadata/access-services/

- for OMAG: /open-metadata/admin/

 The omag server spring boot application will have /open-metadata as context 
path also

 

The review board is: [https://reviews.apache.org/r/67083/]

 

  was:
Create configuration for OMAG API in Atlas using Spring MVC Dispatcher servlet.

Change base URL for the API to "/open-metadata" 

 

Add Spring mvc Dispatcher servlet to Atlas API in order to initialize rest 
resources annotated with.

Spring mvc has contextConfigLocation init param pointing to 
/WEB-INF/openMetadataContext.xml which scans the packages:

{code}



{code}

 

 

The review board is: [https://reviews.apache.org/r/67083/]

 


> Add OMAG-API in Atlas
> -
>
> Key: ATLAS-2665
> URL: https://issues.apache.org/jira/browse/ATLAS-2665
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Bogdan Sava
>Assignee: Bogdan Sava
>Priority: Major
> Attachments: 0001-ATLAS-2665-Add-OMAG-API-in-Atlas.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v2.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v3.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v4.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v5.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v6.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v7.patch
>
>
> Create configuration for OMAG API in Atlas using Spring MVC Dispatcher 
> servlet.
> Change base URL for the API to "/open-metadata" 
>  
> Add Spring mvc Dispatcher servlet to Atlas API in order to initialize rest 
> resources annotated with.
> Spring mvc has contextConfigLocation init param pointing to 
> /WEB-INF/openMetadataContext.xml which scans the packages:
> {code:java}
> 
> {code}
>  The base URIs will be:
> - for OMAS: /open-metadata/access-services/
> - for OMAG: /open-metadata/admin/
>  The omag server spring boot application will have /open-metadata as context 
> path also
>  
> The review board is: [https://reviews.apache.org/r/67083/]
>  



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

[jira] [Updated] (ATLAS-2665) Add OMAG-API in Atlas

[Bogdan Sava (JIRA)]

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

Bogdan Sava updated ATLAS-2665:
---
Description: 
Create configuration for OMAG API in Atlas using Spring MVC Dispatcher servlet.

Change base URL for the API to "/open-metadata" 

 

Add Spring mvc Dispatcher servlet to Atlas API in order to initialize rest 
resources annotated with.

Spring mvc has contextConfigLocation init param pointing to 
/WEB-INF/openMetadataContext.xml which scans the packages:

{code}



{code}

 

 

The review board is: [https://reviews.apache.org/r/67083/]

 

  was:
Create configuration for OMAG API in Atlas using Spring MVC Dispatcher servlet.

Change base URL for the API to "/open-metadata" 

 

The review board is: [https://reviews.apache.org/r/67083/]

 


> Add OMAG-API in Atlas
> -
>
> Key: ATLAS-2665
> URL: https://issues.apache.org/jira/browse/ATLAS-2665
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: Bogdan Sava
>Assignee: Bogdan Sava
>Priority: Major
> Attachments: 0001-ATLAS-2665-Add-OMAG-API-in-Atlas.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v2.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v3.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v4.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v5.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v6.patch, 
> ATLAS-2665-Add-OMAG-API-in-Atlas-v7.patch
>
>
> Create configuration for OMAG API in Atlas using Spring MVC Dispatcher 
> servlet.
> Change base URL for the API to "/open-metadata" 
>  
> Add Spring mvc Dispatcher servlet to Atlas API in order to initialize rest 
> resources annotated with.
> Spring mvc has contextConfigLocation init param pointing to 
> /WEB-INF/openMetadataContext.xml which scans the packages:
> {code}
> 
> {code}
>  
>  
> The review board is: [https://reviews.apache.org/r/67083/]
>  



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