Re: change proposal DataStore

Hi, > extend the datastore interface > workspace name, node name, property name ... I'm not sure if the workspace / node name / node identifier / property name is always available. One advantage of this addition would be: it could speed up garbage collection. If a binary object "knows" the node

Re: change proposal DataStore

On Mon, Jan 25, 2010 at 11:04, JOSE FELIX HERNANDEZ BARRIO wrote: > i think that if we extend the datastore interface, especially the function : > DataRecord addRecord(InputStream stream) > To add more information, for example: workspace name, node name, property > name ... > it would be possible

Re: change proposal DataStore

i think that if we extend the datastore interface, especially the function : DataRecord *addRecord

Re: change proposal DataStore

Hi, Currently there is only data store per repository. If you need a data store per workspace, then you need one repository per workspace. > - Assign a datastore per workspace (customer) so it's possible to measure > (and limit) storage usage for a given customer This more sounds like an "accoun

Re: change proposal DataStore

Are you suggesting to use a different repository for each customer? would the administrative work be very high for such a scenario ? 2010/1/24 Guo Du > On Sun, Jan 24, 2010 at 11:28 AM, JOSE FELIX HERNANDEZ BARRIO > wrote: > > - Assign a datastore per workspace (customer) so it's possible to

Re: change proposal DataStore

On Sun, Jan 24, 2010 at 11:28 AM, JOSE FELIX HERNANDEZ BARRIO wrote: > - Assign a datastore per workspace (customer) so it's possible to measure > (and limit) storage usage for a given customer You may looking for repository as multi tenant solution instead of workspace: http://wiki.apache.org/jac

change proposal DataStore

our goal it's to be able to create most complex policies for the datastore component, for example: - Assign a datastore per workspace (customer) so it's possible to measure (and limit) storage usage for a given customer - Dynamic allocation, so newer or more accessed nodes will be stored on faster