Community
Participate
Working Groups
If you access classes that are partitioned and not partitioned in the same transaction, then the non-partitioned data will be replicated to all database that were accessed. This is not correct, the non partitioned data should only go to the default database.
Setting target and priority. See the following page for the meanings of these fields: http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines Community: Please vote for this bug if it is important to you. Votes are one of the main criteria we use to determine which bugs to fix next.
See, https://bugs.eclipse.org/bugs/show_bug.cgi?id=341153 for diff
Created attachment 194614 [details] add persist partitioning, and partitioning example
Added support for persist to allow assigning the partition for exclusive connections. SVN trunk commit: Bug#340860 - partition persist call https://bugs.eclipse.org/bugs/show_bug.cgi?id=340860 Code review: Andrei (pending) Changes: - Added persist callback to partitioning policies to allow policy to assign exclusive connection based on object being persisted. - Removed some dead code. - Added test for partitioning persist with an exclusive connection. - Added partitioning example.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink