Bug 1460484 – Google translator unexpected behavior for comparison with time

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

Bug 1460484 - Google translator unexpected behavior for comparison with time

Summary:	Google translator unexpected behavior for comparison with time

Status:	CLOSED CURRENTRELEASE

Aliases:	None

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

Priority	unspecified Severity unspecified
Target Milestone:	ER2
Target Release:	6.4.0
Assigned To:	Van Halbert
QA Contact:	Jan Stastny
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-06-10 23:45 EDT by Lucie Fabrikova
Modified:	2018-03-06 09:18 EST (History)
CC List:	7 users (show)

See Also:
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:	If you had comparative operators in Google translator queries, time results were incorrect. This was due to an API issue. An exception is now thrown instead to alert users not to use time with these operators.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-03-06 09:18:44 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-4844	Major	Resolved	Google translator unexpected behavior for comparison with time	2018-02-07 18:36 EST

Groups: None (edit)

Description Lucie Fabrikova 2017-06-10 23:45:19 EDT

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 David Le Sage 2017-11-22 23:12:59 EST

Documented as a resolved issue.

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