@ayushn adobe released new feature AEM remote Spa with next js last year.. it is just awesome.. here you will use either react ssr or react csr with next js app and use aem editor functionalities as-is for content management.     https://experienceleague.adobe.com/docs/experience-manager-learn/getti...

Please refer to tokenizer section in the below blog post, there are already multiple tokenizers available.. why do you want to build custom one?   https://www.bounteous.com/insights/2018/06/07/aem-search-indexing-synonyms-filters-and-stop-words-oh-my

I know this old thread but did compaction solved your problem.

@reno1  as posted by @aanchal-sikka and @sherinregi it is not possible with custom git, please use Adobe git for the same...   @reno1 any reason why you dont want to use Adobe git?

@j408 have you seen https://www.aemcq5tutorials.com/tutorials/text-pre-extraction/ and https://www.tumblr.com/cq-ops/17803840654/how-to-extract-content-and-metadata-from-pdfs 

@chandrakanthim is this related to AEM? can you please post further details here?   @kautuk_sahni  please move to appropriate forum.

@veerareddyc1015 which version of aem are you using and service pack, also what's your acs commons version?

@gurpreetgill can you elaborate a bit more. How are you editing a pdf within AEM? Any screenshots?

@shubhanshu_singh how the property will be changed? automated or via some authoring?

@RobertHarperFS as you are upgrading from old aem to new aem version, just a suggestion that limit your jsp files and check for alternative ways to solve it. Also check for any new jsp which is present in new AEM version and check how taglibs are handled.