[ https://issues.jboss.org/browse/TEIID-5237?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5237: --------------------------------------- [~rareddy] I don't see anything in the translator logic that looks like it would handle this scenario - it seems straight forward that a $in is being built with string values. There's no support for convert nor does there seem to be an alternative name in source that would allow this. Do you think we should just add a doc note about the searchability workaround? On the import side it looks like scanning stops at the first document instance, so the logic won't detect type conflicts there currently. There is some accounting of this in the couchbase translator that we could do here as well. -- This message was sent by Atlassian JIRA (v7.5.0#75005)