Sorry if it looks like we had abandoned this thread:
we continued the discussion in the first thread opened by Hardy.
On 2 October 2013 15:16, Emmanuel Bernard wrote:
> On Wed 2013-10-02 15:19, Hardy Ferentschik wrote:
>>
>> On 2 Jan 2013, at 3:06 PM, Emmanuel Bernard wrote:
>>
>> > Turning the
On Wed 2013-10-02 15:19, Hardy Ferentschik wrote:
>
> On 2 Jan 2013, at 3:06 PM, Emmanuel Bernard wrote:
>
> > Turning the problem upside down, I wonder if IndexShardingStrategy
> > should be deprecated and have SharIdentifierProvider as the API a user
> > would implement. It makes for simpler t
On 2 Jan 2013, at 3:06 PM, Emmanuel Bernard wrote:
> Turning the problem upside down, I wonder if IndexShardingStrategy
> should be deprecated and have SharIdentifierProvider as the API a user
> would implement. It makes for simpler things. What would we lose feature
> wise?
That is exactly wha
Turning the problem upside down, I wonder if IndexShardingStrategy
should be deprecated and have SharIdentifierProvider as the API a user
would implement. It makes for simpler things. What would we lose feature
wise?
Emmanuel
On Fri 2013-09-20 17:30, Hardy Ferentschik wrote:
> Hi,
>
> here comes
Hi,
here comes a follow up on my previous email regarding configuration of dynamic
sharding.
Now I would like to get some feedback on ShardIdentifierProvider. This
interface was added for dynamic sharding on
top of DynamicShardingStrategy. Gunnar and I had a discussion around it today
[1] and
