[JBoss JIRA] (TEIID-3117) NullPointerException while creating source model from Excel table
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3117?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3117.
---------------------------------
> NullPointerException while creating source model from Excel table
> -----------------------------------------------------------------
>
> Key: TEIID-3117
> URL: https://issues.jboss.org/browse/TEIID-3117
> Project: Teiid
> Issue Type: Bug
> Affects Versions: 8.7
> Environment: Fedora 20, data virtualization 6.1.0.ER1
> Reporter: Juraj Duráni
> Assignee: Ramesh Reddy
> Labels: Beta1
> Fix For: 8.7.1, 8.9
>
> Attachments: ExcelDynamic-vdb.xml, Server.log, smalla.xlsx, smalla_raw.xlsx
>
>
> I am trying to create source model from Excel file (.xlsx). When I set property "Header Row Number" to 1 (using Teiid Designer), creating ends with NullPointerException. Setting "Header Row Number" to 0 executes with no problems.
> Same problem (and same exception) with dynamic VDB (only with <property name="importer.headerRowNumber" value="1"/>).
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 10 months
[JBoss JIRA] (TEIID-3160) Teiid inappropriately narrowing
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3160?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3160:
---------------------------------------
In Teiid BigDecimal (decimal) is considered a wider type than double/float whereas it's the other way around in most databases. This is because our BigDecimal was initial and still somewhat unlimited in terms of precision/scale. We may need to revisit that.
> Teiid inappropriately narrowing
> -------------------------------
>
> Key: TEIID-3160
> URL: https://issues.jboss.org/browse/TEIID-3160
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.7.1, 8.9
>
>
> issuing a query such as "select 1.0/2" should be done with non-integral division (.5), but the resolver is choosing integer division and returning 0.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 10 months
[JBoss JIRA] (TEIID-3192) Migrate Salesforce connectivity to sf partner api jars
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3192?page=com.atlassian.jira.plugin... ]
Steven Hawkins resolved TEIID-3192.
-----------------------------------
Resolution: Done
Added the proxy settings to the resource adapter:
proxyUsername
proxyPassword
proxyURL
and an additional:
configProperties
which would be for setting additional (lessor used) properties on ConnectorConfig - including at least for version 22:
validate schema, use chunked post, trace message, trace file, pretty print xml, max request size, max response size, and compression
This would be a string in the format of a properties file:
"useChunkedPost=true"
Alternatively I'm open to leaving this property off or effectively leaving it as undocumented.
> Migrate Salesforce connectivity to sf partner api jars
> ------------------------------------------------------
>
> Key: TEIID-3192
> URL: https://issues.jboss.org/browse/TEIID-3192
> Project: Teiid
> Issue Type: Component Upgrade
> Components: Salesforce Connector
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.10
>
>
> There are several deficiencies in using CXF for salesforce connectivity - we are not batching correctly, there is additional CXF overhead, and we have to maintain our own generated java of the api.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 10 months
[JBoss JIRA] (TEIID-2850) Add options to support sql server variant type
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2850?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-2850:
----------------------------------
Fix Version/s: 8.10
> Add options to support sql server variant type
> ----------------------------------------------
>
> Key: TEIID-2850
> URL: https://issues.jboss.org/browse/TEIID-2850
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors, Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.10
>
>
> Due to a SQL Server driver issue, a variant column cannot be directly retrieved (it needs to be confirmed if this works with JTDS). A valid workaround is a native-query extension with an appropriate cast.
> Beyond that we could:
> - add an option for the translator to automatically convert to a string value
> - allow for converts from object to be pushed down.
--
This message was sent by Atlassian JIRA
(v6.3.8#6338)
9 years, 10 months