Minor Description
LuceneIndex currently provides a hardcoded cost of 10. This causes issue if on same system both old LuceneIndex and newer LucenePropertyIndex are configured as former would always win
To make comparison fair it should report accurate cost based on num of docs in index. Given that LuceneIndex is only used for fulltext queries it does not have to compete with other property index, it should be safe to provide accurate cost