You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Steven Matison (Jira)" <ji...@apache.org> on 2023/05/31 11:40:00 UTC
[jira] [Commented] (NIFI-11608) PutBigQuery: Missing Flowfile Attribute Evaluation
[ https://issues.apache.org/jira/browse/NIFI-11608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17727913#comment-17727913 ]
Steven Matison commented on NIFI-11608:
---------------------------------------
This came up in a community post so I decided to jump in.
Solution worked on with [~exceptionfactory] .
Thank you David for your guidance through debug and PR process.
> PutBigQuery: Missing Flowfile Attribute Evaluation
> --------------------------------------------------
>
> Key: NIFI-11608
> URL: https://issues.apache.org/jira/browse/NIFI-11608
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.21.0
> Reporter: Juan Ignacio Saitua
> Assignee: Steven Matison
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> While the documentation states that PutBigQuery should support expression language for DATASET, TABLE_NAME, and SKIP_INVALID_ROWS, that's not really happening. An examination of the code reveals that these expressions are not evaluated in the current implementation ([see code here](https://github.com/apache/nifi/blob/cfd62c9511e43d5010fbfbb12b98b40bdfdb3fc2/nifi-nar-bundles/nifi-gcp-bundle/nifi-gcp-processors/src/main/java/org/apache/nifi/processors/gcp/bigquery/PutBigQuery.java#L193)). Notably, the issue does not exist in the PutBigQueryBatch processor. While both processors extends the AbstractBigQueryProcessor class, only PutBigQueryBatch utilizes the AbstractBigQueryProcessor.getTableId() method, which correctly evaluates and retrieves the tableId.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)