[JBoss JIRA] (TEIID-3244) XML Choice is not being evaluated as expected
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3244?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3244.
-----------------------------------
Resolution: Won't Fix
We will deprecate the xml document model feature.
> XML Choice is not being evaluated as expected
> ---------------------------------------------
>
> Key: TEIID-3244
> URL: https://issues.jboss.org/browse/TEIID-3244
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Debbie Steigner
> Priority: Minor
> Fix For: Open To Community
>
>
> We have an XML View model, built on a schema that includes choice nodes. We've used the choice editor to define a default choice; however, no data comes back for any of these choices, despite the fact that data does exist.
> It appears that MMX is not executing the queries under the default choice nodes.
> As a second test, we tried setting criteria that would always be true. Still, the choice nodes were not executed.
> Finally, we tried setting criteria that would never be true, and told the choice editor to throw an exception if the criteria was not met. No exception was thrown. This seems to indicate that MMX simply isn't evaluating this part of the document.
> Finally, I have an theory about what could be the source of the problem, based on what I did differently during the rebuild. If you click on the "Subject" mapping class, notice that "choice" gets highlighted. In my rebuild, when I click on "Subject", the "category" gets highlighted, but the choice above it does not. The behavior is problematic in the first case, but works as expected in the second case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (TEIID-3938) EdmDate and EdmTimeOfDay output in local timezone
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3938?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3938:
-------------------------------------
Unfortunately there is no such agreement to keep the values in/out in GMT in OData specification, it just that these values do not have any TZ info at all. Treating them strings or some special construct in Java would have been straight forward, since they are ties to java.sql.Time and java.sql.Date it is making difficult. The right (talking it loosely, I am lost what is right..) thing to do is, define another property such as "defaultTimeZoneForEdmDate" and have a default to "GMT". That way it can be configurable, and decision is in the hands of the developer. For unit tests I can lock it with GMT. WDYT?
> EdmDate and EdmTimeOfDay output in local timezone
> -------------------------------------------------
>
> Key: TEIID-3938
> URL: https://issues.jboss.org/browse/TEIID-3938
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Fix For: 8.12.5
>
>
> EdmDate and EdmTimeOfDay both assume GMT for incoming string values - however when the convert from Java objects to string they use the local/default Calendar. So when Teiid is on a server not in GMT date and time value sent via the odata4 translator will likely be wrong.
> Ramesh:
> I have posted a question to the Olingo development group here http://markmail.org/search/list:org.apache.olingo.dev#query:list%3Aorg.ap...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (TEIID-3836) Create a quick start to demonstrate OData
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3836?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3836:
----------------------------------
Fix Version/s: 9.0
(was: 9.x)
> Create a quick start to demonstrate OData
> -----------------------------------------
>
> Key: TEIID-3836
> URL: https://issues.jboss.org/browse/TEIID-3836
> Project: Teiid
> Issue Type: Task
> Components: Quick Starts
> Affects Versions: 9.x
> Reporter: Kylin Soong
> Assignee: Van Halbert
> Fix For: 9.0
>
>
> Add a quick start to demonstrate OData api may helpful for users.
> After deploy portfolio-vdb.xml successful, I test with(http://localhost:8080/odata/Portfolio.1/Stocks.StockPrices) return a error:
> {code}
> TEIID16011 EntitySet "Stocks.StockPrices" is not found; Check the spelling, use modelName.tableName; The table that representing the Entity type must either have a PRIMARY KEY or UNIQUE key(s)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (TEIID-2884) Support for Amazon Elastic MapReduce
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2884?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-2884:
---------------------------------------
Based upon being able to use the Hive/Impala driver for access, I move to mark this issue as resolved. We can note access on each of translator and the datasources page.
> Support for Amazon Elastic MapReduce
> ------------------------------------
>
> Key: TEIID-2884
> URL: https://issues.jboss.org/browse/TEIID-2884
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Reporter: Van Halbert
> Assignee: Kylin Soong
> Fix For: 8.12.x
>
>
> Amazon Elastic MapReduce
> from http://en.wikipedia.org/wiki/Amazon_Elastic_MapReduce#Amazon_Elastic_MapR...
> Elastic MapReduce (EMR)was introduced by Amazon in April 2009. Provisioning of the Hadoop cluster, running and terminating jobs, and handling data transfer between EC2 and S3 are automated by Elastic MapReduce. Apache Hive, which is built on top of Hadoop for providing data warehouse services, is also offered in Elastic MapReduce.
> ...
> In June 2012, premium options for EMR were added that replace ordinary Hadoop with MapR's M3 and M5 versions. These options provide additional capabilities over and above what the default EMR offering provides.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (TEIID-3826) Upgrade to use resteasy-jaxrs:jar:2.3.10.Final
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3826?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3826:
----------------------------------
Issue Type: Task (was: Enhancement)
> Upgrade to use resteasy-jaxrs:jar:2.3.10.Final
> ----------------------------------------------
>
> Key: TEIID-3826
> URL: https://issues.jboss.org/browse/TEIID-3826
> Project: Teiid
> Issue Type: Task
> Components: OData
> Affects Versions: 8.12
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Priority: Blocker
> Fix For: 8.12.5
>
>
> 8.12.x is currently dependent on resteasy-jaxrs:jar:2.3.7.Final
> In upgrading the IP-BOM to 30, which is dependent on 2.3.10, it seems the following class has been removed from javax-rs 2.3.10:
> org/jboss/resteasy/util/HttpServletRequestDelegate.java
> which breaks ProxyHttpServletRequest.java
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (TEIID-3826) Upgrade to use resteasy-jaxrs:jar:2.3.10.Final
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3826?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3826:
----------------------------------
Fix Version/s: 8.12.5
(was: 8.12.x)
> Upgrade to use resteasy-jaxrs:jar:2.3.10.Final
> ----------------------------------------------
>
> Key: TEIID-3826
> URL: https://issues.jboss.org/browse/TEIID-3826
> Project: Teiid
> Issue Type: Enhancement
> Components: OData
> Affects Versions: 8.12
> Reporter: Van Halbert
> Assignee: Ramesh Reddy
> Priority: Blocker
> Fix For: 8.12.5
>
>
> 8.12.x is currently dependent on resteasy-jaxrs:jar:2.3.7.Final
> In upgrading the IP-BOM to 30, which is dependent on 2.3.10, it seems the following class has been removed from javax-rs 2.3.10:
> org/jboss/resteasy/util/HttpServletRequestDelegate.java
> which breaks ProxyHttpServletRequest.java
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months
[JBoss JIRA] (TEIID-3938) EdmDate and EdmTimeOfDay output in local timezone
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3938?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3938:
---------------------------------------
If there is agreement that Edm.Date and Edm.TimeOfDay should default to GMT in/out, then a property isn't needed unless you are trying to maintain backwards compatibility. I was thinking when I first looked at the patch that your flag on EdmDateTimeOffset changed the actual value, but it just selects between equivalent string forms for the same instant. A flag for Edm.Date and Edm.TimeOfDay would actually change the values.
> EdmDate and EdmTimeOfDay output in local timezone
> -------------------------------------------------
>
> Key: TEIID-3938
> URL: https://issues.jboss.org/browse/TEIID-3938
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Fix For: 8.12.5
>
>
> EdmDate and EdmTimeOfDay both assume GMT for incoming string values - however when the convert from Java objects to string they use the local/default Calendar. So when Teiid is on a server not in GMT date and time value sent via the odata4 translator will likely be wrong.
> Ramesh:
> I have posted a question to the Olingo development group here http://markmail.org/search/list:org.apache.olingo.dev#query:list%3Aorg.ap...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 11 months