23 Nov
2015
23 Nov
'15
10:41 a.m.
Hi Marius,
On 23 Nov 2015 at 10:26:21, Marius Dumitru Florea
(mariusdumitru.florea@xwiki.com(mailto:mariusdumitru.florea@xwiki.com)) wrote:
On Sat, Nov 21, 2015 at 1:01 PM, vincent(a)massol.net
wrote:
Indeed. I mentioned ES because I’ve used it with ActiveInstalls and I know how to use it
and it seems to work fine. But you’re right.
Note that even if we were to use SOLR it would be a separate instance at the logical level
since we need to let our users install it on a separate machine different from the SOLR
instance we use for search.
I have no experience with SOLR at this stage so it would mean spending several more days
in order to come up with a POC so I’ll leave this to someone else since I don’t have the
time ATM. TBH I’m not even sure I have the time for a POC based on ES right now ;)
Note 2: My idea was to do a quick POC of coding AS + Stats as extensions, in xwiki-contrib
to start with. Of course the XWiki Dev Team plans would probably be to take over those
extensions into the core which means it’s better to get an agreement on the technologies
to use from the onset...
Hi devs,
I think that for data that are both not critical
and high volume we should
use ElasticSearch instead of saving them in our RDBMS.
Why ElasticSearch and not Solr or something else? There are many
comparisons on the web between these two. I wouldn't chose one or another
without an investigation. I agree that data that are both not critical and high
volume could be
stored outside our RDBMS.
Yes, this is the important part for me: agreeing that we should reimplement AS + Stats
using some external store (and since it’s high volume, a non RDBMS store).
Thanks
-Vincent
Thanks,
Marius
>
> So the idea would be to have an embedded ES in XWiki by default (using the
> permanent directory to store its data) and admins could configure XWiki to
> use a separate ES instance (very similar to what we do with SOLR).
>
> Whenever a user modifies/creates/deletes/does operations on XObjects/etc,
> this is sent to ES.
>
> The AS UI queries ES to display the data.
>
> The Stats UI does the same.
>
> Pros:
> - scalability
> - performance
> - extensibility. It’s easy to evolve the schema in ES, and we can easily
> have several formats (as was proven by the Active Installs code)
>
> I’d like to start a POC in my “free” time.
>
> WDYT?
>
> Thanks
> -Vincent