On Wed, Jan 23, 2019 at 11:13 AM Alex Amato <ajam...@google.com> wrote:
> Okay, make sense perhaps we can somehow make it fail when it fails to > generate the dep, rather than when compiling the java code later on > That would be a good improvement on error message. :-) Or, does it make sense to manually check-in this particular error-prone auto-gen code until this issue is resolved? > > On Wed, Jan 23, 2019 at 11:12 AM Anton Kedin <ke...@google.com> wrote: > >> ParserImpl is autogenerated by Calcite at build time. It seems that >> there's a race condition there and it sometimes fails. Rerunning the build >> works for me. >> >> Regards, >> Anton >> >> On Wed, Jan 23, 2019, 11:06 AM Alex Amato <ajam...@google.com> wrote: >> >>> https://jira.apache.org/jira/browse/BEAM-6495?filter=-2 >>> >>> Any ideas, how this got through the precommit? >>> >>> > Task :beam-sdks-java-extensions-sql:compileJava FAILED >>> >>> /usr/local/google/home/ajamato/go/src/ >>> github.com/apache/beam/sdks/java/extensions/sql/src/main/java/org/apache/beam/sdk/extensions/sql/impl/JdbcFactory.java:29: >>> error: cannot find symbol >>> >>> import >>> org.apache.beam.sdk.extensions.sql.impl.parser.impl.BeamSqlParserImpl; >>> >>> ^ >>> >>> symbol: class BeamSqlParserImpl >>> >>> location: package org.apache.beam.sdk.extensions.sql.impl.parser.impl >>> >>> 1 error >>> >>> -- ================ Ruoyun Huang
