[GitHub] [beam] kennknowles opened a new issue, #18761: Method chaining order matters for BigQueryIO.readTableRows() and usingStandardSql()

[GitBox <gi...@apache.org>]

kennknowles opened a new issue, #18761:
URL: https://github.com/apache/beam/issues/18761

   Depending on the order of the method calls you use in the fluent API for BigQueryIO.readTableRows() you'll either successfully execute a query requiring standard SQL or get an error indicating that you tried something incompatible with legacy SQL.
   
   Works: 
   ```
   
   p.apply("Read rows will succeed", BigQueryIO.readTableRows().fromQuery(query.toString()).usingStandardSql());
   
   ```
   
   Fails with a 400:
   ```
   
   p.apply("Read rows will fail", BigQueryIO.readTableRows().usingStandardSql().fromQuery(query.toString()));
   
   ```
   
   Error message (edited to anonymize): 
   
   "Invalid table name: `<project\>:<dataset\>.<table\>`\n[Try using standard SQL ([https://cloud.google.com/bigquery/docs/reference/standard-sql/enabling-standard-sql)](Try using standard SQL ([https://cloud.google.com/bigquery/docs/reference/standard-sql/enabling-standard-sql)).]
   
    
   
   I wouldn't expect a fluent API to care about the ordering of the clauses. Even if a specific order were required, I would expect a more informative error message with a link to a grammar ... 
   
    
   
   See here for a complete example:
   
   https://github.com/pbrumblay/bigqueryioproblems/blob/master/src/main/java/com/fearlesstg/UsingStandardSQLOrderMatters.java
   
    
   
   Imported from Jira [BEAM-4363](https://issues.apache.org/jira/browse/BEAM-4363). Original Jira may contain additional context.
   Reported by: pbrumblay.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org