4ca65f6a4bda the latency would vary depending on the size of the index and the amount of customer data.

I ran some analysis and only 0.08% of queries are using wildcards, so the risk of increasing latency for all customers was not something the team wanted.

Happy to chat more about your specific circumstance and learn why you don't have the ability to search for words that end on a specific text: https://calendly.com/owallis

owallis@atlassian.com Did you test the exact impact on search latency?
We don't have the ability to search for words that end on a specific text, as far as I know.
So being able to search with latency is still better than no possibility at all.

We don’t enable leading wildcards due to high latency. This is as per recommendation from OpenSearch: Wildcard

Thus sadly we won't be fixing this ticket

Confluence search syntax page mentions leading wildcards in search are not supported. There was, however, a workaround as described on a very similar page here Confluence Search Syntax
and that is by using the following pattern /.text./ to search for words including "pretext", "textpost", as also mentioned here Solved: search exact word . 

This workaround stopped working since migration to confluence Cloud, as mentioned here Confluence Search: Why does the workaround with RegEx for leading wildcards not work? . 

Is this the only ticket relating to the mentioned problem?
Last comment in 2017 seems quite old...

In my opinion, this is a key feature for user acceptance which is missing.
So not a request for a new feature, but a bug which damages the user experience.

At least, clearly mention this issue in the documentation:
https://support.atlassian.com/confluence-cloud/docs/confluence-search-syntax/

maybe it is best you switch the underlying technology.

Google has no problems with wildcards at the beginning.

I give only the advice that the workaround didn't work securely.

It wasn't only a filter on atlassians documentation.
Before i opened a ticket i didn't found sites in my wiki and then i was looking for an example for the support team to reproduce the problem.

Hi,
Wildcard search works on our site with Confluence 6.0.6.

A search for /.*URL./ returns e.g. all documents with "hourly" which is correct...

So this should work with the DEFAULT Confluence search page. Maybe there's some filtering done on the Atlassian Documentation page. They're using the Scroll Viewport addon.

Jan

@jirasupport4 this is my contribution to show that the workaround didn't work secure. Of course there are sites with "wildcard", which i wanted to find!

I opened a supportcall and the support  confirmed that there was a problem and had no solution for this

Hi Atlassian Support Team,

We are using Confluence 5.9.4 and the search with wild cards before words/patterns doesn't work!

This is major issue for our users, could you please add some comments or explanation to this as search function is indeed CRITICAL in documentation system.

Please explain why vdrmeer's suggestion wasn't taken into account ?

Please explain why the POWER option mentioned by dstuder@tvc.org is not mentioned in your documentation at https://confluence.atlassian.com/doc/confluence-search-syntax-158720.html ?

power option: "The beginning / and trailing / tell the search engine that you want to do a regular expressions search rather than just a normal search."

It took us really some time to find out that the already resolved BUG issue continues to exist and that it has part of it's history hidden here as a mare SUGGESTION !

Could you please estimate when you are going to make any action on this ?  **

Please consider altering the documentation in the way you admit your failure and specifically describe there is no way using the wild cards match before the patterns without using regexp.

Looking forward to a positive change.

Luckily for us the workaround works in Confluence 5.9.4

Best Regards,

Adam Dedek

Confluence Support / Comeerzsystems / Commerzbank

@mkornatzki: was I supposed to find anything there ?