Your client converts IP addresses to base64 strings before it indexes the documents, so it must also use the same conversion to a base64 string when querying the document.
Ranges are a little more complicated. For example. if you simply encode "9" and "111" as strings, then you cannot perform range queries, since "111" is less than "0", string-wise. In this case you must do something that ensures that "9" is less than "111", typically by creating fixed-length input strings before encoding; for example "009" and "111". Now the string comparisons will match the intended numeric comparisons. IP addresses will be more complex. But still, you will need to apply the same external conversions in front of your queries that you do in front of your indexing. Brian -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/893f0e01-388c-4350-8b8c-151a06ed8f59%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
