On Oct 31, 2007, at 10:04 AM, Brian Carmalt wrote:
There is more to consider here. Lucene now supports "payloads",
additional metadata on terms that can be leveraged with custom
queries. I've not yet tinkered with them myself, but my
understanding is that they would be useful (and in fact
There is more to consider here. Lucene now supports "payloads",
additional metadata on terms that can be leveraged with custom
queries. I've not yet tinkered with them myself, but my understanding
is that they would be useful (and in fact designed in part) for
representing structured docume
As it happens, I put together an app that indexes books and
wrestled with this issue. NOTE: this was NOT solr, just straight
Lucene but I think my experience may apply. Also, I haven't
followed this entire thread, so I may be irrelevant...
First, the question of spanning across pages certainly was
On Oct 18, 2007, at 11:53 AM, Binkley, Peter wrote:
I think the requirements I mentioned in a comment
(https://issues.apache.org/jira/browse/SOLR-380#action_12535296)
justify
abandoning the one-page-per-document approach. The increment-gap
approach would break the cross-page searching, and wo
I echo the apology for using JIRA to work out ideas on this.
Just thinking out loud here:
* Is there any reason why the page id should be an integer? I mean
could the page identifier be an alphanumeric string?
* Ideally our project would like to store some page level meta-data
(e
Sent: Wednesday, October 17, 2007 4:26 PM
To: Binkley, Peter
Subject: [jira] Commented: (SOLR-380) There's no way to convert search
results into page-level hits of a "structured document".
[
https://issues.apache.org/jira/browse/SOLR-380?page=com.atlassian.jira.p
lugin.system.is
