private boolean hasFullEntry(JsonValue entry,QuerySide querySide){
  if (querySide == QuerySide.SOURCE && sourceQueryFullEntry != null) {
    return sourceQueryFullEntry;
  }
 else   if (querySide == QuerySide.TARGET && targetQueryFullEntry != null) {
    return targetQueryFullEntry;
  }
  if (entry != null) {
    short ignoreFields=0;
    if (entry.isDefined("_id")) {
      ignoreFields++;
    }
    if (entry.isDefined("_rev")) {
      ignoreFields++;
    }
    ignoreFields+=2;
    return entry.size() > ignoreFields;
  }
 else {
    return false;
  }
}

private boolean hasFullEntry ( JsonValue entry , QuerySide querySide ) { if ( querySide == QuerySide . SOURCE && sourceQueryFullEntry != null ) { return sourceQueryFullEntry ; } else if ( querySide == QuerySide . TARGET && targetQueryFullEntry != null ) { return targetQueryFullEntry ; } if ( entry != null ) { short ignoreFields = 0 ; if ( entry . isDefined ( "_id" ) ) { ignoreFields ++ ; } if ( entry . isDefined ( "_rev" ) ) { ignoreFields ++ ; } ignoreFields += 2 ; return entry . size ( ) > ignoreFields ; } else { return false ; } }
whether the query ( source or target side query of a reconciliation ) returns full entry data , or just ids if explicitly configured , returns that setting . if not , tries to auto - detect if a given entry contains just id info , or contains full data the detection has limitations , such as requiring at least three data fields aside from fields it expects in id queries . this may not be case for all custom connectors , in which case explicit config is required instead of using auto detect .
