Uploaded image for project: 'Atlassian Intelligence'
  1. Atlassian Intelligence
  2. AI-830

Extend the Remote API to include a trigger for a full re-index of site content

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.

      Just as a full rebuild of the indices can now be triggered from the Admin panel, it would be very useful to be able to initiate it via SOAP or XML-RPC.

            [AI-830] Extend the Remote API to include a trigger for a full re-index of site content

            BillA added a comment -

            Thank you for raising this issue. While I can see how this feature would be useful, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Thanks again for your idea.

            BillA added a comment - Thank you for raising this issue. While I can see how this feature would be useful, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Thanks again for your idea.

            Nicholas Rahn added a comment -

            When you import a space using the XML-RPC function, 'confluence1.importSpace', the search index is not built on that imported space. Searching in the imported space will not work until the index is rebuilt.

            A work-around would be to have an XML-RPC function, like this issue mentions, that builds the index (say 'confluence1.buildIndex') and to call this directly after the importSpace function.

            Nicholas Rahn added a comment - When you import a space using the XML-RPC function, 'confluence1.importSpace', the search index is not built on that imported space. Searching in the imported space will not work until the index is rebuilt. A work-around would be to have an XML-RPC function, like this issue mentions, that builds the index (say 'confluence1.buildIndex') and to call this directly after the importSpace function.

            Silvan Strüby added a comment -

            That's exactly what I need.
            I'm using XML-RPC to push a space from one confluence instance to another. But there is no possibility to make an indexing after the import (without doing it manually in the Administration Console). Without indexing we aren’t able to use the search-function in the external instance.
            Therefore I would love to do an indexing after every push automatically.
            Basically the only thing missing is the option whether we want to "Build Index" or not after the import (like the flag under "Backup & Restore").

            Silvan Strüby added a comment - That's exactly what I need. I'm using XML-RPC to push a space from one confluence instance to another. But there is no possibility to make an indexing after the import (without doing it manually in the Administration Console). Without indexing we aren’t able to use the search-function in the external instance. Therefore I would love to do an indexing after every push automatically. Basically the only thing missing is the option whether we want to "Build Index" or not after the import (like the flag under "Backup & Restore").

              Unassigned Unassigned
              jfleming James Fleming (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: