Re: What should be the value of any.search.dao property in. the persistence.properties
Thank you Francesco for the clarification! Regards, Vinay From: Francesco Chicchiriccò Sent: Monday, March 21, 2022 3:24 AM To: dev@syncope.apache.org Subject: Re: What should be the value of any.search.dao property in. the persistence.properties [CAUTION: EXTERNAL SENDER] Hi, most of your attachments are stripped down, so I can't really tell anything about your current configuration. One important thing is that there is no automatic transition from standard persistence to JSONB, so you either must start with an empty database or you need to provide a way to migrate existing data. Regards. On 19/03/22 22:14, Vinay Kavala wrote: > Sure Francesco. Thanks for the response. > > However, after enabling all the configurations as mentioned in the document, > I still do not see any plainattrs being stored in a JSONB column on the > syncopeuser table. > > How do I verify if my configuration changes are working fine? > > below are my changes for your reference. > > 1. added the below dependency in the core/pom.xml > > 2. updated the persistence.properties with below values > > 3. Updated domains/Master.properties with the below changes > > Master.url=jdbc:postgresql://localhost:5432/syncope*?stringtype=unspecified* > Master.orm=META-INF/*spring-orm-pgjsonb*.xml > Master.audit.sql=*audit_pgjsonb*.sql > the necessary dependencies are downloaded into my local machine > 4. Replaced the below files under respective locations > > 5. restarted the syncope core server > > > *Couple of questions:* > > 1. Do I need to do anything else apart from the above configuration? > 2. what happens to the existing user/group/anyobject data? (I have enabled > the JSONB configuration on an existing syncope core installation, built as a > Maven Project) > 1. does all the plain attributes associated to those objects gets > automatically stored in a respective JSONB column? > 3. how do I verify that my configuration is working? > > > Very much looking forward to the response. > > Thanks in Advance for your Support, > Vinay > > 6. > > > 7. > > > > 8. > > > > > > > > -- > *From:* Francesco Chicchiriccò > *Sent:* Friday, March 18, 2022 7:56 AM > *To:* dev@syncope.apache.org > *Subject:* Re: What should be the value of any.search.dao property in. the > persistence.properties > [CAUTION: EXTERNAL SENDER] > > > Hi Vinay, > with Elasticsearch enabled, you benefit from a general search performance > improvement, even compared with JSONB. > > JSONB support will be anyway beneficial for create, reads and updates. > > Hope this clarifies. > Regards. > > P.S. please send your questions to user@ ML > > On 2022/03/17 23:19:48 Vinay Kavala wrote: > > Thanks Andrea for the clarification! > > > > However, if we intend to use ElasticsearchAnySearchDAO for searching Users, > > Groups and AnyObjects, what is the advantage of enabling JSONB? Where will > > it improve the performance of the system? > > Can you clarify please? > > > > Thanks, > > Vinay > > > > From: Andrea Patricelli > > Sent: Thursday, March 17, 2022 11:30 AM > > To: dev@syncope.apache.org ; Vinay Kavala > > > > Subject: Re: What should be the value of any.search.dao property in. the > > persistence.properties > > > > [CAUTION: EXTERNAL SENDER] > > > > > > 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 > >
Re: What should be the value of any.search.dao property in. the persistence.properties
Hi, most of your attachments are stripped down, so I can't really tell anything about your current configuration. One important thing is that there is no automatic transition from standard persistence to JSONB, so you either must start with an empty database or you need to provide a way to migrate existing data. Regards. On 19/03/22 22:14, Vinay Kavala wrote: Sure Francesco. Thanks for the response. However, after enabling all the configurations as mentioned in the document, I still do not see any plainattrs being stored in a JSONB column on the syncopeuser table. How do I verify if my configuration changes are working fine? below are my changes for your reference. 1. added the below dependency in the core/pom.xml 2. updated the persistence.properties with below values 3. Updated domains/Master.properties with the below changes Master.url=jdbc:postgresql://localhost:5432/syncope*?stringtype=unspecified* Master.orm=META-INF/*spring-orm-pgjsonb*.xml Master.audit.sql=*audit_pgjsonb*.sql the necessary dependencies are downloaded into my local machine 4. Replaced the below files under respective locations 5. restarted the syncope core server *Couple of questions:* 1. Do I need to do anything else apart from the above configuration? 2. what happens to the existing user/group/anyobject data? (I have enabled the JSONB configuration on an existing syncope core installation, built as a Maven Project) 1. does all the plain attributes associated to those objects gets automatically stored in a respective JSONB column? 3. how do I verify that my configuration is working? Very much looking forward to the response. Thanks in Advance for your Support, Vinay 6. 7. 8. -- *From:* Francesco Chicchiriccò *Sent:* Friday, March 18, 2022 7:56 AM *To:* dev@syncope.apache.org *Subject:* Re: What should be the value of any.search.dao property in. the persistence.properties [CAUTION: EXTERNAL SENDER] Hi Vinay, with Elasticsearch enabled, you benefit from a general search performance improvement, even compared with JSONB. JSONB support will be anyway beneficial for create, reads and updates. Hope this clarifies. Regards. P.S. please send your questions to user@ ML On 2022/03/17 23:19:48 Vinay Kavala wrote: > Thanks Andrea for the clarification! > > However, if we intend to use ElasticsearchAnySearchDAO for searching Users, Groups and AnyObjects, what is the advantage of enabling JSONB? Where will it improve the performance of the system? > Can you clarify please? > > Thanks, > Vinay > > From: Andrea Patricelli > Sent: Thursday, March 17, 2022 11:30 AM > To: dev@syncope.apache.org ; Vinay Kavala > Subject: Re: What should be the value of any.search.dao property in. the persistence.properties > > [CAUTION: EXTERNAL SENDER] > > > 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 > >
Re: What should be the value of any.search.dao property in. the persistence.properties
Sure Francesco. Thanks for the response. However, after enabling all the configurations as mentioned in the document, I still do not see any plainattrs being stored in a JSONB column on the syncopeuser table. How do I verify if my configuration changes are working fine? below are my changes for your reference. 1. added the below dependency in the core/pom.xml [cid:d49db35c-0d3e-4c7a-9464-eb2ddd5cc5b5] 2. updated the persistence.properties with below values [cid:f455c7b0-9cc7-4b79-8115-6e4813feb838] 3. Updated domains/Master.properties with the below changes Master.url=jdbc:postgresql://localhost:5432/syncope?stringtype=unspecified Master.orm=META-INF/spring-orm-pgjsonb.xml Master.audit.sql=audit_pgjsonb.sql the necessary dependencies are downloaded into my local machine 4. Replaced the below files under respective locations [cid:28dcd251-210b-4869-af9a-89fee7e3c031] 5. restarted the syncope core server Couple of questions: 1. Do I need to do anything else apart from the above configuration? 2. what happens to the existing user/group/anyobject data? (I have enabled the JSONB configuration on an existing syncope core installation, built as a Maven Project) * does all the plain attributes associated to those objects gets automatically stored in a respective JSONB column? 3. how do I verify that my configuration is working? Very much looking forward to the response. Thanks in Advance for your Support, Vinay 1. 2. 3. From: Francesco Chicchiricc? Sent: Friday, March 18, 2022 7:56 AM To: dev@syncope.apache.org Subject: Re: What should be the value of any.search.dao property in. the persistence.properties [CAUTION: EXTERNAL SENDER] Hi Vinay, with Elasticsearch enabled, you benefit from a general search performance improvement, even compared with JSONB. JSONB support will be anyway beneficial for create, reads and updates. Hope this clarifies. Regards. P.S. please send your questions to user@ ML On 2022/03/17 23:19:48 Vinay Kavala wrote: > Thanks Andrea for the clarification! > > However, if we intend to use ElasticsearchAnySearchDAO for searching Users, > Groups and AnyObjects, what is the advantage of enabling JSONB? Where will it > improve the performance of the system? > Can you clarify please? > > Thanks, > Vinay > > From: Andrea Patricelli > Sent: Thursday, March 17, 2022 11:30 AM > To: dev@syncope.apache.org ; Vinay Kavala > > Subject: Re: What should be the value of any.search.dao property in. the > persistence.properties > > [CAUTION: EXTERNAL SENDER] > > > 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 > >
Re: What should be the value of any.search.dao property in. the persistence.properties
Hi Vinay, with Elasticsearch enabled, you benefit from a general search performance improvement, even compared with JSONB. JSONB support will be anyway beneficial for create, reads and updates. Hope this clarifies. Regards. P.S. please send your questions to user@ ML On 2022/03/17 23:19:48 Vinay Kavala wrote: > Thanks Andrea for the clarification! > > However, if we intend to use ElasticsearchAnySearchDAO for searching Users, > Groups and AnyObjects, what is the advantage of enabling JSONB? Where will it > improve the performance of the system? > Can you clarify please? > > Thanks, > Vinay > > From: Andrea Patricelli > Sent: Thursday, March 17, 2022 11:30 AM > To: dev@syncope.apache.org ; Vinay Kavala > > Subject: Re: What should be the value of any.search.dao property in. the > persistence.properties > > [CAUTION: EXTERNAL SENDER] > > > 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 > >
Re: What should be the value of any.search.dao property in. the persistence.properties
Thanks Andrea for the clarification! However, if we intend to use ElasticsearchAnySearchDAO for searching Users, Groups and AnyObjects, what is the advantage of enabling JSONB? Where will it improve the performance of the system? Can you clarify please? Thanks, Vinay From: Andrea Patricelli Sent: Thursday, March 17, 2022 11:30 AM To: dev@syncope.apache.org ; Vinay Kavala Subject: Re: What should be the value of any.search.dao property in. the persistence.properties [CAUTION: EXTERNAL SENDER] 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
Re: What should be the value of any.search.dao property in. the persistence.properties
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
What should be the value of any.search.dao property in. the persistence.properties
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 at https://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
