[ISSUE] (TIGON-146) In TigonSQL if multiple streams are used with same fieldtypes in their schema, they are interpreted wrongly since all schemas are tied to a default interface set.

[Gokul Gunasekaran (JIRA)]

Gokul Gunasekaran created an issue

Tigon / TIGON-146 In TigonSQL if multiple streams are used with same fieldtypes in their schema, they are interpreted wrongly since all schemas are tied to a default interface set. Issue Type: Bug Affects Versions: 0.2.0 Assignee: Achal Pandey Created: 16/Oct/14 4:41 PM Fix Versions: 0.2.1 Priority: Major Reporter: Gokul Gunasekaran If users have two schemas, say Schema1 > int, int And Schema2 > int, int. Currently we use only one interface set (DEFAULT) and both schemas get referenced to the same interface set and thus data sent to schema1 might be parsed as schema2. A working solution is to have one interface set for each input stream. But users have to prefix the interface set name to their schema name in the SQL query they write. Add Comment

This message was sent by Atlassian JIRA (v6.1.5#6160-sha1:a61a0fc)

[Gokul Gunasekaran (JIRA)]

Gokul Gunasekaran updated an issue

Tigon / TIGON-146 In TigonSQL if multiple streams are used with same fieldtypes in their schema, they are interpreted wrongly since all schemas are tied to a default interface set.

Change By: Gokul Gunasekaran Priority: Major Critical

Add Comment

[Gokul Gunasekaran (JIRA)]

Gokul Gunasekaran updated an issue

Tigon / TIGON-146 In TigonSQL if multiple streams are used with same fieldtypes in their schema, they are interpreted wrongly since all schemas are tied to a default interface set.

Change By: Gokul Gunasekaran Priority: Critical Blocker

Add Comment

[Gokul Gunasekaran (JIRA)]

Gokul Gunasekaran updated an issue

Tigon / TIGON-146 In TigonSQL if multiple streams are used with same fieldtypes in their schema, they are interpreted wrongly since all schemas are tied to a default interface set. Change By: Gokul Gunasekaran

If users have two schemas, say Schema1 -> int, int And Schema2-> int, int. Currently we use only one interface set (DEFAULT) and both schemas get referenced to the same interface set and thus data sent to schema1 might be parsed as schema2. A working solution is to have one interface set for each input stream. But users have to prefix the interface set name to their schema name in the SQL query they write.

Add Comment

[Priyanka Nambiar (JIRA)]

Priyanka Nambiar updated an issue

Tigon / TIGON-146 In TigonSQL if multiple streams are used with same fieldtypes in their schema, they are interpreted wrongly since all schemas are tied to a default interface set.

Change By: Priyanka Nambiar Fix Version/s: 0.3.0 Fix Version/s: 0.2.1

Add Comment

[Gokul Gunasekaran (JIRA)]

Gokul Gunasekaran updated an issue

Tigon / TIGON-146 In TigonSQL if multiple streams are used with same fieldtypes in their schema, they are interpreted wrongly since all schemas are tied to a default interface set.

Change By: Gokul Gunasekaran

Fix Version/s: 0.2.1 Fix Version/s: 0.3.0

Add Comment

[Gokul Gunasekaran (JIRA)]

Gokul Gunasekaran resolved an issue as Fixed

https://github.com/caskdata/tigon/pull/92

Tigon / TIGON-146 In TigonSQL if multiple streams are used with same fieldtypes in their schema, they are interpreted wrongly since all schemas are tied to a default interface set.

Change By: Gokul Gunasekaran Status: Open Resolved Resolution: Fixed

Add Comment

[ted (JIRA)]

ted commented on an issue

Re: In TigonSQL if multiple streams are used with same fieldtypes in their schema, they are interpreted wrongly since all schemas are tied to a default interface set. I thought we had addressed this issue a few weeks ago. there is **NO CONNECTION** between a schema and an interface. One schema can be used with multiple interfaces, and in advanced applications multiple interfaces can be used with one schema. I had recommended that you disable the use of the default interface by setting its query in the .ifq file to an unsatisfiable predicate. I checked and verified that this works. That way any user query that does not explicitly reference an interface or interface set will be in error. I thought that you had resolved this kind of issue by having users explicitly reference interfaces in queries. We checked in a modification to tigon-sql to support this kind of query, since previously one needed to specify both the server name and the interface name of the interface in the query. To make use of parallelized stream transmission and query processing, you eventually want to define query sets and have users write queries so that they reference query sets. However I thought you had a working solution in which users would reference interfaces and the default interface set was disabled.

Add Comment

Tigon / TIGON-146 In TigonSQL if multiple streams are used with same fieldtypes in their schema, they are interpreted wrongly since all schemas are tied to a default interface set.

If users have two schemas, say Schema1 - > int, int And Schema2- > int, int. Currently we use only one interface set (DEFAULT) and both schemas get referenced to the same interface set and thus data sent to schema1 might be parsed as schema2. A working solution is to have one interface set for each input stream. But users have to prefix the interface set ...

[Gokul Gunasekaran (JIRA)]

Gokul Gunasekaran commented on an issue

Re: In TigonSQL if multiple streams are used with same fieldtypes in their schema, they are interpreted wrongly since all schemas are tied to a default interface set.

Hi ted You are right. We implemented what you have described in your comment. I have marked this JIRA as resolved in 0.2.1 Release. Thanks, Gokul

Add Comment