fixed #1879: Add support for range filter

[zhxiaogg]

Currently it supports the following schema:

{
  "type": "between",
  "numerically": false,
  "upper": "abd",
  "lower": "abc"
}

The numerically field can be omitted and defaults to be false if both upper and lower are not numbers. It means the omitted field will be true if given:

{
  "type": "between",
  "upper": 1,
  "lower": 0.1
}

and will be false if given:

{
  "type": "between",
  "upper": "1",
  "lower": "0.1"
}

Also worth note:

1. the bounds to defaults to value <= upper && value >= lower and does NOT support configuration
2. string comparison are implemented use String#compareTo which is case sensitive.

Finally, I just finished coding and have NOT tested the code. Hopefully somebody could help to review this code and feed me back some suggestions.

[drcrallen]

Most boundaries in druid are "greater than or equal" on the lower and "less than" on the upper. Can you give some examples of if that would or would not work for this?

[drcrallen]

can be boolean in which case it will default to false

[drcrallen]

@zhxiaogg Have you seen #1936 ?

[zhxiaogg]

@drcrallen yes, i just noticed that... oops!

[zhxiaogg]

@drcrallen can you still review this code? I'll pick a new issue later.