AnsweredAssumed Answered

How to force a field type to a string when it is first added to an index even though the field contains an integer value?

Question asked by kkancherla Employee on Apr 27, 2017
Latest reply on Apr 27, 2017 by Yury Kats

There is  some inconsistency the way a field types are displayed on the Discovered Fields tab during testing a pipeline vs Discovered Fields tab after a workflow completes vs Field type defined in the schema.

 

Example.

I have a tagging stage in a pipeline that tags a field named "stringer" with a value of "1234".

 

When i test the pipeline i see the type as STRING.

When i run the workflow i see the type as INT.

When i goto the index schema i see the type as tlongs.

I am aware that HCI determines the type of the field based on the value it sees, but in my case is it possible to force HCI to use String as the type even though the value is an integer?

Outcomes