Luke deGruchy ad71755c2b Resolve 5029 Token params with system and value longer than maximum length should be created and searched differently (#4998) ... * Partial implementation after this has been paused: Move trimming of value and system from BaseSearchParamExtractor to ResourceIndexedSearchParamToken. Do not throw Exceptions in TokenPredicateBuilder. Ensure that the hash computing in the search param token takes the 200+ token value into account. Other search param tokens are not yet implemented. * in ResourceIndexedSearchParamToken,changed hardcoded length to constant MAX_LENGTH; in BaseSearchParamExtractor, added check in createTokenIndexIfNotBlank so that the return value is null if system or value is blank. * added test for TokenPredicateBuilder to verify that long values exceeds the max length does not cause exception. added test in FhirSystemDaoR4SearchTest to verify searchParamToken with longer system and value than max length can be created successfully. And hash value will be calculated before truncation * fixed a logical error in previous commits * changed existing tests to accommodate for the changes * modified existing tests * added changelog * changed truncation method name and added comments Co-authored-by: michaelabuckley <michaelabuckley@gmail.com> * modified changelog Co-authored-by: michaelabuckley <michaelabuckley@gmail.com> * combined redundant tests --------- Co-authored-by: tyner <tyner.guo@smilecdr.com> Co-authored-by: TynerGjs <132295567+TynerGjs@users.noreply.github.com> Co-authored-by: michaelabuckley <michaelabuckley@gmail.com>		2023-06-30 10:48:33 -04:00
..
src	Resolve 5029 Token params with system and value longer than maximum length should be created and searched differently (#4998)	2023-06-30 10:48:33 -04:00
pom.xml	Bulk export partitioning fixes (#5039)	2023-06-29 08:34:32 -04:00