[
https://issues.apache.org/jira/browse/PARQUET-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14363743#comment-14363743
]
Alex Levenson commented on PARQUET-218:
---------------------------------------
How would we want to handle the case where the macro can't really tell what's
going on in the closure?
The more we make the closure look like a plain chunk of any scala code, the
more confusing it's going to be to users when no, actually, only a tiny subset
of valid scala can go here.
> Macro based Scala APIs for Predicate and Projection push down
> -------------------------------------------------------------
>
> Key: PARQUET-218
> URL: https://issues.apache.org/jira/browse/PARQUET-218
> Project: Parquet
> Issue Type: Improvement
> Components: parquet-mr
> Reporter: Julien Le Dem
>
> There has been some experiments with Scala macros to make Predicate and
> Projection APIs in Scala.
> In particular by [~neville]:
> https://github.com/nevillelyh/parquet-avro-extra/blob/master/parquet-avro-examples/src/main/scala/me/lyh/parquet/avro/examples/ExampleApp.scala
> https://github.com/nevillelyh/parquet-avro-extra/commit/090f8d1d1d7d44489bb71e04465d4a12a46432c9#diff-89dca6adcdf105c6063661de43931c29R15
> There have also been some discussion at Twitter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
