[jira] [Commented] (ATLAS-1564) EntityResource v1 should start routing its calls to v2 EntityREST
[ https://issues.apache.org/jira/browse/ATLAS-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15883842#comment-15883842 ] Sarath Subramanian commented on ATLAS-1564: --- committed to master: https://github.com/apache/incubator-atlas/commit/765d556cce4f276d295d06cdb513fc3b9b00dc51 > EntityResource v1 should start routing its calls to v2 EntityREST > - > > Key: ATLAS-1564 > URL: https://issues.apache.org/jira/browse/ATLAS-1564 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian > Attachments: ATLAS-1564.3.patch > > > With the v2 implementation of EntityREST ready, we must start routing all v1 > entity CRUD calls to start using v2 APIs in EntityREST. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1564) EntityResource v1 should start routing its calls to v2 EntityREST
[ https://issues.apache.org/jira/browse/ATLAS-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879898#comment-15879898 ] Sarath Subramanian commented on ATLAS-1564: --- [~davidrad], Agreed. We should start deprecating V1 entities apis soon. I will not be routing v1 glossary calls to v2, but I think we must support existing customers who might have applications depending on V1 entity apis. > EntityResource v1 should start routing its calls to v2 EntityREST > - > > Key: ATLAS-1564 > URL: https://issues.apache.org/jira/browse/ATLAS-1564 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian > > With the v2 implementation of EntityREST ready, we must start routing all v1 > entity CRUD calls to start using v2 APIs in EntityREST. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1564) EntityResource v1 should start routing its calls to v2 EntityREST
[ https://issues.apache.org/jira/browse/ATLAS-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15879899#comment-15879899 ] Sarath Subramanian commented on ATLAS-1564: --- Review Link : https://reviews.apache.org/r/56969/ > EntityResource v1 should start routing its calls to v2 EntityREST > - > > Key: ATLAS-1564 > URL: https://issues.apache.org/jira/browse/ATLAS-1564 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian > > With the v2 implementation of EntityREST ready, we must start routing all v1 > entity CRUD calls to start using v2 APIs in EntityREST. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (ATLAS-1564) EntityResource v1 should start routing its calls to v2 EntityREST
[ https://issues.apache.org/jira/browse/ATLAS-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15871476#comment-15871476 ] David Radley commented on ATLAS-1564: - Some thoughts: Can I suggest that you do not route the V1 Glossary calls to V2. We have JIRA 1410 for a V2 version of the glossary. At some stage we should deprecate the V1 API; or make a statement to say people should use the V2 APIs. I notice there is code to convert V1 shape entities to V2 shapes. It sounds like to make this change you would need to change the V1 entity shapes in the graph to be V2 then skin the V2 APIs with the V1 JAVA, REST API, notification and search wrappers (did i miss any)? As the bridges have been changed to V2 - I am not sure how many people could stay on V1. I think the effort should focus on migration strategies; is this a requirement raised by an Atlas customer? > EntityResource v1 should start routing its calls to v2 EntityREST > - > > Key: ATLAS-1564 > URL: https://issues.apache.org/jira/browse/ATLAS-1564 > Project: Atlas > Issue Type: Bug > Components: atlas-core >Affects Versions: 0.8-incubating >Reporter: Sarath Subramanian >Assignee: Sarath Subramanian > > With the v2 implementation of EntityREST ready, we must start routing all v1 > entity CRUD calls to start using v2 APIs in EntityREST. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
