[
https://issues.apache.org/jira/browse/SYNCOPE-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16013912#comment-16013912
]
ASF subversion and git services commented on SYNCOPE-1077:
----------------------------------------------------------
Commit f2e0886b377d6f1c45768b6216b1c9d83223d227 in syncope's branch
refs/heads/2_0_X from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=f2e0886 ]
[SYNCOPE-1077] Applying some ES best practices
> Extension: Elasticsearch-based search engine
> --------------------------------------------
>
> Key: SYNCOPE-1077
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1077
> Project: Syncope
> Issue Type: New Feature
> Components: core, extensions
> Reporter: Francesco Chicchiriccò
> Assignee: Francesco Chicchiriccò
> Fix For: 2.0.4, 2.1.0
>
>
> As outlined in SYNCOPE-1006, the current search engine is somehow fragile
> (being based on SQL views) and highly depends on the DBMS used as internal
> storage - with frequent issues for MySQL / MariaDB.
> [As
> suggested|https://issues.apache.org/jira/browse/SYNCOPE-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15856313#comment-15856313],
> an idea could be to provide another, optional search engine implementation
> which requires an Elasticsearch node.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
