Skip to content

Conversation

@fernst
Copy link
Contributor

@fernst fernst commented Sep 1, 2022

No description provided.

@fernst fernst added the build Trigger unit test build label Sep 1, 2022
@fernst fernst changed the title PLUGIN-1367 Fixed null pointer exception when sink schema is not set and SQL Engine Output is initialized. [PLUGIN-1367] Fixed null pointer exception when sink schema is not set and SQL Engine Output is initialized. Sep 1, 2022
Schema.Field.of("name", Schema.of(Schema.Type.STRING)),
Schema.Field.of("price", Schema.of(Schema.Type.DOUBLE)),
Schema.Field.of("dt", Schema.nullableOf(Schema.of(Schema.LogicalType.DATE))),
Schema.Field.of("bytedata", Schema.of(Schema.Type.BYTES)),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you fix the tabs here, pls

// Sink Pushdown is not supported if the sink schema is not defined.
if (tableSchema == null) {
LOG.debug("BigQuery SQL Engine Output was not initialized. Schema was empty.");
return;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so, this just means that bqexecute will not be pushed down for schemaless and will work in the old way, correct?

Copy link
Contributor Author

@fernst fernst Sep 1, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BQ Execute is not a stage that can be "pushed down" in the traditional pipeline sense. BQ Execute operates on tables in BigQuery after the sink operation is completed.

Schemaless pipelines still work in Spark as they did before version 0.20 of the plugin / CDAP 6.7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bq-pushdown build Trigger unit test build

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants