Task #102975
closed
Use full md5 hash for `indexed_search`
Added by Stefan Bürk 4 months ago.
Updated 4 months ago.
Description
For `ext:indexed_search` not only a cumbersome md5 to int
conversion has been used. The original md5 length has been
reduced by simply cutting of values from the end combined
with a `hexdec` conversion, leading to a highly increased
conflict propability (duplicate keys) for several places.
To mitigate this, the raw md5 hash should be used instead
of the reduced integer representation.
- Related to Bug #84541: Uncaught TYPO3 Exception in indexed_search: duplicate key (hash) error added
- Related to Bug #90977: possible race condition in indexedsearch added
- Related to Bug #87138: indexed_search: Duplicate entry for key 'Primary' in index_rel added
- Status changed from New to Under Review
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Closed
- Related to Task #103312: Document database changes for md5 hash added
- Related to Bug #103541: Validation failed while trying to call TYPO3\CMS\IndexedSearch\Controller\AdministrationController->statisticDetailsAction(). added
- Related to Bug #103543: indexed_search: Cannot save stopwords in "Words by top count" and "Words by frequency" added
- Related to deleted (Bug #103543: indexed_search: Cannot save stopwords in "Words by top count" and "Words by frequency")
- Related to Bug #103547: indexed_search: Link to word details fails added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by