You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kylin.apache.org by "Shaofeng SHI (JIRA)" <ji...@apache.org> on 2015/11/24 03:01:11 UTC

[jira] [Created] (KYLIN-1161) Rest API /api/cubes?cubeName= is doing fuzzy match instead of exact match

Shaofeng SHI created KYLIN-1161:
-----------------------------------

             Summary: Rest API /api/cubes?cubeName=  is doing fuzzy match instead of exact match
                 Key: KYLIN-1161
                 URL: https://issues.apache.org/jira/browse/KYLIN-1161
             Project: Kylin
          Issue Type: Bug
          Components: REST Service
    Affects Versions: v1.1.1, v0.7.1, v0.7.2, v1.0, v1.1
            Reporter: Shaofeng SHI
            Assignee: Zhong,Jason
             Fix For: v1.2, 2.0


This is reported by Yang HaiLe from dev mailing list:

 When I use restful api to get details of a cube, I found that the server will return more than one cube’s detail I want. For example:
I use the url: http://server_ip:7070/kylin/api/cubes?cubeName=v5&limit=15&offset=0. The server will return these:
   [
    {
        "uuid": "876dd9d8-bc40-45fd-be6b-e0429ff9d4d1",
        "name": "v5",
        "owner": "ADMIN",
        "version": null,
        "cost": 50,
        "status": "READY",
        "segments": [
            {
                "uuid": "dd80cab3-1069-4333-8463-e0e48f2602c6",
                "name": "20151020000000_20151021000000",
                "status": "READY",
                                     ……….
            },
            {
                "uuid": "960e44b8-ac38-4483-8dbe-6a6a817ff4e1",
                "name": "20151020000000_20151022000000",
                "status": "NEW",
……….
            },
            {
                "uuid": "a8f6116f-acd6-46ac-be2f-021c2b291531",
                "name": "20151021000000_20151022000000",
                "status": "READY",
                                     ……….

            }
        ],
        "last_modified": 1448258568340,
        "descriptor": "v5",
        "create_time_utc": 1448244454401,
        "auto_merge_time_ranges": null,
        "retention_range": 0,
        "size_kb": 0,
        "input_records_count": 0,
        "input_records_size": 0
    },
    {
        "uuid": "c0dc404a-cfe6-4315-ac1c-ef52b27f8335",
        "name": "v5_21",
        "owner": "ADMIN",
        "version": null,
        "cost": 50,
        "status": "READY",
        "segments": [
            {
                "uuid": "c8e195ba-51a9-4fd9-be86-40e9943bcb1c",
                "name": "20151021000000_20151022000000",
               "status": "READY",
                                     ……….
            }
        ],
        "last_modified": 1448257690944,
        "descriptor": "v5_21",
        "create_time_utc": 1448247295576,
        "auto_merge_time_ranges": null,
        "retention_range": 0,
        "size_kb": 0,
        "input_records_count": 0,
        "input_records_size": 0
    }
]
I don’t understand why this happen. The v5_21 cube and v5 cube base a sample fact table and project.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)