How to implement Solr's facet.missing=true with Lucene
Solr supports returning the number of matching documents with no facet value for the field. How can the same be achieved with Lucene?
Example: I have 5 documents that may have values for the a field category
- Document 1 has
category=A
- Document 2 has
category=A
andcategory=B
- Document 3 has
category=B
andcategory=C
- Document 4 and 5 have no
category
values
The code looks like
var facetsCollector = new FacetsCollector();
FacetsCollector.Search(_indexSearcher, new MatchAllDocsQuery(), 100, facetsCollector);
var state = DefaultSortedSetDocValuesReaderState(_indexReader, "category_facet");
var facets = SortedSetDocValuesFacetCounts(state, facetsCollector);
var children = facets.GetTopChildren(100, "category_dim");
This gives me LabelValues
- Label:A, Value:2
- Label:B, Value:2
- Label:C, Value:1
How can I determine "Label:(missing), Value:2"?
Running another query +*:* -category:*
is an obvious option. However, can it be done in a smarter way?
lucene facet
add a comment |
Solr supports returning the number of matching documents with no facet value for the field. How can the same be achieved with Lucene?
Example: I have 5 documents that may have values for the a field category
- Document 1 has
category=A
- Document 2 has
category=A
andcategory=B
- Document 3 has
category=B
andcategory=C
- Document 4 and 5 have no
category
values
The code looks like
var facetsCollector = new FacetsCollector();
FacetsCollector.Search(_indexSearcher, new MatchAllDocsQuery(), 100, facetsCollector);
var state = DefaultSortedSetDocValuesReaderState(_indexReader, "category_facet");
var facets = SortedSetDocValuesFacetCounts(state, facetsCollector);
var children = facets.GetTopChildren(100, "category_dim");
This gives me LabelValues
- Label:A, Value:2
- Label:B, Value:2
- Label:C, Value:1
How can I determine "Label:(missing), Value:2"?
Running another query +*:* -category:*
is an obvious option. However, can it be done in a smarter way?
lucene facet
add a comment |
Solr supports returning the number of matching documents with no facet value for the field. How can the same be achieved with Lucene?
Example: I have 5 documents that may have values for the a field category
- Document 1 has
category=A
- Document 2 has
category=A
andcategory=B
- Document 3 has
category=B
andcategory=C
- Document 4 and 5 have no
category
values
The code looks like
var facetsCollector = new FacetsCollector();
FacetsCollector.Search(_indexSearcher, new MatchAllDocsQuery(), 100, facetsCollector);
var state = DefaultSortedSetDocValuesReaderState(_indexReader, "category_facet");
var facets = SortedSetDocValuesFacetCounts(state, facetsCollector);
var children = facets.GetTopChildren(100, "category_dim");
This gives me LabelValues
- Label:A, Value:2
- Label:B, Value:2
- Label:C, Value:1
How can I determine "Label:(missing), Value:2"?
Running another query +*:* -category:*
is an obvious option. However, can it be done in a smarter way?
lucene facet
Solr supports returning the number of matching documents with no facet value for the field. How can the same be achieved with Lucene?
Example: I have 5 documents that may have values for the a field category
- Document 1 has
category=A
- Document 2 has
category=A
andcategory=B
- Document 3 has
category=B
andcategory=C
- Document 4 and 5 have no
category
values
The code looks like
var facetsCollector = new FacetsCollector();
FacetsCollector.Search(_indexSearcher, new MatchAllDocsQuery(), 100, facetsCollector);
var state = DefaultSortedSetDocValuesReaderState(_indexReader, "category_facet");
var facets = SortedSetDocValuesFacetCounts(state, facetsCollector);
var children = facets.GetTopChildren(100, "category_dim");
This gives me LabelValues
- Label:A, Value:2
- Label:B, Value:2
- Label:C, Value:1
How can I determine "Label:(missing), Value:2"?
Running another query +*:* -category:*
is an obvious option. However, can it be done in a smarter way?
lucene facet
lucene facet
asked Nov 19 '18 at 12:19
Paul B.
1,7301839
1,7301839
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Solr facet.missing
functionality is done without any collectors by just doing this:
SchemaField sf = searcher.getSchema().getField(fieldName);
DocSet hasVal = searcher.getDocSet(sf.getType().getRangeQuery(null, sf, null, null, false, false));
return docs.andNotSize(hasVal);
which basically means - use the docset that was provided earlier by the search, get another docset by running range query which is finding only documents with missing values and then applying simple boolean operation.
Unfortunately, Lucene doesn't have built-in DocSet functionality so it would require some tricks. I could come up with something like this:
Query q = some Lucene query
Set<Integer> queryRes = new HashSet<>();
searcher.search(q, new CheckHits.SetCollector(queryRes));
Set<Integer> missingRes = new HashSet<>();
searcher.search(new TermRangeQuery("category", null, null, false, false), new CheckHits.SetCollector(missingRes));
missingRes.retainAll(queryRes);
System.out.println(missingRes.size());
HashSet retain functionality should be pretty okay in terms of speed. If further needed, this collector could be extended to store ids in somewhere more efficient way
Full example could be found there
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53374492%2fhow-to-implement-solrs-facet-missing-true-with-lucene%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Solr facet.missing
functionality is done without any collectors by just doing this:
SchemaField sf = searcher.getSchema().getField(fieldName);
DocSet hasVal = searcher.getDocSet(sf.getType().getRangeQuery(null, sf, null, null, false, false));
return docs.andNotSize(hasVal);
which basically means - use the docset that was provided earlier by the search, get another docset by running range query which is finding only documents with missing values and then applying simple boolean operation.
Unfortunately, Lucene doesn't have built-in DocSet functionality so it would require some tricks. I could come up with something like this:
Query q = some Lucene query
Set<Integer> queryRes = new HashSet<>();
searcher.search(q, new CheckHits.SetCollector(queryRes));
Set<Integer> missingRes = new HashSet<>();
searcher.search(new TermRangeQuery("category", null, null, false, false), new CheckHits.SetCollector(missingRes));
missingRes.retainAll(queryRes);
System.out.println(missingRes.size());
HashSet retain functionality should be pretty okay in terms of speed. If further needed, this collector could be extended to store ids in somewhere more efficient way
Full example could be found there
add a comment |
Solr facet.missing
functionality is done without any collectors by just doing this:
SchemaField sf = searcher.getSchema().getField(fieldName);
DocSet hasVal = searcher.getDocSet(sf.getType().getRangeQuery(null, sf, null, null, false, false));
return docs.andNotSize(hasVal);
which basically means - use the docset that was provided earlier by the search, get another docset by running range query which is finding only documents with missing values and then applying simple boolean operation.
Unfortunately, Lucene doesn't have built-in DocSet functionality so it would require some tricks. I could come up with something like this:
Query q = some Lucene query
Set<Integer> queryRes = new HashSet<>();
searcher.search(q, new CheckHits.SetCollector(queryRes));
Set<Integer> missingRes = new HashSet<>();
searcher.search(new TermRangeQuery("category", null, null, false, false), new CheckHits.SetCollector(missingRes));
missingRes.retainAll(queryRes);
System.out.println(missingRes.size());
HashSet retain functionality should be pretty okay in terms of speed. If further needed, this collector could be extended to store ids in somewhere more efficient way
Full example could be found there
add a comment |
Solr facet.missing
functionality is done without any collectors by just doing this:
SchemaField sf = searcher.getSchema().getField(fieldName);
DocSet hasVal = searcher.getDocSet(sf.getType().getRangeQuery(null, sf, null, null, false, false));
return docs.andNotSize(hasVal);
which basically means - use the docset that was provided earlier by the search, get another docset by running range query which is finding only documents with missing values and then applying simple boolean operation.
Unfortunately, Lucene doesn't have built-in DocSet functionality so it would require some tricks. I could come up with something like this:
Query q = some Lucene query
Set<Integer> queryRes = new HashSet<>();
searcher.search(q, new CheckHits.SetCollector(queryRes));
Set<Integer> missingRes = new HashSet<>();
searcher.search(new TermRangeQuery("category", null, null, false, false), new CheckHits.SetCollector(missingRes));
missingRes.retainAll(queryRes);
System.out.println(missingRes.size());
HashSet retain functionality should be pretty okay in terms of speed. If further needed, this collector could be extended to store ids in somewhere more efficient way
Full example could be found there
Solr facet.missing
functionality is done without any collectors by just doing this:
SchemaField sf = searcher.getSchema().getField(fieldName);
DocSet hasVal = searcher.getDocSet(sf.getType().getRangeQuery(null, sf, null, null, false, false));
return docs.andNotSize(hasVal);
which basically means - use the docset that was provided earlier by the search, get another docset by running range query which is finding only documents with missing values and then applying simple boolean operation.
Unfortunately, Lucene doesn't have built-in DocSet functionality so it would require some tricks. I could come up with something like this:
Query q = some Lucene query
Set<Integer> queryRes = new HashSet<>();
searcher.search(q, new CheckHits.SetCollector(queryRes));
Set<Integer> missingRes = new HashSet<>();
searcher.search(new TermRangeQuery("category", null, null, false, false), new CheckHits.SetCollector(missingRes));
missingRes.retainAll(queryRes);
System.out.println(missingRes.size());
HashSet retain functionality should be pretty okay in terms of speed. If further needed, this collector could be extended to store ids in somewhere more efficient way
Full example could be found there
answered Dec 28 '18 at 15:22
Mysterion
5,90221942
5,90221942
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53374492%2fhow-to-implement-solrs-facet-missing-true-with-lucene%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown