Custom Attributes for User

[10年前 に venka reddy によって更新されました。]

Hi,

I have added custom attribute for the userEntity as string .

I need to make that string as searchable, so there is an option to make searchable as "As aText" "As a keyword".

So what is the difference between these 2 options? Which one will be more suitable?

[10年前 に Harish Kumar によって更新されました。]

AFAIK In case of As a Text input string will be subject to tokenization while parsed by lucene or solr. on the other hand in case of As a Keyword, Tokenizer does not split the input at all. No processing in performed on the string, and the whole string is treated as a single entity.

[10年前 に Vilmos Papp によって更新されました。]

Hi,

Do you mean a custom field, or you created an EXT plugin? If the first one, you can select the "Indexed" version of the field. If you are going to modify indexing, you should decide which search method to find the new field. If you use keyword then the simple search is fine for you. If you want the other way, then you have to modify the advanced search UI to meet your requirements.