[teiid-issues] [JBoss JIRA] (TEIID-1070) Create Amazon SimpleDB Connector

[Ramesh Reddy (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12958636#comment-12958636 ] 

Ramesh Reddy commented on TEIID-1070:
-------------------------------------

I think the assumption made here can be modified. It was assumed that every domain's item is multi-valued attribute, thus trying to return concatenated string to represent the multiple values. I suggest, we flip that assumption, where when scanning domain's first item, if we find that item has multi-valued create it as string[], otherwise as plain string. This will save from creating these concat of strings in select and insert etc.

Also note that when the item is multi-valued, the calling semantics are little different, you have to use "every" or "intersection" keyword, as defined here http://docs.aws.amazon.com/AmazonSimpleDB/latest/DeveloperGuide/UsingSelectOperators.html, I do not think I saw that in the code.

* IN criteria support should be added, as it is supported in the query syntax
* SORT support should be added
* COUNT STAR support can be added

The one question I have is how to support "update" of array values in Teiid? I do not think Teiid supports that yet, does it?

                
> Create Amazon SimpleDB Connector 
> ---------------------------------
>
>                 Key: TEIID-1070
>                 URL: https://issues.jboss.org/browse/TEIID-1070
>             Project: Teiid
>          Issue Type: Feature Request
>          Components: Misc. Connectors
>            Reporter: John Doyle
>            Assignee: Ramesh Reddy
>             Fix For: 8.7
>
>
> We need connectivity to Amazon SimpleDB.  This should be accomplished through a dedicated connector.
> Simple DB presents a few challenges as a Teiid source as it is more like a spreadsheet than a database.  Simple DB "Domains' are like individual worksheets and contain any number of items.  Items however can have any number of attributes, and the attributes do not have to be the same for ever item.  So in a single Domain you can have an item with the attributes Size and Color, and another item with the attributes Color and ExpirationDate.  This presents both modeling issues and SQL execution issues.  None of them are insurmountable, but users will have to understand the issues and design their integration around them. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira