[hibernate-issues] [Hibernate-JIRA] Updated: (HSHARDS-4) extend shard locking to criteria and query

[Max Ross (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HSHARDS-4?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Ross updated HSHARDS-4:
---------------------------

    Fix Version/s:     (was: 3.0.0)
                   3.0.0.beta2

> extend shard locking to criteria and query
> ------------------------------------------
>
>                 Key: HSHARDS-4
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSHARDS-4
>             Project: Hibernate Shards
>          Issue Type: New Feature
>          Components: query
>    Affects Versions: 3.0.0.Beta1
>            Reporter: Max Ross
>            Assignee: Max Ross
>             Fix For: 3.0.0.beta2
>
>
> We currently give people the ability to lock the shard used for shard selection, but we should extend this to shard resolution, criteria, and query.  The use case is a request that does all of its db work against a single shard.  Shards should give the user the ability to perform some operation to determine what shard should be used and then lock in that shard so that all subsequent db access via the ShardedSession only uses that one shard.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira