Any documents with the same uri and digest (in other words an unchanged item) share the same record and have multiple values for the snapshot date.Given two snapshot dates, we want to find the following four things.One way to do this would be to declare a multivalued stored and indexed field.Then you can use its values in a search query just like a SQL JOIN.Solr by dasnom - Pearltrees [...] Lucid Imagination » Nested Queries in Solr To embed a query of another type in a Lucene/Solr query string, simply use the magic field name _query_ .The following example embeds a lucene query type:poems into another lucene query: text:"roses are red" AND _query_:"type:poems" Nested Queries in Lucene Syntax Now of course this isn’t too useful on it’s own, but it becomes very powerful in conjunction with the query parser framework and local params which allows us to change the types of queries.The ability to nest an arbitrary query type inside another query type is a useful feature that was quietly added to Solr some time ago, along with the support for query parser plugins to support different query types.
(job is snapshot id for what happened on a certain date).
For example, the following allows an easy way for the client to specify that they want some sort of recency date boost added into the relevancy score, while leaving the exact query type up to the Solr server config (via search handler defaults in solrconfig.xml) The client query would specify the boost query as $datefunc: The same idea could be used to allow a client to switch between complex filters, without having to specify what those filters are.
Without the nested query parser type, it would only be possible to specify the query value in a separate place (via local params v=$param) not the type also.
What I'm really looking for is comparing two sets of results with something like WHERE result1= result2AND result1.digest !
= result2.digest (the first part of this where is just a JOIN moved into the WHERE clause).