Uploaded image for project: 'Jahia Community'
  1. Jahia Community
  2. JAHIA-4299

Consider making synchronized indexing the default policy again

Details

    • Task
    • Resolution: Done
    • Minor
    • xCM 6.0
    • xCM 6.0
    • None

    Description

      With Jahia 6 we changed the default filter creator for queries to be Lucene rather than DB. The problem with this is that indexation ondefault is only done delayed, resulting in the side-effect, that user might not see the recently added cotnent in the list immediately. This can be fixed by setting the synchronized indexing policy for the particular container definition in the applicationcontext-indexationpolicy.xml

      Perhaps we should make synchronized indexation again THE default rule, as I do not believe it is such a performance issue. So only if there are containers/fields, which may cause slow indexation, then a developer could configure that container definition to be indexed in a delayed indexation. We should decide on switching the default some time before the final BETA.

      TestRail: Results

        Attachments

          Activity

            [JAHIA-4299] Consider making synchronized indexing the default policy again

            Synchronized indexation is the default again.

            pap@commaro.com_old Benjamin Papez (Inactive) added a comment - Synchronized indexation is the default again.

            Moved second IndexReader for non-filtered queries to WORK-544

            pap@commaro.com_old Benjamin Papez (Inactive) added a comment - Moved second IndexReader for non-filtered queries to WORK-544

            We need to test the impact, when synchronized indexation is made the default.

            We also have to consider adding a second IndexReader for non-filtered queries, because if synchronized access is requred, the startup of the IndexReader with auto-warming filters may take too long before being exposed to requests.

            pap@commaro.com_old Benjamin Papez (Inactive) added a comment - We need to test the impact, when synchronized indexation is made the default. We also have to consider adding a second IndexReader for non-filtered queries, because if synchronized access is requred, the startup of the IndexReader with auto-warming filters may take too long before being exposed to requests.

            People

              pap@commaro.com_old Benjamin Papez (Inactive)
              pap@commaro.com_old Benjamin Papez (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                TestRail: Runs

                  TestRail: Cases

                    Packages

                      Version Package
                      xCM 6.0