Bug 1506519 – Osisoft translator - SUBSTRING fails when start > string length

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1506519 - Osisoft translator - SUBSTRING fails when start > string length

Summary:	Osisoft translator - SUBSTRING fails when start > string length

Status:	CLOSED WONTFIX

Aliases:	None

Product:	JBoss Data Virtualization 6
Classification:	JBoss
Component:	Teiid, Documentation (Show other bugs)
Sub Component:
Version:	6.4.0
Hardware:	Unspecified Unspecified

Priority	medium Severity medium
Target Milestone:	GA
Target Release:	6.4.0
Assigned To:	David Le Sage
QA Contact:	Jan Stastny
Docs Contact:

URL:
Whiteboard:
Keywords:	Documentation

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-10-26 05:32 EDT by Andrej Smigala
Modified:	2018-02-01 03:20 EST (History)
CC List:	8 users (show)

See Also:
Fixed In Version:
Doc Type:	Known Issue
Doc Text:	If you are using the OsiSoft translator and try to use the substring function in your queries, you will find that if the index is larger than the length of the string, an exception is thrown.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-02-01 03:20:14 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
JBoss Issue Tracker	TEIID-5126	Minor	Closed	Osisoft translator - SUBSTRING fails when start > string length	2018-02-01 08:38 EST

Groups: None (edit)

Description Andrej Smigala 2017-10-26 05:32:40 EDT

Calling a query such as

> SELECT cast(TIMESTAMPVALUE as string), SUBSTRING(TIMESTAMPVALUE, 22, 0) FROM BQT1.SmallA

fails with the following (the length of timestampvalue converted to string is 20):

> com.osisoft.rdsa.RdsaException: [PIOLEDBENT] Arguments are invalid.


This appears to be an issue with the SUBSTR implementation on the PI server, we are ok with either a workaround or documenting as KI.

Comment 3 David Le Sage 2017-12-03 17:06:25 EST

Added to release notes errata as a known issue.

Comment 4 Andrej Smigala 2017-12-07 08:46:24 EST

David, the doc text does not fully capture the nature of the KI. It mentions returning empty string instead of null or not supporting negative indexes, but none of that applies in this case. The real problem is that indexes larger than the length of the string result in an exception.

Note You need to log in before you can comment on or make changes to this bug.