Hi Vinay,
You should anyway use this
any.search.dao=org.apache.syncope.core.persistence.jpa.dao.ElasticsearchAnySearchDAO
since queries are performed on ES, in order to have the best
performances while searching.
On the other end, if you set to PGJPAJSONAnySearchDAO, instead, you're
just telling to Syncope not to use ES to perform searches, but go
directly on db through JSON-based queries, anyway faster than the basic
queries.
Best regards,
Andrea
On 14/03/22 18:49, Vinay Kavala wrote:
Hi Team,
I have enabled Elastic Search on my local syncope instance and it was working
fine with the prescribed changes. Now I am planning to implement JSONB usage as
well and am following the documentation provided in the syncope docs
athttps://syncope.apache.org/docs/2.1/reference-guide.html#postgresql-jsonb
I have a question now for the any.search.dao property in. the
persistence.properties file what should be the value of it?
#any.search.dao=org.apache.syncope.core.persistence.jpa.dao.ElasticsearchAnySearchDAO
any.search.dao=org.apache.syncope.core.persistence.jpa.dao.PGJPAJSONAnySearchDAO
I currently commented out the ElasticSearchDao entry and enabled the
JSONAnySearchDAO. Is this correct? or what should be the value for it?
I am seeing few issues in my local when I start up the server, not sure if it
is related to the same.. just wanted to confirm what is the correct value for
it.
Thanks,
Vinay
--
Andrea Patricelli
Tirasa - Open Source Excellence
http://www.tirasa.net/
Member at The Apache Software Foundation
Syncope
