Custom Query (420 matches)
Results (34 - 36 of 420)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #848 | fixed | mgpp crash: bit buffer overrun | ||
| Description |
Diego had some very messy PDFs containing strings like fffffffff (x500ish) - which triggered word splitting at max_stem_len which is 255. Building an mgpp index would crash the build, with a bit buffer overrun. |
|||
| #845 | fixed | Searching a GS3 lucene collection with wildcards doesn't show terms | ||
| Description |
In GS2, searching a lucene collection displays information for possible search terms when the original search used a wildcard. This doesn't happen with a lucene collection in GS3. The disparity is owing to GS3's LuceneWrapper3.jar using version 3.3.0 of the lucene-core library, whereas GS2's LuceneWrapper.jar used lucene 2.3.2. E.g. when searching for econom* in a GS2 lucene containing the documents from Demo (as in the indexers tutorial), the search results start with: Word count: econometrics: 1, economique: 1, economist: 4, economical: 6, economists: 6, economically: 25, economics: 27, economies: 38, economy: 156, economic: 507 10 documents matched the query. The same search in GS3 however produces just the documents in the results list without the term information seen above. |
|||
| #844 | fixed | GS3: should search form remember previous search options? | ||
| Description |
At present, when I search for cat, it displays the results but resets all the fields (including the search field, empty of cat again), so that I can't tweak the existing search, but have to start all over again. Kathy thought this could be done with Javascript. |
|||
