<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 03:36:54 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[SERVER-15090] Improve Text Indexes to support partial word match</title>
                <link>https://jira.mongodb.org/browse/SERVER-15090</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;As mentioned here &lt;a href=&quot;http://docs.mongodb.org/manual/core/index-text/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://docs.mongodb.org/manual/core/index-text/&lt;/a&gt; it is possible to create text indexes, search for them and sort them by textScore which all works well.&lt;br/&gt;
But as mentioned in &lt;a href=&quot;http://stackoverflow.com/questions/21018738/mongodb-fulltext-search-workaroud-for-partial-word-match&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://stackoverflow.com/questions/21018738/mongodb-fulltext-search-workaroud-for-partial-word-match&lt;/a&gt; and &lt;a href=&quot;http://stackoverflow.com/questions/17887140/mongodb-full-text-search-matching-precesion&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://stackoverflow.com/questions/17887140/mongodb-full-text-search-matching-precesion&lt;/a&gt; it would be very useful to add some option for partial word matching.&lt;/p&gt;

&lt;p&gt;This could either be when you create the Index or when you query the database. Adding a potential implementation, there could be an additional option:&lt;/p&gt;
&lt;p/&gt;
&lt;div id=&quot;syntaxplugin&quot; class=&quot;syntaxplugin&quot; style=&quot;border: 1px dashed #bbb; border-radius: 5px !important; overflow: auto; max-height: 30em;&quot;&gt;
&lt;table cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; border=&quot;0&quot; width=&quot;100%&quot; style=&quot;font-size: 1em; line-height: 1.4em !important; font-weight: normal; font-style: normal; color: black;&quot;&gt;
		&lt;tbody &gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;  margin-top: 10px;   width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;db.reviews.ensureIndex( &lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;   width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;  { comments: &quot;text&quot; } ,&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;   width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;  { match: &quot;partial&quot; }&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;   margin-bottom: 10px;  width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;)&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
			&lt;/tbody&gt;
&lt;/table&gt;
&lt;/div&gt;
&lt;p/&gt;
&lt;p&gt;And the options for match could be &quot;whole&quot; (default), &quot;prefix&quot;, &quot;postfix&quot;, &quot;partial&quot;.  &lt;br/&gt;
Where-as prefix would additionally search with the input-query at the beginning of the word, so for example the stored word is &quot;blueberry&quot;:&lt;br/&gt;
Using prefix:&lt;br/&gt;
It would behave the same as the current search behaviour and in addition a query like &quot;blue&quot; or &quot;bl&quot; or &quot;blueb&quot; would also return &quot;blueberry&quot;, where-as &quot;berry&quot;, &quot;eberry&quot;, &quot;erry&quot; would not.&lt;br/&gt;
Using postfix: Exactly the reverse of &quot;prefix&quot;&lt;br/&gt;
Partial: Matches any characters at any position in the word. So &quot;b&quot;, &quot;ber&quot; &quot;ue&quot; all would return &quot;blueberry&quot;.&lt;/p&gt;

