[ 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 > 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] > 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)