[ https://issues.jboss.org/browse/TEIID-4918?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4918: --------------------------------------- This would apply to the first batch sent to the translator. Subsequent batches would see the target as non-empty. Without locking this does have a consistency issue - if another insert happens at the same time, you won't be empty any longer for the putAll. The same is true in a narrow sense for the individual inserts - it's a best effort consistency. Another concern is that we're not checking the pk constraint for the insert - so a putAll if there is a duplicate would result in the last entry being respected, rather than an exception in an insert scenario. -- This message was sent by Atlassian JIRA (v7.2.3#72005)