After more feedback about sharding from IRC and the forum [1], I
believe we should bind sharding implementations to indexed types, as
opposing to index names.
Currently a sharding strategy is strongly related to the index, but
configured on the index name and so it will affect all entities using
th
On Thu, 11 Aug 2011 13:51:33 +0200, Sanne Grinovero
wrote:
> This also means we could change the sharding strategy interface to:
> a - deal with Entity instances instead of org.apache.lucene.Document
> and string-encoded ids
Are there not valid use-cases where I want to make the decision usin
2011/8/11 Hardy Ferentschik :
> On Thu, 11 Aug 2011 13:51:33 +0200, Sanne Grinovero
> wrote:
>
>> This also means we could change the sharding strategy interface to:
>> a - deal with Entity instances instead of org.apache.lucene.Document
>> and string-encoded ids
>
> Are there not valid use-cases
Answers inline
On Thu, 11 Aug 2011 14:27:58 +0200, Sanne Grinovero
wrote:
>>> This also means we could change the sharding strategy interface to:
>>> a - deal with Entity instances instead of org.apache.lucene.Document
>>> and string-encoded ids
>>
>> Are there not valid use-cases where I wan
I'll try to support AS7 and earlier. If its not as7, will catch the
jndi naming exception and try the older name.
For the user transaction lookup, I think that
"java:comp/UserTransaction" is supported by AS7 and earlier. I'll
change the AS7 user transaction lookup to use that.
Any feedback o