&lt;p&gt;This would in my opinion majorly improve the full-text search in a lot of use-cases, for example building a search for a news site and you wouldn&apos;t have to add additional dependencies such as elasticsearch, which could be an overkill in some scenarios.&lt;br/&gt;
Furhter it would also be much better than regular expression search in these cases, because you get all the &apos;automatic&apos; indexing, the sorting capabilities and it is less error prone because you don&apos;t have to write any regular expression.&lt;/p&gt;</description>
                <environment></environment>
        <key id="155500">SERVER-15090</key>
            <summary>Improve Text Indexes to support partial word match</summary>
                <type id="4" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14710&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="10038" iconUrl="https://jira.mongodb.org/images/icons/subtask.gif" description="">Backlog</status>
                    <statusCategory id="2" key="new" colorName="default"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="backlog-query-integration">Backlog - Query Integration</assignee>
                                    <reporter username="globegitter">Markus Padourek</reporter>
                        <labels>
                            <label>qi-text-search</label>
                    </labels>
                <created>Fri, 29 Aug 2014 13:33:54 +0000</created>
                <updated>Thu, 28 Dec 2023 18:36:20 +0000</updated>
                                            <version>2.6.4</version>
                                                    <component>Text Search</component>
                                        <votes>133</votes>
                                    <watches>141</watches>
                                                                                                                <comments>
                            <comment id="4868704" author="JIRAUSER1271316" created="Fri, 30 Sep 2022 14:27:39 +0000"  >&lt;p&gt;Any progress on this? thi sis ciritcal feature for performace for non-english alphabet because &lt;b&gt;$diacriticSensitive&lt;/b&gt; cannot be attchieved with regex&lt;/p&gt;</comment>
                            <comment id="4323240" author="noone@supervoidrecords.com" created="Sat, 29 Jan 2022 21:48:15 +0000"  >&lt;p&gt;Hello. Any updates here? I don&apos;t see how search features are useful if there is no partial search. It&apos;s simply a requirement of any modern-day search engine.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;Any comment would be greatly appreciated. Thanks.&lt;/p&gt;</comment>
                            <comment id="4233905" author="ashfaqnisar00@gmail.com" created="Tue, 7 Dec 2021 06:23:13 +0000"  >&lt;p&gt;Any update on this issue ?&lt;/p&gt;</comment>
                            <comment id="4178810" author="JIRAUSER1263243" created="Tue, 9 Nov 2021 20:43:04 +0000"  >&lt;p&gt;This issue has been open for over 7 years. Is there any movement?&#160; I noticed that an open source fork of MongoDB called Percona has added this feature as an &quot;ngram&quot; language.&#160; &#160;See&#160;&lt;a href=&quot;https://docs.percona.com/percona-server-for-mongodb/4.4/ngram-full-text-search.html&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://docs.percona.com/percona-server-for-mongodb/4.4/ngram-full-text-search.html&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="4018458" author="JIRAUSER1269212" created="Tue, 24 Aug 2021 02:00:43 +0000"  >&lt;p&gt;This would be a great feature.&lt;/p&gt;</comment>
                            <comment id="3208426" author="doug.tarr" created="Mon, 15 Jun 2020 16:54:23 +0000"  >&lt;p&gt;Hi Cassio - You can filter in Atlas Search to your tenant by using a &lt;a href=&quot;https://docs.atlas.mongodb.com/reference/atlas-search/compound/#filter&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;compound filter query&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;You would need to add your tenant id to your Atlas Search index to make this work.&lt;/p&gt;</comment>
                            <comment id="3207036" author="cassio@intakeq.com" created="Sat, 13 Jun 2020 12:03:11 +0000"  >&lt;p&gt;I don&apos;t think any of the solutions offered by MongoDB works well for a simple scenario: implementing a quick search with autocomplete on multiple fields (name, email, phone number). For this&#160;to work, we need partial matches, but text indexes don&apos;t support partial matches. So we looked into Atlas Search, but since the search needs to be the first stage in the pipeline, it makes no sense to use it on a multi-tenant database. Are we missing something?&lt;/p&gt;</comment>
                            <comment id="3022031" author="admin@hivepoint.com" created="Wed, 1 Apr 2020 21:38:11 +0000"  >&lt;p&gt;FYI, it&apos;s really easy to add your own ngram support.&#160; Just add an extra field to the document containing an array of ngrams of the words in your searchable text.&#160; (It&apos;s trivial to generate ngrams for any string.)&#160; &#160;Then add that ngrams field into your text search index (with a lower weighting than the other fields).&#160; We&apos;ve been doing this for more than a year and it works great.&lt;/p&gt;</comment>
                            <comment id="3021899" author="doug.tarr" created="Wed, 1 Apr 2020 20:36:30 +0000"  >&lt;p&gt;Hi Jason -&lt;/p&gt;

