Skip to content

Terms with filters #37

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
clintongormley opened this issue Feb 22, 2010 · 5 comments
Closed

Terms with filters #37

clintongormley opened this issue Feb 22, 2010 · 5 comments

Comments

@clintongormley
Copy link
Contributor

For auto-suggest, it would be nice to be able to ask for (eg) all terms with prefix 'sch' that occur in the same document as 'arnold'
@kimchy
Copy link
Member

kimchy commented Feb 22, 2010

Can you give a more concrete example? When you say document arnold, is that the id of the document, or actually a query?

I do plan to add a more like this option, where (in one case) you would give the document id, and all the documents that are like the document will be returned.

@clintongormley
Copy link
Contributor Author

That's nice too, but not what I mean.

Think about google's auto suggest.

The user starts typing "ar", possible matches are 'arnold' 'arnaud', 'argentinia' etc

If the user starts typing 'sch', possible matches are 'schwab', 'schweitz', 'schwarzenegger'

But if the user types "arnold sch" then the likeliest match is "schwarzenegger"

So it'd be nice to say: give me all the terms starting with $prefix, in documents that contain [$token_1, $token_n]

@kimchy
Copy link
Member

kimchy commented Feb 22, 2010

Yes, now I understand what you mean. Thats a more complex autosuggest, which can be done in several ways, not just the one you mentioned (for example, google uses the queries users enter for auto suggest, which I think is far better).

@clintongormley
Copy link
Contributor Author

sure - agreed

@clintongormley
Copy link
Contributor Author

Now implemented with search facets in 0.9

@bluelu bluelu mentioned this issue Dec 11, 2014
Closed
dadoonet added a commit that referenced this issue Jun 5, 2015
@dadoonet
Merge pull request #37 from ryansb/readmeDeprecateS3Gateway
3c23373 
Add note that the S3 Gateway will be deprecated
dadoonet added a commit that referenced this issue Jun 5, 2015
@dadoonet
Update to Lucene 4.9.0
19697b2 
Closes #37.

(cherry picked from commit 5243bdc)
dadoonet added a commit that referenced this issue Jun 5, 2015
@dadoonet
BlobContainer interface changed in elasticsearch 1.4.0
6d5ac76 
AWS plugin needs an update because of this change #7551

Closes #37.
@donkoink donkoink mentioned this issue Jun 25, 2015
Closed
@makeyang makeyang mentioned this issue Sep 7, 2015
Closed
rmuir pushed a commit to rmuir/elasticsearch that referenced this issue Nov 8, 2015
@dadoonet
Mapper plugin overwrites multifield mapping
d7a2e7e 
If you define some specific mapping for your file content, such as the following:

```javascript
{
    "person": {
        "properties": {
            "file": {
                "type": "attachment",
                "path": "full",
                "fields": {
                    "file": {
                        "type": "multifield",
                        "fields": {
                            "file": { "type": "string" },
                            "suggest": { "type": "string" }
                        }
                    }
                }
            }
        }
    }
}
```

And then, if you ask back the mapping, you get:

```javascript
{
   "person":{
      "properties":{
         "file":{
            "type":"attachment",
            "path":"full",
            "fields":{
               "file":{
                  "type":"string"
               },
               "author":{
                  "type":"string"
               },
               "title":{
                  "type":"string"
               },
               "name":{
                  "type":"string"
               },
               "date":{
                  "type":"date",
                  "format":"dateOptionalTime"
               },
               "keywords":{
                  "type":"string"
               },
               "content_type":{
                  "type":"string"
               }
            }
         }
      }
   }
}
```

All your settings have been overwrited by the mapper plugin.

Closes elastic#37.
@burtonator burtonator mentioned this issue May 13, 2016
Closed
njlawton pushed a commit to njlawton/elasticsearch that referenced this issue Mar 15, 2017
@kblincoe
Merge pull request elastic#37 from IanvsPoplicola/coordination_#22768
ec1a13f 
Request to update Coordination.md
@BradHarris BradHarris mentioned this issue Oct 11, 2017
Closed
@chakravarthy392 chakravarthy392 mentioned this issue Aug 29, 2018
Closed
@Katulus Katulus mentioned this issue Sep 17, 2018
Closed
@robin13 robin13 mentioned this issue Sep 26, 2018
Closed
@tKe tKe mentioned this issue Dec 11, 2018
Closed
@wlsaud619 wlsaud619 mentioned this issue Apr 11, 2019
Closed
henningandersen pushed a commit to henningandersen/elasticsearch that referenced this issue Jun 4, 2020
@danielmitterdorfer
Cleanup and tests
930f891 
With this commit we remove some dead code, simplify the existing random
generator and also add test infrastructure and an example test for the timestamp
generator.

Relates elastic#37
@bnprss bnprss mentioned this issue Jul 15, 2021
Open
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
@danielmitterdorfer
Add legend for release benchmarks
19248da 
Closes elastic#37
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kimchy @clintongormley