It's bugged me for a while that we can't define any analysis on primitive types. This is especially acute with date types, we require a very exact format and have to tell people "transform it correctly on the ingestion side", or "create an custom update processor that transforms it".
I thought I remembered something about being able to do this, but can't find it. I suspect I was confusing it with DIH. What's the reason for primitive types being unanalyzed? Just "it's always been that way", or "it would lead to a very sticky wicket we never wanted to get stuck in"? Both are perfectly valid, I'm just sayin'. I realize this would provide some "interesting" output. Say you defined a regex for an int type that removed all non-numerics. If the input was "30asdf" and it was transformed correctly into 30 for the underlying int field, it would still come back as 30asdf from the stored data, but that's true about all analysis steps. Or perhaps you'd like to have a string of integers as input to a multiValued int field. Or.... Musings sparked by seeing this crop up again in another context. Erick --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
