Task #1886
Check indexing behaviour
| Status: | Closed | Start date: | 2008-10-27 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assigned To: | Karsten Dambekalns | % Done: | 0% |
|
| Category: | Index/Search | |||
| Target version: | - | |||
| Sprint: |
Description
Make sure content can be searched tokenized and non-tokenized.
Related issues
Associated revisions
FLOW3, TYPO3CR:
TYPO3CR:
- Persistence: array keys are now preserved when persisting, fixes #1620
- Persistence: fixed error when persisting DateTime properties, fixes #2195
- changed the way properties are added to the Lucene index, fixes #1623, refs #1886
- fixed storage backend to enable use of namespaced nodetype names
- moved the KeywordAnalyser here from TYPO3CR
FLOW3:
- equality comparisons in persistence can now be done case-insensitive (in QueryInterface and Repository), refs #1884, refs #2811
- changed more use of PersistenceManager into PersistenceManagerInterface
- added support for case-insensitive equality comparison in QueryInterface implementation, fixes #2811
- implemented Literal, LowerCase, UpperCase in QOM
- reduced the number of tables used for storing properties by roughly 50%
- removed Lucene search backend
- added in-RDBMS property index and new search backend based on it, refs #1886
- removed Lucene package from Global packages
- removed install.sh, it was broken anyway
History
#1 Updated by Karsten Dambekalns almost 7 years ago
- Priority changed from Should have to Must have
- Target version set to 197
#2 Updated by Karsten Dambekalns about 6 years ago
- Status changed from New to Closed
- Assigned To set to Karsten Dambekalns
Indexing behaviour has changed radically, thus is outdated. We'll stumble over any issues anyway...
#3 Updated by Robert Lemke about 4 years ago
- Target version deleted (
197)