Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/10341#issuecomment-165963733
Hey @HyukjinKwon, actually I hit the same issue for testing
`AND`/`OR`/`NOT` while working on #10377, and at last I resorted to
`SearchArgument.toString`, which produces quite structured and readable string
representation of a `SearchArgument`. Although a little bit clunky, it turned
out to be quite effective. However, note that ORC tries to "unify" comparison
operators. For example, all `>` are transformed to `<=` wrapped by a `not` in
the final string representation.
Please refer to [this file][1] for details.
[1]:
https://github.com/apache/spark/pull/10377/files#diff-51d62db1a740ae845fc2797b7f551a8cR179
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
