Cascading writing in FeatureWriter

Question

Hi Community,

does anybody know a way to force FeatureWriter to wait for completion of a writing task of a feature type before the next writing is triggered?

I'm trying to delete features on a database (Oracle Non Spatial) with constraints on the affected tables. So I must enforce a specific delete order. Currently I use a rather complex mechanism with mutiple FeatureWriter transformers in chain and would like to tie them down into one FetureWriter.

If a FeatureWriter could be configured in that way it would also be great to do the action within a single transaction. Is this possible too?

Page 1 / 1

In the writer there should be a parameter of features per transaction, try setting that to 1 so that each delete is committed before trying the next. The help documentation says this will decrease performance.Alternatively, you might be able to use a SQLExecutor, where each feature executes a statement to delete itself from the database.

Reply

ctredinnick · Answer

In the writer there should be a parameter of features per transaction, try setting that to 1 so that each delete is committed before trying the next. The help documentation says this will decrease performance.Alternatively, you might be able to use a SQLExecutor, where each feature executes a statement to delete itself from the database.

Reply

Community Stats

Sign up

An FME Account is required to contribute

Login to the community

An FME Account is required to contribute

Scanning file for viruses.

This file cannot be downloaded