[jira] [Created] (ISIS-2020) DataNucleus Federated Datastore functionality not used in query

[Brian Kalbfus (JIRA)]

Brian Kalbfus created ISIS-2020:
-----------------------------------

Summary: DataNucleus Federated Datastore functionality not used in query
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus


Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.

example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]

Mailing list: [https://lists.apache.org/thread.html/2edea2f8d802532c3672eddc83b484bbc2e31d1cac16f2759feeb95f@%3Cusers.isis.apache.org%3E]

 

 



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

[Brian Kalbfus (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16661428#comment-16661428 ]

Brian Kalbfus commented on ISIS-2020:
-------------------------------------

I am solving this by patching datanucleus-api-jdo.   JDOQLTypedQueryImpl is getting a query from the primaryStoreMgr instead of finding the correct StoreManager for the class.

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Priority: Major
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[Brian Kalbfus (JIRA)]

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

Brian Kalbfus updated ISIS-2020:
--------------------------------
Attachment: datanucleus-api-jdo.patch

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Priority: Major
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[Brian Kalbfus (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16661428#comment-16661428 ]

Brian Kalbfus edited comment on ISIS-2020 at 10/23/18 11:01 PM:
----------------------------------------------------------------

I am solving this by patching datanucleus-api-jdo.   JDOQLTypedQueryImpl is getting a query from the primaryStoreMgr instead of finding the correct StoreManager for the class.  The attached patch fixes the "Find by Name" operation, not the "List All" operation.


was (Author: bkalbfus):
I am solving this by patching datanucleus-api-jdo.   JDOQLTypedQueryImpl is getting a query from the primaryStoreMgr instead of finding the correct StoreManager for the class.

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Priority: Major
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[Andi Huber (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16661777#comment-16661777 ]

Andi Huber commented on ISIS-2020:
----------------------------------

Hi Brian, without having looked into the details of this issue ...
Do you think it needs fixing on the Datanucleus side? If so you could open an issue on Datanucleus' github page, or even propose a pull-request there. I'm sure Andy Jefferson (who maintains DN) is happy to help out.

Cheers

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Priority: Major
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[Brian Kalbfus (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662499#comment-16662499 ]

Brian Kalbfus commented on ISIS-2020:
-------------------------------------

Hi Andi,

I will look at a PR for datanucleus for the query by name sub-issue.

-Brian

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Priority: Major
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[Dan Haywood (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676249#comment-16676249 ]

Dan Haywood commented on ISIS-2020:
-----------------------------------

raised [datanucleus-api-jdo #93|https://github.com/datanucleus/datanucleus-api-jdo/issues/93]

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Priority: Major
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[Dan Haywood (JIRA)]

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

Dan Haywood updated ISIS-2020:
------------------------------
Fix Version/s: 1.16.3

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Priority: Major
Fix For: 1.16.3
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[Dan Haywood (JIRA)]

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

Dan Haywood resolved ISIS-2020.
-------------------------------
Resolution: Not A Problem

an issue with DN, not Isis

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Priority: Major
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[Brian Kalbfus (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677251#comment-16677251 ]

Brian Kalbfus commented on ISIS-2020:
-------------------------------------

This issue is apparently fixed in datanucleus-core 5.2.0-m2 as of 3 days ago.  Andy patched datanucleus-core because it makes more sense there than my one-off fix of datanucleus-api-jdo.   My datanucleus test passes now.

The fix the test project using Isis, I can't simply reference 5.2.0-m2 from the test project because it is part of isis-core-plugins-jdo-datanucleus-5.  Maybe there is a maven override that allows me to do this.  Is there a newer version of isis-core-plugins-jdo-datanucleus-5 that references the later datanucleus build?

-Brian

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Priority: Major
Fix For: 1.16.3
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[Brian Kalbfus (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677251#comment-16677251 ]

Brian Kalbfus edited comment on ISIS-2020 at 11/6/18 9:32 PM:
--------------------------------------------------------------

This issue is apparently fixed in datanucleus-core 5.2.0-m2 as of 3 days ago.  Andy patched datanucleus-core because it makes more sense there than my one-off fix of datanucleus-api-jdo.   My datanucleus test passes now.

To fix the test project using Isis, I can't simply reference 5.2.0-m2 from the test project because it is part of isis-core-plugins-jdo-datanucleus-5.  Maybe there is a maven override that allows me to do this.  Is there a newer version of isis-core-plugins-jdo-datanucleus-5 that references the later datanucleus build?

-Brian


was (Author: bkalbfus):
This issue is apparently fixed in datanucleus-core 5.2.0-m2 as of 3 days ago.  Andy patched datanucleus-core because it makes more sense there than my one-off fix of datanucleus-api-jdo.   My datanucleus test passes now.

The fix the test project using Isis, I can't simply reference 5.2.0-m2 from the test project because it is part of isis-core-plugins-jdo-datanucleus-5.  Maybe there is a maven override that allows me to do this.  Is there a newer version of isis-core-plugins-jdo-datanucleus-5 that references the later datanucleus build?

-Brian

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Priority: Major
Fix For: 1.16.3
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[Brian Kalbfus (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677341#comment-16677341 ]

Brian Kalbfus commented on ISIS-2020:
-------------------------------------

I updated [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1] with substituting the latest datanucleus-core 5.2 jar.  It makes use of a dependency exception and redeclaring the datanucleus maven plugin in the child pom.  The findByName action works, but listAll does not work with this code - Please advise on how to get listAll to work.

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Priority: Major
Fix For: 1.16.3
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[Andi Huber (JIRA)]

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

Andi Huber reopened ISIS-2020:
------------------------------
Assignee: Andi Huber

As Brian pointed out there is at least two parts to this issue, where one was just fixed on DN's side, while the other could be a bug with Isis.

I can reproduce the 'listAll' not working part, as demonstrated with the github example [1] and as described with steps to reproduce from the user mailing list.

1) create some instances of HelloOtherWorldObject from the "Other" menu: "1", "2", and "3"
2) then 'listAll' HelloOtherWorldObject instances via the "Other" menu, shows no result

[1] [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Assignee: Andi Huber
Priority: Major
Fix For: 2.0.0-M2
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[Andi Huber (JIRA)]

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

Andi Huber updated ISIS-2020:
-----------------------------
Fix Version/s: (was: 1.16.3)
2.0.0-M2

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Assignee: Andi Huber
Priority: Major
Fix For: 2.0.0-M2
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[ASF subversion and git services (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677800#comment-16677800 ]

ASF subversion and git services commented on ISIS-2020:
-------------------------------------------------------

Commit 95b4b404e98ee03a8303bb20007991eb7537bc0a in isis's branch refs/heads/v2 from [~hobrom]
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=95b4b40 ]

ISIS-2020: update to latest DataNucleus

dn5-jdo-api.version -> 3.2.0-m10
dn5-core.version -> 5.2.0-m2
dn5-api-jdo.version -> 5.2.0-m2
dn5-jdo-query.version -> 5.0.8
dn5-rdbms.version -> 5.2.0-m2
dn5-jodatime.version -> 5.2.0-m1

also dealing with the fact, that some DN classes and methods have been
renamed

Task-Url: https://issues.apache.org/jira/browse/ISIS-2020

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Assignee: Andi Huber
Priority: Major
Fix For: 2.0.0-M2
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[ASF subversion and git services (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677801#comment-16677801 ]

ASF subversion and git services commented on ISIS-2020:
-------------------------------------------------------

Commit 95b4b404e98ee03a8303bb20007991eb7537bc0a in isis's branch refs/heads/v2 from [~hobrom]
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=95b4b40 ]

ISIS-2020: update to latest DataNucleus

dn5-jdo-api.version -> 3.2.0-m10
dn5-core.version -> 5.2.0-m2
dn5-api-jdo.version -> 5.2.0-m2
dn5-jdo-query.version -> 5.0.8
dn5-rdbms.version -> 5.2.0-m2
dn5-jodatime.version -> 5.2.0-m1

also dealing with the fact, that some DN classes and methods have been
renamed

Task-Url: https://issues.apache.org/jira/browse/ISIS-2020

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Assignee: Andi Huber
Priority: Major
Fix For: 2.0.0-M2
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[Andi Huber (JIRA)]

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

Andi Huber updated ISIS-2020:
-----------------------------
Fix Version/s: (was: 2.0.0-M2)
2.0.0

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Assignee: Andi Huber
Priority: Major
Fix For: 2.0.0
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[Andi Huber (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16678099#comment-16678099 ]

Andi Huber commented on ISIS-2020:
----------------------------------

As it stands, there is no easy fix to this (see Details below). For now we simply don't support Data Federation [1], as this feature is still 'experimental' with Datanucleus.

DN does recommend to use multiple Persistence Managers instead, which is also not yet supported by Apache Isis. There is a lot of work involved with getting there, which is also related to our vision of supporting JPA as an alternative persistence layer, which requires decoupling from DN.

I'm afraid, this issue will take some time to get resolved.

+Details:+
We are programmatically modifying DN properties, when bootstrapping Apache Isis. We are overriding those that are read in from property files. We do this to handle schema creation.
However, DN's FederatedStoreManager does not allow this approach for secondary properties. I seems would need DN to extends its API in order for us to hook in as we do with the SchemaAwareStoreManager.

 

[1] http://www.datanucleus.org/products/datanucleus/jdo/persistence.html#data_federation

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Assignee: Andi Huber
Priority: Major
Fix For: 2.0.0
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[Andi Huber (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16678099#comment-16678099 ]

Andi Huber edited comment on ISIS-2020 at 11/7/18 11:50 AM:
------------------------------------------------------------

As it stands, there is no easy fix to this (see Details below). For now we simply don't support Data Federation [1], as this feature is still 'experimental' with Datanucleus.

DN does recommend to use multiple Persistence Managers instead, which is also not yet supported by Apache Isis. There is a lot of work involved with getting there, which is also related to our vision of supporting JPA as an alternative persistence layer, which requires decoupling from DN.

I'm afraid, this issue will take some time to get resolved.

+Details:+
We are programmatically modifying DN properties, when bootstrapping Apache Isis. We are overriding those that are read in from property files. We do this to handle schema creation.
However, DN's FederatedStoreManager does not allow this approach for secondary properties. I seems we would need DN to extend its API in order for us to hook in as we do with the SchemaAwareStoreManager.

 

[1] http://www.datanucleus.org/products/datanucleus/jdo/persistence.html#data_federation


was (Author: hobrom):
As it stands, there is no easy fix to this (see Details below). For now we simply don't support Data Federation [1], as this feature is still 'experimental' with Datanucleus.

DN does recommend to use multiple Persistence Managers instead, which is also not yet supported by Apache Isis. There is a lot of work involved with getting there, which is also related to our vision of supporting JPA as an alternative persistence layer, which requires decoupling from DN.

I'm afraid, this issue will take some time to get resolved.

+Details:+
We are programmatically modifying DN properties, when bootstrapping Apache Isis. We are overriding those that are read in from property files. We do this to handle schema creation.
However, DN's FederatedStoreManager does not allow this approach for secondary properties. I seems would need DN to extends its API in order for us to hook in as we do with the SchemaAwareStoreManager.

 

[1] http://www.datanucleus.org/products/datanucleus/jdo/persistence.html#data_federation

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Assignee: Andi Huber
Priority: Major
Fix For: 2.0.0
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[Andi Huber (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16678099#comment-16678099 ]

Andi Huber edited comment on ISIS-2020 at 11/7/18 11:51 AM:
------------------------------------------------------------

As it stands, there is no easy fix to this (see Details below). For now we simply don't support Data Federation [1], as this feature is still 'experimental' with Datanucleus.

DN does recommend to use multiple Persistence Managers instead, which is also not yet supported by Apache Isis. There is a lot of work involved with getting there, which is also related to our vision of supporting JPA as an alternative persistence layer, which requires decoupling from DN.

I'm afraid, this issue will take some time to get resolved.

+Details:+
We are programmatically modifying DN properties, when bootstrapping Apache Isis. We are overriding those that are read in from property files. We do this to handle schema creation.
However, DN's FederatedStoreManager does not allow this approach for secondary properties. It seems we would need DN to extend its API in order for us to hook in as we do with the SchemaAwareStoreManager.

 

[1] http://www.datanucleus.org/products/datanucleus/jdo/persistence.html#data_federation


was (Author: hobrom):
As it stands, there is no easy fix to this (see Details below). For now we simply don't support Data Federation [1], as this feature is still 'experimental' with Datanucleus.

DN does recommend to use multiple Persistence Managers instead, which is also not yet supported by Apache Isis. There is a lot of work involved with getting there, which is also related to our vision of supporting JPA as an alternative persistence layer, which requires decoupling from DN.

I'm afraid, this issue will take some time to get resolved.

+Details:+
We are programmatically modifying DN properties, when bootstrapping Apache Isis. We are overriding those that are read in from property files. We do this to handle schema creation.
However, DN's FederatedStoreManager does not allow this approach for secondary properties. I seems we would need DN to extend its API in order for us to hook in as we do with the SchemaAwareStoreManager.

 

[1] http://www.datanucleus.org/products/datanucleus/jdo/persistence.html#data_federation

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Assignee: Andi Huber
Priority: Major
Fix For: 2.0.0
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[Brian Kalbfus (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16678672#comment-16678672 ]

Brian Kalbfus commented on ISIS-2020:
-------------------------------------

When I change
{code:java}
return repositoryService.allInstances(HelloOtherWorldObject.class);{code}
to
{code:java}
return isisJdoSupport.executeQuery(HelloOtherWorldObject.class, null);{code}
then the result looks good to me.  Is there a good reason to prefer repositoryService#allInstances over doing a query like this?

 

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Assignee: Andi Huber
Priority: Major
Fix For: 2.0.0
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[Brian Kalbfus (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16680647#comment-16680647 ]

Brian Kalbfus commented on ISIS-2020:
-------------------------------------

I have SimpleApp working with a federated data store.  I am working from the v2 branch.

I had to make one change in the isis-core-plugins-jdo-datanucleus-5 module:

[https://github.com/apache/isis/blob/2f8f57c32e3a85c54c35c9d73062e8212bb4c8e5/core/plugins/jdo-datanucleus-5/src/main/java/org/apache/isis/core/runtime/system/persistence/DataNucleusApplicationComponents5.java#L124]

(from the v2 branch)

The isSchemaAwareStoreManager method assumes that hsqldb and sqlserver urls would render a SchemaAwareStoreManager.  This is not the case if there is a secondary store defined - you get a Federated data store manager. 

I suppose you could test for the presence of a "isis.persistor.datanucleus.impl.datanucleus.datastore.*" property to immediately return false.  I commented out this code so that the probePmf test is used.  Also, I had to change the entity listAll methods like I describe in my prior comment and "ignore" the unit test that calls this method.

I now understand why the build and tests succeeded but the web app failed to start:  the federated data store is declared in the webapp module.

What is the downside of not having a SchemaAwareStoreManager in Apache Isis?

Thanks,

Brian

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Assignee: Andi Huber
Priority: Major
Fix For: 2.0.0
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[Andi Huber (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16680953#comment-16680953 ]

Andi Huber commented on ISIS-2020:
----------------------------------

Hi Brian,
thanks for the effort and findings! And you are asking great questions, which are noticed, but I fail to answer, because I don't yet understand our DN integration well enough. Maybe Dan has more insight.

With your last comment you are proposing a fine workaround, which in case of a FederatedStoreManager would make it the responsibility of the developer to properly setup the DN properties in order for schema creation to work. Whereas for SchemaAwareStoreManager, we do this programmatically. And I believe the latter is a bit hacky to deal with other issues from the past, that I'm not particularly aware of.

I'll implement your workaround, but still I fear that this is only the beginning, if we want to fully support the FederatedStoreManager. But there is nothing preventing us from having this as an experimental feature.

Cheers, Andi!

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Assignee: Andi Huber
Priority: Major
Fix For: 2.0.0
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[ASF subversion and git services (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16681016#comment-16681016 ]

ASF subversion and git services commented on ISIS-2020:
-------------------------------------------------------

Commit 44d30790eb139bf8f0394d5fbe7f23decbdf3f46 in isis's branch refs/heads/v2 from [~hobrom]
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=44d3079 ]

ISIS-2020: properly predict Federated Store Manager

Task-Url: https://issues.apache.org/jira/browse/ISIS-2020

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Assignee: Andi Huber
Priority: Major
Fix For: 2.0.0
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[ASF subversion and git services (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16681015#comment-16681015 ]

ASF subversion and git services commented on ISIS-2020:
-------------------------------------------------------

Commit 44d30790eb139bf8f0394d5fbe7f23decbdf3f46 in isis's branch refs/heads/v2 from [~hobrom]
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=44d3079 ]

ISIS-2020: properly predict Federated Store Manager

Task-Url: https://issues.apache.org/jira/browse/ISIS-2020

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Assignee: Andi Huber
Priority: Major
Fix For: 2.0.0
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[ASF subversion and git services (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16681234#comment-16681234 ]

ASF subversion and git services commented on ISIS-2020:
-------------------------------------------------------

Commit 3d16c64e9bdb4b7a23f2ff0673d445b6eeecc75f in isis's branch refs/heads/v2 from [~hobrom]
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=3d16c64 ]

ISIS-2020: fixes the listAll issue

I believe, that the issue is on DN's side with the PersistenceManager
not creating queries that act upon the correct DB connection.

As of DN-5.2 FederatedJDOQLQuery is still work in progress.

We fixed this by utilizing the new type-safe queries as provided with
DN-5, which appear do work correctly on Federated Data Stores.

As a side-effect we fixed the 'disable-MultivaluedFetch' optimization,
which was not working in our implementation since ther was a key
renaming in DN's migration from 4.1.0.M1 to 4.1.0.M2


Task-Url: https://issues.apache.org/jira/browse/ISIS-2020

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Assignee: Andi Huber
Priority: Major
Fix For: 2.0.0
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[ASF subversion and git services (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16681235#comment-16681235 ]

ASF subversion and git services commented on ISIS-2020:
-------------------------------------------------------

Commit 3d16c64e9bdb4b7a23f2ff0673d445b6eeecc75f in isis's branch refs/heads/v2 from [~hobrom]
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=3d16c64 ]

ISIS-2020: fixes the listAll issue

I believe, that the issue is on DN's side with the PersistenceManager
not creating queries that act upon the correct DB connection.

As of DN-5.2 FederatedJDOQLQuery is still work in progress.

We fixed this by utilizing the new type-safe queries as provided with
DN-5, which appear do work correctly on Federated Data Stores.

As a side-effect we fixed the 'disable-MultivaluedFetch' optimization,
which was not working in our implementation since ther was a key
renaming in DN's migration from 4.1.0.M1 to 4.1.0.M2


Task-Url: https://issues.apache.org/jira/browse/ISIS-2020

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Assignee: Andi Huber
Priority: Major
Fix For: 2.0.0
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[ASF subversion and git services (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16681248#comment-16681248 ]

ASF subversion and git services commented on ISIS-2020:
-------------------------------------------------------

Commit 6392d42607c1379dd675d89c08dbff8eafb9d6fe in isis's branch refs/heads/v2 from [~hobrom]
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=6392d42 ]

ISIS-2020: add missing @Programmatic annotation

Task-Url: https://issues.apache.org/jira/browse/ISIS-2020

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Assignee: Andi Huber
Priority: Major
Fix For: 2.0.0
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[ASF subversion and git services (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16681247#comment-16681247 ]

ASF subversion and git services commented on ISIS-2020:
-------------------------------------------------------

Commit 6392d42607c1379dd675d89c08dbff8eafb9d6fe in isis's branch refs/heads/v2 from [~hobrom]
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=6392d42 ]

ISIS-2020: add missing @Programmatic annotation

Task-Url: https://issues.apache.org/jira/browse/ISIS-2020

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Assignee: Andi Huber
Priority: Major
Fix For: 2.0.0
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[ASF subversion and git services (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16681284#comment-16681284 ]

ASF subversion and git services commented on ISIS-2020:
-------------------------------------------------------

Commit f51205290fa23679797ed91a030fea0e687ff1e5 in isis's branch refs/heads/v2 from [~hobrom]
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=f512052 ]

ISIS-2020: setting FIXME markers for known issues with DN's
FederatedDataStore

Task-Url: https://issues.apache.org/jira/browse/ISIS-2020

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Assignee: Andi Huber
Priority: Major
Fix For: 2.0.0
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[ASF subversion and git services (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16681283#comment-16681283 ]

ASF subversion and git services commented on ISIS-2020:
-------------------------------------------------------

Commit f51205290fa23679797ed91a030fea0e687ff1e5 in isis's branch refs/heads/v2 from [~hobrom]
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=f512052 ]

ISIS-2020: setting FIXME markers for known issues with DN's
FederatedDataStore

Task-Url: https://issues.apache.org/jira/browse/ISIS-2020

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: Bug
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Assignee: Andi Huber
Priority: Major
Fix For: 2.0.0
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[Andi Huber (JIRA)]

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

Andi Huber updated ISIS-2020:
-----------------------------
Issue Type: New Feature (was: Bug)

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: New Feature
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Assignee: Andi Huber
Priority: Major
Fix For: 2.0.0
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[Andi Huber (JIRA)]

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

Andi Huber updated ISIS-2020:
-----------------------------
Priority: Minor (was: Major)

Post by Brian Kalbfus (JIRA)
DataNucleus Federated Datastore functionality not used in query
---------------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: New Feature
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Assignee: Andi Huber
Priority: Minor
Fix For: 2.0.0
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[Andi Huber (JIRA)]

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

Andi Huber updated ISIS-2020:
-----------------------------
Summary: Experimantal Support for DataNucleus Federated Datastore (was: DataNucleus Federated Datastore functionality not used in query)

Experimantal Support for DataNucleus Federated Datastore
--------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: New Feature
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Assignee: Andi Huber
Priority: Minor
Fix For: 2.0.0
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[Andi Huber (JIRA)]

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

Andi Huber updated ISIS-2020:
-----------------------------
Summary: Experimental Support for DataNucleus Federated Datastore (was: Experimantal Support for DataNucleus Federated Datastore)

Experimental Support for DataNucleus Federated Datastore
--------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: New Feature
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Assignee: Andi Huber
Priority: Minor
Fix For: 2.0.0
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[ASF subversion and git services (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16682574#comment-16682574 ]

ASF subversion and git services commented on ISIS-2020:
-------------------------------------------------------

Commit d8a3e76d923a65310d4a6a149e2db63838ee6aec in isis's branch refs/heads/v2 from [~hobrom]
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=d8a3e76 ]

ISIS-2020: fixes broken DN Blob mapping

dealing with the fact, that with DN 5.1.10 -> 5.2.0.M1 extension-points
were renamed

DN Migration Guide:
http://www.datanucleus.org/products/accessplatform/migration.html

Task-Url: https://issues.apache.org/jira/browse/ISIS-2020

Post by Andi Huber (JIRA)
Experimental Support for DataNucleus Federated Datastore
--------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: New Feature
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Assignee: Andi Huber
Priority: Minor
Fix For: 2.0.0
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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

[ASF subversion and git services (JIRA)]

[ https://issues.apache.org/jira/browse/ISIS-2020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16682575#comment-16682575 ]

ASF subversion and git services commented on ISIS-2020:
-------------------------------------------------------

Commit d8a3e76d923a65310d4a6a149e2db63838ee6aec in isis's branch refs/heads/v2 from [~hobrom]
[ https://gitbox.apache.org/repos/asf?p=isis.git;h=d8a3e76 ]

ISIS-2020: fixes broken DN Blob mapping

dealing with the fact, that with DN 5.1.10 -> 5.2.0.M1 extension-points
were renamed

DN Migration Guide:
http://www.datanucleus.org/products/accessplatform/migration.html

Task-Url: https://issues.apache.org/jira/browse/ISIS-2020

Post by Andi Huber (JIRA)
Experimental Support for DataNucleus Federated Datastore
--------------------------------------------------------
Key: ISIS-2020
URL: https://issues.apache.org/jira/browse/ISIS-2020
Project: Isis
Issue Type: New Feature
Components: Core: Objectstore: JDO
Affects Versions: 1.16.2, 2.0.0-M1
Reporter: Brian Kalbfus
Assignee: Andi Huber
Priority: Minor
Fix For: 2.0.0
Attachments: datanucleus-api-jdo.patch
Insert and Update operations work as expected, but query operations operate on the primary datastore.  I see from stepping through the M1 code that Insert and Update operations use a transaction that accesses a FederatedDataStore.  I guess that is where the difference occurs in that the query operations get a data store another way, failing to get the FederatedDataStore that is configured.
example code created from helloworld-archetype is at [https://github.com/bkalbfus/isis-federatedDS-2_0_0-M1]
 
 

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