You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stanbol.apache.org by florent andré <fl...@4sengines.com> on 2011/06/01 10:18:15 UTC
Save the contentHub on disk
Hello,
Actually the content hub is save in memory. There is a way to turn the
content hub persistent (save on disk) ?
Thanks.
++
Re: Save the contentHub on disk
Posted by Florent André <fl...@apache.org>.
Hooo yes, ok I got it !
Your brain works fine and well remember how it's work.
Thanks for your answers.
On 06/01/2011 06:34 PM, Olivier Grisel wrote:
> 2011/6/1 Florent André<fl...@apache.org>:
>>
>>
>> On 06/01/2011 11:36 AM, Olivier Grisel wrote:
>>>
>>> 2011/6/1 Florent André<fl...@apache.org>:
>>
>> ...
>>>
>>> The enhancements are already stored in a clerezza graph and can be
>>> queries using the sparql endpoint. This is how the contenthub view
>>> currently work.
>>>
>>
>> Yep, I see that. But if I stop/start Stanbol all goes out. There is a
>> configuration for storing graph on the disk ?
>
> The graph is stored on the disk, only th view of the content hub must
> be filtered to only display content items with a non-null binary
> content. The metadata should still be available in the sparql endpoint
> if I remember correctly.
>
Re: Save the contentHub on disk
Posted by Olivier Grisel <ol...@ensta.org>.
2011/6/1 Florent André <fl...@apache.org>:
>
>
> On 06/01/2011 11:36 AM, Olivier Grisel wrote:
>>
>> 2011/6/1 Florent André<fl...@apache.org>:
>
> ...
>>
>> The enhancements are already stored in a clerezza graph and can be
>> queries using the sparql endpoint. This is how the contenthub view
>> currently work.
>>
>
> Yep, I see that. But if I stop/start Stanbol all goes out. There is a
> configuration for storing graph on the disk ?
The graph is stored on the disk, only th view of the content hub must
be filtered to only display content items with a non-null binary
content. The metadata should still be available in the sparql endpoint
if I remember correctly.
--
Olivier
http://twitter.com/ogrisel - http://github.com/ogrisel
Re: Save the contentHub on disk
Posted by Florent André <fl...@apache.org>.
On 06/01/2011 11:36 AM, Olivier Grisel wrote:
> 2011/6/1 Florent André<fl...@apache.org>:
...
>
> The enhancements are already stored in a clerezza graph and can be
> queries using the sparql endpoint. This is how the contenthub view
> currently work.
>
Yep, I see that. But if I stop/start Stanbol all goes out. There is a
configuration for storing graph on the disk ?
Moreover as number of enhancements grow memory become less.
Thanks for your inputs.
++
Re: Save the contentHub on disk
Posted by Olivier Grisel <ol...@ensta.org>.
2011/6/1 Florent André <fl...@apache.org>:
> Thanks for your pointers on size limitation.
>
> About the content hub, my purpose is more about store resulting enhancement
> graphs and query them. For now content streams are store elsewhere.
>
> I could use an external graph repository, but if already include in
> Stanbol...
The enhancements are already stored in a clerezza graph and can be
queries using the sparql endpoint. This is how the contenthub view
currently work.
--
Olivier
http://twitter.com/ogrisel - http://github.com/ogrisel
Re: Save the contentHub on disk
Posted by Florent André <fl...@apache.org>.
Thanks for your pointers on size limitation.
About the content hub, my purpose is more about store resulting
enhancement graphs and query them. For now content streams are store
elsewhere.
I could use an external graph repository, but if already include in
Stanbol...
++
On 06/01/2011 10:28 AM, Olivier Grisel wrote:
> 2011/6/1 florent andré<fl...@4sengines.com>:
>> Hello,
>>
>> Actually the content hub is save in memory. There is a way to turn the
>> content hub persistent (save on disk) ?
>
> Yes this was just a quick prototype. I think clerezza has a blob store
> implementation somewhere we should use to store the content streams.
>
Re: Save the contentHub on disk
Posted by Olivier Grisel <ol...@ensta.org>.
2011/6/1 florent andré <fl...@4sengines.com>:
> Hello,
>
> Actually the content hub is save in memory. There is a way to turn the
> content hub persistent (save on disk) ?
Yes this was just a quick prototype. I think clerezza has a blob store
implementation somewhere we should use to store the content streams.
--
Olivier
http://twitter.com/ogrisel - http://github.com/ogrisel