23 Nov
2015
23 Nov
'15
10:39 a.m.
Without jumping into the Solr v. ElasticSearch discussion, I am quite
favorable to the general idea of a big-data store complementing the RDBMS.
Especially if it might allow us to again enable stats that are more
fine-grained than those collected by piwik.
This also opens the door to possibly storing revision histories outside
of the db which would be a big win for scalability and might even lead to
one day recommending an embedded db for production, a big win for ease of
installation.
+1 for an investigation.
Caleb
On 23/11/15 10:26, Marius Dumitru Florea wrote:
On Sat, Nov 21, 2015 at 1:01 PM, vincent(a)massol.net
<vincent(a)massol.net>
wrote:
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.
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
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs