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
[jira] [Commented] (SYNCOPE-1656) Remediations are not created on update while pulling
[ https://issues.apache.org/jira/browse/SYNCOPE-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508187#comment-17508187 ] ASF subversion and git services commented on SYNCOPE-1656: -- Commit cc7f2f66b21479f76f632dc24eccc4c5d7c6868b in syncope's branch refs/heads/master from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=cc7f2f6 ] [SYNCOPE-1656] Cleanup and refactor (#327) > Remediations are not created on update while pulling > > > Key: SYNCOPE-1656 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1656 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.1.10 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli >Priority: Major > Fix For: 2.1.11, 3.0.0 > > > # Create an user on Syncope and setup some constraint or validation on an > attribute. For example define an unique attribute, then set a value for it in > the user. > # Create an entity on an external resource that matches with the user > created at step 1. Syncope is going to perform an update. > # Create a pull task on that resource with remediation flagged. > # Run the pull task and you'll see a failure on that user pull, but no > remediations are created. The same behavior while creating an user creates > remediation, instead. -- This message was sent by Atlassian Jira (v8.20.1#820001)
Re: Time for 2.1.11
The problems mentioned below should be gone now, and the number of outstanding issues fixed [1] raised up to 16 meanwhile. Unless there is any objection, I would start the release process tomorrow morning CET. Regards. On 10/03/22 17:10, Andrea Patricelli wrote: Hi all, I've just found a problem related to this [1] issue, thus I had to re-open it. Going to fix it ASAP. Best regards, Andrea [1] https://issues.apache.org/jira/browse/SYNCOPE-1656 On 10/03/22 16:04, Francesco Chicchiriccò wrote: HI all, I believe it is time to cut 2.1.11, with 14 outstanding issues fixed [1] and > 5 months since 2.1.10. Unless there is any objection, I would start the release process tomorrow morning CET. Regards. [1] https://issues.apache.org/jira/issues/?jql=statusCategory%20%3D%20done%20AND%20project%20%3D%2012313120%20AND%20fixVersion%20%3D%2012350677%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[jira] [Resolved] (SYNCOPE-1656) Remediations are not created on update while pulling
[ https://issues.apache.org/jira/browse/SYNCOPE-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-1656. - Resolution: Fixed > Remediations are not created on update while pulling > > > Key: SYNCOPE-1656 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1656 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.1.10 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli >Priority: Major > Fix For: 2.1.11, 3.0.0 > > > # Create an user on Syncope and setup some constraint or validation on an > attribute. For example define an unique attribute, then set a value for it in > the user. > # Create an entity on an external resource that matches with the user > created at step 1. Syncope is going to perform an update. > # Create a pull task on that resource with remediation flagged. > # Run the pull task and you'll see a failure on that user pull, but no > remediations are created. The same behavior while creating an user creates > remediation, instead. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (SYNCOPE-1668) Provide Entity Cache report and management
[ https://issues.apache.org/jira/browse/SYNCOPE-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-1668. - Resolution: Fixed > Provide Entity Cache report and management > -- > > Key: SYNCOPE-1668 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1668 > Project: Syncope > Issue Type: Improvement > Components: core >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.1.11, 3.0.0 > > > Up to 1.2, there used to be a [JSP > page|https://github.com/apache/syncope/blob/1_2_X/core/src/main/webapp/cacheStats.jsp] > reporting information about [OpenJPA cache > data|https://openjpa.apache.org/builds/3.2.1/apache-openjpa/docs/ref_guide_caching.html]. > It is useful to re-introduce such a feature. > It is also useful to provide a mean to completely clear the cache: this would > allow to skip restarts in case manual changes to internal storage (via SQL > statements) are performed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (SYNCOPE-1668) Provide Entity Cache report and management
[ https://issues.apache.org/jira/browse/SYNCOPE-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508173#comment-17508173 ] ASF subversion and git services commented on SYNCOPE-1668: -- Commit 3a483b3a1d6592e4c27ef2fc614774d35a8dcc18 in syncope's branch refs/heads/2_1_X from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=3a483b3 ] [SYNCOPE-1668] Adding entity cache REST endpoints > Provide Entity Cache report and management > -- > > Key: SYNCOPE-1668 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1668 > Project: Syncope > Issue Type: Improvement > Components: core >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.1.11, 3.0.0 > > > Up to 1.2, there used to be a [JSP > page|https://github.com/apache/syncope/blob/1_2_X/core/src/main/webapp/cacheStats.jsp] > reporting information about [OpenJPA cache > data|https://openjpa.apache.org/builds/3.2.1/apache-openjpa/docs/ref_guide_caching.html]. > It is useful to re-introduce such a feature. > It is also useful to provide a mean to completely clear the cache: this would > allow to skip restarts in case manual changes to internal storage (via SQL > statements) are performed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (SYNCOPE-1656) Remediations are not created on update while pulling
[ https://issues.apache.org/jira/browse/SYNCOPE-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508152#comment-17508152 ] ASF subversion and git services commented on SYNCOPE-1656: -- Commit 50e75332800a63cd722e29f1422cbb449908a6e9 in syncope's branch refs/heads/2_1_X from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=50e7533 ] [SYNCOPE-1656] Cleanup and refactor (#327) > Remediations are not created on update while pulling > > > Key: SYNCOPE-1656 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1656 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.1.10 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli >Priority: Major > Fix For: 2.1.11, 3.0.0 > > > # Create an user on Syncope and setup some constraint or validation on an > attribute. For example define an unique attribute, then set a value for it in > the user. > # Create an entity on an external resource that matches with the user > created at step 1. Syncope is going to perform an update. > # Create a pull task on that resource with remediation flagged. > # Run the pull task and you'll see a failure on that user pull, but no > remediations are created. The same behavior while creating an user creates > remediation, instead. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[GitHub] [syncope] ilgrosso merged pull request #327: [SYNCOPE-1656] Cleanup and refactor
ilgrosso merged pull request #327: URL: https://github.com/apache/syncope/pull/327 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@syncope.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (SYNCOPE-1668) Provide Entity Cache report and management
[ https://issues.apache.org/jira/browse/SYNCOPE-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17508150#comment-17508150 ] ASF subversion and git services commented on SYNCOPE-1668: -- Commit b0348eae402d7afcdd1ca3d8cc5e9dca97ab7fe4 in syncope's branch refs/heads/master from Francesco Chicchiriccò [ https://gitbox.apache.org/repos/asf?p=syncope.git;h=b0348ea ] [SYNCOPE-1668] Adding entityCache actuator endpoint > Provide Entity Cache report and management > -- > > Key: SYNCOPE-1668 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1668 > Project: Syncope > Issue Type: Improvement > Components: core >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.1.11, 3.0.0 > > > Up to 1.2, there used to be a [JSP > page|https://github.com/apache/syncope/blob/1_2_X/core/src/main/webapp/cacheStats.jsp] > reporting information about [OpenJPA cache > data|https://openjpa.apache.org/builds/3.2.1/apache-openjpa/docs/ref_guide_caching.html]. > It is useful to re-introduce such a feature. > It is also useful to provide a mean to completely clear the cache: this would > allow to skip restarts in case manual changes to internal storage (via SQL > statements) are performed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (SYNCOPE-1668) Provide Entity Cache report and management
[ https://issues.apache.org/jira/browse/SYNCOPE-1668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-1668: Description: Up to 1.2, there used to be a [JSP page|https://github.com/apache/syncope/blob/1_2_X/core/src/main/webapp/cacheStats.jsp] reporting information about [OpenJPA cache data|https://openjpa.apache.org/builds/3.2.1/apache-openjpa/docs/ref_guide_caching.html]. It is useful to re-introduce such a feature. It is also useful to provide a mean to completely clear the cache: this would allow to skip restarts in case manual changes to internal storage (via SQL statements) are performed. was: Up to 1.2, there used to be a [JSP page|https://github.com/apache/syncope/blob/1_2_X/core/src/main/webapp/cacheStats.jsp] reporting information about [OpenJPA cache data|https://openjpa.apache.org/builds/3.2.1/apache-openjpa/docs/ref_guide_caching.html]. It is useful to re-introduce such a feature. It is also useful to provide a mean to completely clear the cache: this would allow to skip restarts in case manual changes to internal storage (via SQL) are performed. > Provide Entity Cache report and management > -- > > Key: SYNCOPE-1668 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1668 > Project: Syncope > Issue Type: Improvement > Components: core >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò >Priority: Major > Fix For: 2.1.11, 3.0.0 > > > Up to 1.2, there used to be a [JSP > page|https://github.com/apache/syncope/blob/1_2_X/core/src/main/webapp/cacheStats.jsp] > reporting information about [OpenJPA cache > data|https://openjpa.apache.org/builds/3.2.1/apache-openjpa/docs/ref_guide_caching.html]. > It is useful to re-introduce such a feature. > It is also useful to provide a mean to completely clear the cache: this would > allow to skip restarts in case manual changes to internal storage (via SQL > statements) are performed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (SYNCOPE-1668) Provide Entity Cache report and management
Francesco Chicchiriccò created SYNCOPE-1668: --- Summary: Provide Entity Cache report and management Key: SYNCOPE-1668 URL: https://issues.apache.org/jira/browse/SYNCOPE-1668 Project: Syncope Issue Type: Improvement Components: core Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 2.1.11, 3.0.0 Up to 1.2, there used to be a [JSP page|https://github.com/apache/syncope/blob/1_2_X/core/src/main/webapp/cacheStats.jsp] reporting information about [OpenJPA cache data|https://openjpa.apache.org/builds/3.2.1/apache-openjpa/docs/ref_guide_caching.html]. It is useful to re-introduce such a feature. It is also useful to provide a mean to completely clear the cache: this would allow to skip restarts in case manual changes to internal storage (via SQL) are performed. -- This message was sent by Atlassian Jira (v8.20.1#820001)
