jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From RafalJanik <r...@softwaremind.pl>
Subject Re: Filesystem, datastore and mysql in JackRabbit
Date Fri, 10 Oct 2008 13:17:52 GMT
Thank You very much - now everything is clear:)
Cheers,
Rafael

Alexander Klimetschek pisze:
> No, you should not remove this folder, as the list of subfolders under
> "workspaces/" (or what is configured under Workspaces.rootPath in
> repository.xml) is used by Jackrabbit as what are the existing
> workspaces. Each workspace folder also contains the workspace.xml,
> which defines the configuration for that workspace. (The workspace.xml
> is created from the Workspace element in repository.xml, which only
> acts as a template for new workspaces. To change the configuration of
> existing workspaces, you will always have to modify the workspace.xml)
>
> The lucene index can be deleted, it will be re-created upon next start
> of Jackrabbit (which can take some time, depending on the amount of
> data in the repository).
>
> Regards,
> Alex
>
> On Fri, Oct 10, 2008 at 1:44 PM, RafalJanik <rajn@softwaremind.pl> wrote:
>   
>> Thank  You:)
>> I understand how DataStore works. Important thing for was what exactly is in
>>  [workspaces/WORKSPACE_NAME/index]
>> and  I've found it and second thing - is workspace important and necessary,
>> e.g. what will happen when I remove this folder -
>> will db or repository have any problems. I've done it and everything seems
>> to be ok - it's why i've asked about workspaces and db.
>>
>> Alexander Klimetschek pisze:
>>     
>>> Basically all data (JCR nodes and properties) is stored in the
>>> PersistenceManager, eg. the mysql db in your case. The FileSystem is
>>> only used if the persistence manager uses it, which is not the case
>>> for the (recommended) bundle db persistence managers. The Lucene
>>> search index always uses the filesystem
>>> (workspaces/WORKSPACE_NAME/index). The datastore is used for large
>>> binary properties (eg. files stored as nt:file in the repo), which are
>>> faster when stored separately from smaller properties and on the
>>> filesystem than in a database (and it avoids duplicates, see
>>> http://wiki.apache.org/jackrabbit/DataStore).
>>>
>>> Regards,
>>> Alex
>>>
>>> On Fri, Oct 10, 2008 at 12:44 PM, RafalJanik <rajn@softwaremind.pl> wrote:
>>>
>>>       
>>>> Hi, I'm trying to understand how JacRabbit works...
>>>> In my repository.xml I have <datastore> <persistanceManager>
with mysql.
>>>> In datastore there is sended date which size is lower then 100.
>>>> I know that in MySQL db JackRabbit creates four tables for workspace, but
>>>> when add nodes with the same properties only the workspace in filesystem
>>>> is
>>>> changing and tables in mysqldb. My question is what exactly is putting
>>>> into
>>>> db and what into filesystem after adding a new node? Is workspace
>>>> filesystem
>>>> only working copy of part of data stored in db? How works connections
>>>> between datastore and db?
>>>>
>>>> Cheers,
>>>>
>>>> Rafael
>>>>
>>>>
>>>>
>>>>
>>>>         
>>>
>>>
>>>       
>>     
>
>
>
>   


Mime
View raw message