Skip to main content
Solved

Issue with Dynamic Writing to SDE for larger datasets

  • December 2, 2024
  • 3 replies
  • 45 views

tbarker1986
Contributor
Forum|alt.badge.img+4

Hi all, I am experiencing an issue with writing dynamically to SDE for large datasets (i’m unsure of the exact number, but above ~5000 features seems to cause a fail).  

My flow reads in a dataset name from an SQL table, matches it to a dataset that has been downloaded as part of a previous flow, checks if it has been updated and if so drops and recreates the Feature Class using a name given in the SQL tables.

When running the flow in batch using a Workspace Runner, ~half of my datasets ran successfully, and ~half failed to be updated in the SDE. I have looked into this is some depth and the only pattern I can see is the datasets that are failing are larger. The error message I am getting is below. I have tried using a sampler on the data just before the FeatureWriter and the flow works correctly, which validates my findings. What could be the potential reasoning behind this behaviour? or has anyone else experienced similar? If there are any other suggestions of settings I could change to help that would be appreciated!

Error message

FME version is 2023.2.1 (Build 23774)

 

FeatureWriter settings

 

Best answer by nielsgerrits

I think this error

Feature Type Definition ‘’ was requested, but not defined.

is caused by a missing schemafeature or a datafeature arriving at the FeatureWriter before the schemafeature.

What happens if you use AttributeCreators to create an attribute “Order” with value 1 for schemafeatures and 2 for datafeatures and use a sorter to sort on order, forcing the schemafeatures to arrive at the FeatureWriter first?

Also, switching off FeatureCaching on big production runs will improve your runtime greatly.

View original
Did this help you find an answer to your question?

3 replies

nielsgerrits
VIP
Forum|alt.badge.img+54
  • Best Answer
  • December 2, 2024

I think this error

Feature Type Definition ‘’ was requested, but not defined.

is caused by a missing schemafeature or a datafeature arriving at the FeatureWriter before the schemafeature.

What happens if you use AttributeCreators to create an attribute “Order” with value 1 for schemafeatures and 2 for datafeatures and use a sorter to sort on order, forcing the schemafeatures to arrive at the FeatureWriter first?

Also, switching off FeatureCaching on big production runs will improve your runtime greatly.


tbarker1986
Contributor
Forum|alt.badge.img+4
  • Author
  • Contributor
  • December 2, 2024

Thank you ​@nielsgerrits, that seems to have worked a treat… and thank you for the very quick reply!


nielsgerrits
VIP
Forum|alt.badge.img+54

Cheers :)


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings