23 Nov
2015
23 Nov
'15
10:42 a.m.
Same here, we already have done lots of work to deal with Solr so it seems
to be using Solr would be a better fit for us. Just need to add another
core (each core has it's own shema).
On Mon, Nov 23, 2015 at 10:26 AM, Marius Dumitru Florea <
mariusdumitru.florea(a)xwiki.com> wrote:
On Sat, Nov 21, 2015 at 1:01 PM, vincent(a)massol.net
<vincent(a)massol.net>
wrote:
--
Thomas Mortagne
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