I would argue this should be more like `setPlannerFactory()` taking either a 
`String` or `Constructor`. I like the `PipelineOptions` approach, I just don't 
think they belong in `BeamQueryPlanner`.

[ Full content available at: https://github.com/apache/beam/pull/6598 ]
This message was relayed via gitbox.apache.org for devnull@infra.apache.org

Reply via email to