You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gobblin.apache.org by "Hung Tran (Jira)" <ji...@apache.org> on 2020/10/22 19:14:00 UTC

[jira] [Resolved] (GOBBLIN-1298) return JsonElement instead of null for the last element in resultChaining iterator

     [ https://issues.apache.org/jira/browse/GOBBLIN-1298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hung Tran resolved GOBBLIN-1298.
--------------------------------
    Fix Version/s: 0.16.0
       Resolution: Fixed

Issue resolved by pull request #3136
[https://github.com/apache/incubator-gobblin/pull/3136]

> return JsonElement instead of null for the last element in resultChaining iterator
> ----------------------------------------------------------------------------------
>
>                 Key: GOBBLIN-1298
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1298
>             Project: Apache Gobblin
>          Issue Type: Bug
>          Components: gobblin-salesforce
>            Reporter: Wenqin Wang
>            Assignee: Hung Tran
>            Priority: Major
>             Fix For: 0.16.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> A previous commit introduced a bug in the result chaining iterator, and would always omit the last record because it is returning null (instead of returning JsonElement). That is what I've seen in gobblin client side for SFDC extractor log & actual behavior, where there is always one record didn't get ingested.
> Therefore in this commit, instead of returning null, the code would only print out the records and return the last jsonElement.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)