I don't believe so. Entities are stored whole. They're not like database tables where you can update a single column. The bulkloader turns your local CSV entry into an entity and list of properties and saves that without reading the current entity in the datastore.
Would it be easier if you could read your CSV file from the blobstore in a mapper job? You'd have programmatic control over reading the existing entity and deciding whether to modify it or not. -- Ikai Lan Developer Programs Engineer, Google App Engine Blogger: http://googleappengine.blogspot.com Reddit: http://www.reddit.com/r/appengine Twitter: http://twitter.com/app_engine On Thu, Nov 4, 2010 at 11:10 PM, Philip <[email protected]>wrote: > Any suggestions on getting this to work well? > > We upload from a csv that has 4 fields. The receiving entity in the > datastore has 5 properties. We only mention the 4 fields in the > bulkloader.yaml file. When the upload_data completes, existing > entities that matched the entries in the csv are replaced, not > updated. > > This results in us losing the 5th property as a result of upload_data > for existing entities. > > Is there a way to preserve the 5th property during the upload_data > process while at the same time replacing any of the values of the 4 > properties that may have been updated in the csv file? > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