&lt;p&gt;ngrams are definitely something we are working on in our near-term roadmap.&#160; &#160; &#160;We don&apos;t yet have a date for that feature however.&lt;/p&gt;

&lt;p&gt;In the meantime, you can vote for the features that are important to you on our uservoice site:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://mongodb.uservoice.com/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://mongodb.uservoice.com/&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="3021865" author="jason.benassi@verizondigitalmedia.com" created="Wed, 1 Apr 2020 20:18:48 +0000"  >&lt;p&gt;Hi Timothy and team -&#160;&lt;/p&gt;

&lt;p&gt;We work with James Kovaks and made him aware of the need for us to also request the partial/fuzzy text search (ngram) functionality. Any idea when you guys might be implementing this in Atlas Search? Our current project has it as a requirement. We are looking to work around it but the options are not great - e.g. transforming/syncing with ES. It would be nice to just be able to use these features directly in MongoDB. It seems since you have enabled other lucene analyzers, is it a large lift to enable ngram type patterns/results?&lt;/p&gt;</comment>
                            <comment id="3002571" author="mystackoverflow@gmail.com" created="Thu, 26 Mar 2020 16:00:57 +0000"  >&lt;p&gt;We need this feature in an on-premises solution. We have a quick search in our application that scans fields like first name, last name, date of birth, street, zip code, etc.. A text index is perfect for this. But when the user enters something into the quick search, the results should be displayed immediately. For this use case we need the possibility to search for prefixes, too. &lt;/p&gt;

&lt;p&gt;Other solutions are just hacks which unnecessarily pollute the data model and increase the data volume. We do not want to setup and maintain additional software like Elastic Search or Solr for such a fundamental feature. &lt;/p&gt;

&lt;p&gt;Unfortunately this feature is only available in Atlas. However, this feature is very important for our application, because our customers are already using it intensively in other applications (with other databases). Due to Google and co this kind of search is expected by our customers. &lt;/p&gt;

&lt;p&gt;We would appreciate it very much if this feature would also be available on-prem. Of course we would like to participate in further discussions. We are also looking forward to further ideas on how we can implement our requirements correctly. &lt;/p&gt;

&lt;p&gt;Unfortunately a contribution under &lt;a href=&quot;https://mongodb.canny.io/searchbeta&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://mongodb.canny.io/searchbeta&lt;/a&gt; is no longer possible, because the link is not valid anymore.&lt;/p&gt;</comment>
                            <comment id="2328934" author="tim.frietas" created="Tue, 16 Jul 2019 15:57:01 +0000"  >&lt;p&gt;There are no plans to support $searchBeta for on-prem installations and FTS is currently planned to be an Atlas-only feature indefinitely.&lt;/p&gt;

&lt;p&gt;As with all features during beta we are considering the overall experience and future scope and welcome feedback and the opportunity to have conversations with customers who are seeking an on-prem solution to better understand their needs and inform our future roadmap.&lt;/p&gt;

&lt;p&gt;We welcome feature requests and suggestions for Atlas Search. You can create and upvote feature requests or suggestions here:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://mongodb.uservoice.com/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://mongodb.uservoice.com/&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="2328018" author="kss160992" created="Tue, 16 Jul 2019 05:15:22 +0000"  >&lt;p&gt;Hi Timothy&lt;/p&gt;

&lt;p&gt;Is the full-text search coming to on premise mongodb instances or only Atlas?&lt;/p&gt;</comment>
                            <comment id="2327727" author="tim.frietas" created="Mon, 15 Jul 2019 21:18:55 +0000"  >&lt;p&gt;Our new Full Text Search feature is now in beta (using the $searchBeta operator).&lt;/p&gt;

&lt;p&gt;While the feature is Atlas-only and does not yet support all cluster sizes (it is currently only supported in M30 cluster sizes and above), we are working on both expanding hardware support and extending functionality.&lt;/p&gt;

&lt;p&gt;Many of the use cases described here are already supported in the beta.  Please see &lt;a href=&quot;https://docs.atlas.mongodb.com/reference/full-text-search/term/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://docs.atlas.mongodb.com/reference/full-text-search/term/&lt;/a&gt; for more info.&lt;/p&gt;

&lt;p&gt;If you want to try out a Full Text Search on a cluster of your own you can use credit activation code MONGODB4DOT2 for $200 of Atlas credit to get started.&lt;/p&gt;</comment>
                            <comment id="2314774" author="angieduan" created="Mon, 8 Jul 2019 05:37:00 +0000"  >&lt;p&gt;This should be the feature that needed by almost everyone, so is there a plan for this?&lt;/p&gt;

&lt;p&gt;Match with regex is&#160;extremely slow on big collections...&lt;/p&gt;</comment>
                            <comment id="2211627" author="admin@hivepoint.com" created="Fri, 12 Apr 2019 17:35:42 +0000"  >&lt;p&gt;FYI, we have a similar need and solved this problem by creating an additional field in the record that includes ngrams for each of the words in the text field(s).&#160; (If you&apos;re not familiar with n-grams, they are trivial &#8211;&#160; just all of the partial word substrings of each word.&#160; See&#160;&lt;a href=&quot;https://en.wikipedia.org/wiki/N-gram&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://en.wikipedia.org/wiki/N-gram&lt;/a&gt;.)&#160; This new field is added as an additional field in the full-text index.&lt;/p&gt;

&lt;p&gt;This works great for us and solves the &quot;as-you-type&quot; problem.&#160; Obviously, it adds a significant amount of text in the index, but in our case this isn&apos;t a problem.&#160; (We are also careful about only including unique n-grams and limiting their length.)&#160;&lt;/p&gt;</comment>
                            <comment id="2137267" author="ygbr@mac.com" created="Mon, 4 Feb 2019 20:38:00 +0000"  >&lt;p&gt;up!&lt;/p&gt;</comment>
                            <comment id="2035260" author="chilveri" created="Thu, 18 Oct 2018 16:06:19 +0000"  >&lt;p&gt;I have been searching in google to fix similar issue in Mongo DB. I have been developing couple of APIs in my company where we have search criteria on partial key word. Please release this feature soon.&lt;/p&gt;</comment>
                            <comment id="1967277" author="dandelaney8" created="Mon, 6 Aug 2018 02:25:42 +0000"  >&lt;p&gt;I just signed up for this to comment on this issue - we have a lot of search happening on our website and this would be super helpful. Please make this happen soon!&lt;/p&gt;</comment>
                            <comment id="1959500" author="themacboy72@gmail.com" created="Sun, 29 Jul 2018 16:58:29 +0000"  >&lt;p&gt;Important for me too&lt;/p&gt;</comment>
                            <comment id="1802152" author="fatmatto" created="Sun, 11 Feb 2018 10:38:10 +0000"  >&lt;p&gt;I think this feature is really important.&lt;/p&gt;

&lt;p&gt;I&apos;ve personally built several APIs for various companies and products all backed by MongoDB and the single issue i&apos;ve had is the lack of this feature.&lt;/p&gt;

&lt;p&gt;Sometimes you can settle with $regex, but not everytime.&lt;/p&gt;

&lt;p&gt;Even simple SaaS APIs need partial word matching on a full text index and the current solution is to use software like Elasticsearch or Solr in combination with mongodb, which really makes costs go up for smaller companies (more servers / more training / hire an expert)&lt;/p&gt;</comment>
                            <comment id="1755581" author="dsyrstad" created="Tue, 19 Dec 2017 14:22:13 +0000"  >&lt;p&gt;+1 This request would come close to satisfying our needs, but what would really be great is the Lucene/Solr/Elasticsearch wildcard capability: &lt;a href=&quot;https://lucene.apache.org/core/2_9_4/queryparsersyntax.html#Wildcard%20Searches&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://lucene.apache.org/core/2_9_4/queryparsersyntax.html#Wildcard%20Searches&lt;/a&gt;.&lt;br/&gt;
