Tigon
  1. Tigon
  2. 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.

    Details

    • Type: Bug Bug
    • Status: Resolved Resolved
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: 0.2.0
    • Fix Version/s: 0.2.1
    • Labels:
      None
    • Rank:
      1|hzyg3b:

      Description

      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.

        Activity

        Show
        Gokul Gunasekaran added a comment - https://github.com/caskdata/tigon/pull/92
        Hide
        ted added a comment -

        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.

        Show
        ted added a comment - 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.
        Hide
        Gokul Gunasekaran added a comment -

        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

        Show
        Gokul Gunasekaran added a comment - 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

          People

          • Assignee:
            Achal Pandey
            Reporter:
            Gokul Gunasekaran
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: