boolean field should never be analyzed

Description

I just ran into some unexpected results when I tried to search on a boolean value. The field was annotated like so

Upon examination of the index I realized that the values were indexed as

in stead of

I never realized before that this could happen as it doesn't make any sense to analyze a boolean value string. It might have been something that changed over time. Anyway, I think it's a bug. It might even make sense to store a boolean value by default as a NumericField.

Adding Analyze.NO of course resolves the issues, but this shouldn't be necessary.

Environment

None

Assignee

Fabio Massimo Ercoli

Reporter

Marc Schipperheyn

Labels

None

Suitable for new contributors

None

Feedback Requested

None

Components

Fix versions

Priority

Major
Configure