You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@gobblin.apache.org by ap...@gmail.com on 2019/11/27 06:06:14 UTC

Apache Gobblin Gitter messages at 2019/11/26 22:06:12

####  ![](https://avatars2.githubusercontent.com/u/1669073?v=4&s=60) kchando
(kchando)

**[2019-11-26T22:05:17.580Z]**

Hi there,

We are currently using Gobblin V7 and we are in process of upgrading to
Gobblin V14.  
Due to S3 being our State store we have consistency issues with current.jst
not getting updated sometimes. Currently we manually fix this when we see
error.

IN the CHANGELOG for Gobblin 0.12 i can see that there is no need for
"current.jst" anymore. I followed this ticket
<https://issues.apache.org/jira/browse/GOBBLIN-109> and the discussion in this
PR :- [apache/incubator-gobblin#965](https://github.com/apache/incubator-
gobblin/pull/965) . It looks like even though there is no need for
"current.jst" it is still the default option.

in the poperties file these are the settings we have related to state store.

    
    
    # File system URIs
    fs.uri=${env:HADOOP_FS_URI}
    state.store.fs.uri=${env:S3_BUCKET_URI}
    state.store.dir=${env:S3_STATE_STORE_FOLDER}
    state.store.jobStateInStateStore=true

I see mysql an an option instead. I tried removing "createAlias()" in
FsDatasetsateStore.java but it still relies on "current.jst".  
So To keep using S3 wHat config changes are required to move to new state
store mechanism where there is no need for "current.jst" .???

* * *