-
Suggestion
-
Resolution: Unresolved
-
4
-
Issue Summary
Currently when a new Space or Page or other Content is created or copied either through the UI or REST calls, it can take up to a minute for CQL to return the correct results, that is the search results are eventually consistent. This is different to the experience of JQL which is almost immediate in the search results when content is updated.
This is both for REST APIs used for search and through the UI, e.g.
- /wiki/rest/api/content/search?cql=space="CQLTEST" and type="page"
This can mean issues for apps that create or copy pages and then execute CQL will see a delay and this will impact customer experience.
It would be good if the delay between content creation and CQL search was minimised as much as possible.
- mentioned in
-
Page Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[AI-920] CQL searches should be consistent as soon as possible
| Remote Link | New: This issue links to "Page (Confluence)" [ 1030669 ] |
| Support reference count | Original: 3 | New: 4 |
| Support reference count | New: 3 |
| Labels | New: ecohelp |
| Assignee | Original: Shashi Kiran Gujja [ 95f680324019 ] |
| Assignee | Original: Diego Peralta [ ebc00f6a1693 ] | New: Shashi Kiran Gujja [ 95f680324019 ] |
| Assignee | Original: Souradeep Ray [ d7abff4cd556 ] | New: Diego Peralta [ ebc00f6a1693 ] |
| Description |
Original:
h3. Issue Summary
Currently when a new Space or Page or other Content is created or copied either through the UI or REST calls, it can take up to a minute for CQL to return the correct results, that is the search results are eventually consistent. This is different to the experience of JQL which is almost immediate in the search results when content is updated. This can mean issues for apps that create or copy pages and then execute CQL will see a delay and this will impact customer experience. It would be good if the delay between content creation and CQL search was minimised as much as possible. |
New:
h3. Issue Summary
Currently when a new Space or Page or other Content is created or copied either through the UI or REST calls, it can take up to a minute for CQL to return the correct results, that is the search results are eventually consistent. This is different to the experience of JQL which is almost immediate in the search results when content is updated. This is both for REST APIs used for search and through the UI, e.g. * {{/wiki/rest/api/content/search?cql=space="CQLTEST" and type="page"}} This can mean issues for apps that create or copy pages and then execute CQL will see a delay and this will impact customer experience. It would be good if the delay between content creation and CQL search was minimised as much as possible. |