We currently run Solr in parallel with the DB to fulfill these features (plus others like fuzzy and proximity searches).&lt;/p&gt;</comment>
                            <comment id="1742719" author="sunilksamanta" created="Tue, 5 Dec 2017 12:41:49 +0000"  >&lt;p&gt;Stuck at this point. This is seriously needed. &lt;img class=&quot;emoticon&quot; src=&quot;https://jira.mongodb.org/images/icons/emoticons/sad.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/p&gt;</comment>
                            <comment id="1624823" author="ygbr@mac.com" created="Tue, 18 Jul 2017 15:48:59 +0000"  >&lt;p&gt;+42. This is one of the main reasons a lot of people needs to spin up elasticsearch/solr instances together with mongo. Having partial word support would allow the vast majority of full text searching cases to be handled directly by mongo since there&apos;s already support for stemming, tokenization and search scoring.&lt;/p&gt;</comment>
                            <comment id="1577489" author="eduardbosch" created="Tue, 23 May 2017 09:31:10 +0000"  >&lt;p&gt;Maybe an actual solution could be to implement in our databases this explanation &lt;b&gt;&lt;em&gt;Keywords &#8211; partial (and case insensitive) searches&lt;/em&gt;&lt;/b&gt; in the following article?&lt;br/&gt;
&lt;a href=&quot;http://jam.sg/blog/efficient-partial-keyword-searches/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://jam.sg/blog/efficient-partial-keyword-searches/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;This could help indexing texts and search efficiently by multiple keywords with partial insensitive searches.&lt;/p&gt;</comment>
                            <comment id="1230777" author="fresheneesz" created="Fri, 8 Apr 2016 20:38:05 +0000"  >&lt;p&gt;Yes please, this is what I expected the text search query to do by default. I&apos;m disappointed this doesn&apos;t exist yet : /&lt;/p&gt;</comment>
                            <comment id="748417" author="liddellj" created="Fri, 24 Oct 2014 14:05:45 +0000"  >&lt;p&gt;I have also found the full-text search support lacking in this area. In my case, we have an application for managing customer data which is stored in Mongo. Our search covers various fields within the customer collection including the name, email and postcode.&lt;/p&gt;

&lt;p&gt;Let&apos;s assume that I have a customer document that looks something like this:&lt;br/&gt;
{&lt;br/&gt;
    name: null,&lt;br/&gt;
    email: &apos;joebloggs@blah.com,&lt;br/&gt;
    postCode: &apos;1234&apos;&lt;br/&gt;
}&lt;/p&gt;

&lt;p&gt;With a text index over these fields, I would ideally like a search for &apos;joe bloggs&apos; to match the above document. However, as it stands, this does not work. It &lt;b&gt;would&lt;/b&gt; work if the email address happened to be in the form &apos;joe.bloggs@blah.com&apos; because the &apos;.&apos; characters causes the separate components to be indexed as separate words, but this is not always the case.&lt;/p&gt;

&lt;p&gt;Supporting regular expressions when using text search would solve this:&lt;br/&gt;
    db.customers.find({ $text: &lt;/p&gt;
{ $search: /bloggs/ }
&lt;p&gt; })&lt;/p&gt;

&lt;p&gt;As would some kind of additional option:&lt;br/&gt;
    db.customers.find({ $text: { $search: &apos;bloggs&apos;, $options: &lt;/p&gt;
{ partial: true }
&lt;p&gt; } })&lt;/p&gt;

&lt;p&gt;Without this, I have dropped back to indexing the fields individually (a compound index does not appear to work for our queries), and am relying on index intersection to satisfy the queries. Another option I spiked out was to follow the approach described at &lt;a href=&quot;http://docs.mongodb.org/manual/tutorial/model-data-for-keyword-search/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://docs.mongodb.org/manual/tutorial/model-data-for-keyword-search/&lt;/a&gt;, and maintain a keywords property against each document. Into the keywords property I added all possible sub-strings (above 2 characters) of the fields I was interested in. I could then create a single field index against the keywords field, and execute queries against that field alone. This worked (and gives faster performance than index intersection with regex queries), but I wasn&apos;t comfortable pushing the responsibility of managing keywords into the application, where this feels like it is a responsibility of the data storage technology. Supporting partial matches on full text search would negate the need for this at all.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="147979">SERVER-14621</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                                        </outwardlinks>
                                                                <inwardlinks description="is related to">
                                        <issuelink>
            <issuekey id="18266">SERVER-3260</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>27.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                <customfield id="customfield_12751" key="com.atlassian.jira.plugin.system.customfieldtypes:multiselect">
                        <customfieldname>Assigned Teams</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="25467"><![CDATA[Query Integration]]></customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_13552" key="com.go2group.jira.plugin.crm:crm_generic_field">
                        <customfieldname>Case</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[[500A000000a8KTWIA2, 500A000000aPJFwIAO, 5002K00000ejcMzQAI, 5002K00000hTtAcQAK, 5002K00000gf76vQAA, 5002K00000jdVTHQA2, 5002K00000uGVY2QAO, 5002K000010I6RMQA0, 5006R00001pknNsQAI]]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Fri, 24 Oct 2014 14:05:45 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        1 year, 18 weeks, 5 days ago
    
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18254" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Dependencies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[]]></customfieldvalue>


                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10057" key="com.atlassian.jira.toolkit:lastusercommented">
                        <customfieldname>Last comment by Customer</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>true</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10056" key="com.atlassian.jira.toolkit:lastupdaterorcommenter">
                        <customfieldname>Last commenter</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>ted.tuckman@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            1 year, 18 weeks, 5 days ago
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                    <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>aaronmotacek@gmail.com</customfieldvalue>
            <customfieldvalue>mystackoverflow@gmail.com</customfieldvalue>
            <customfieldvalue>angieduan</customfieldvalue>
            <customfieldvalue>ashfaqnisar00@gmail.com</customfieldvalue>
            <customfieldvalue>backlog-query-integration</customfieldvalue>
            <customfieldvalue>fresheneesz</customfieldvalue>
            <customfieldvalue>cassio@intakeq.com</customfieldvalue>
            <customfieldvalue>ctmay4@gmail.com</customfieldvalue>
            <customfieldvalue>dandelaney8</customfieldvalue>
            <customfieldvalue>dsyrstad</customfieldvalue>
            <customfieldvalue>doug.tarr@mongodb.com</customfieldvalue>
            <customfieldvalue>eduardbosch</customfieldvalue>
            <customfieldvalue>Chilveri</customfieldvalue>
            <customfieldvalue>admin@hivepoint.com</customfieldvalue>
            <customfieldvalue>jason.benassi@verizondigitalmedia.com</customfieldvalue>
            <customfieldvalue>liddellj</customfieldvalue>
            <customfieldvalue>noone@supervoidrecords.com</customfieldvalue>
            <customfieldvalue>globegitter</customfieldvalue>
            <customfieldvalue>fatmatto</customfieldvalue>
            <customfieldvalue>themacboy72@gmail.com</customfieldvalue>
            <customfieldvalue>kss160992</customfieldvalue>
            <customfieldvalue>sunilksamanta</customfieldvalue>
            <customfieldvalue>tim.frietas@mongodb.com</customfieldvalue>
            <customfieldvalue>vytasbboy@gmail.com</customfieldvalue>
            <customfieldvalue>ygbr@mac.com</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hrloun:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hr2dnz:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>135145</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_23361" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Requested By</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_22870" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Triagers</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_14350" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>serverRank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hrpgfj:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>