[jira] [Closed] (KYLIN-2772) Turn on all TIMEDATE FUNCTIONS in ODBC
[ https://issues.apache.org/jira/browse/KYLIN-2772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi closed KYLIN-2772. Resolution: Duplicate > Turn on all TIMEDATE FUNCTIONS in ODBC > -- > > Key: KYLIN-2772 > URL: https://issues.apache.org/jira/browse/KYLIN-2772 > Project: Kylin > Issue Type: Improvement >Reporter: Roger Shi > > Only 4 functions are declared in ODBC while actually there's no such > limitation in Kylin implementation. Turn them on. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KYLIN-2771) Turn on all TIMEDATE FUNCTIONS in ODBC
Roger Shi created KYLIN-2771: Summary: Turn on all TIMEDATE FUNCTIONS in ODBC Key: KYLIN-2771 URL: https://issues.apache.org/jira/browse/KYLIN-2771 Project: Kylin Issue Type: Improvement Reporter: Roger Shi Only 4 functions are declared in ODBC while actually there's no such limitation in Kylin implementation. Turn them on. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (KYLIN-2772) Turn on all TIMEDATE FUNCTIONS in ODBC
Roger Shi created KYLIN-2772: Summary: Turn on all TIMEDATE FUNCTIONS in ODBC Key: KYLIN-2772 URL: https://issues.apache.org/jira/browse/KYLIN-2772 Project: Kylin Issue Type: Improvement Reporter: Roger Shi Only 4 functions are declared in ODBC while actually there's no such limitation in Kylin implementation. Turn them on. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] hongbin ma reopened KYLIN-2720: --- > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming >Assignee: qiumingming > Fix For: v2.1.0 > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16108291#comment-16108291 ] hongbin ma commented on KYLIN-2720: --- Hi [~qmm] I'm afraid with https://issues.apache.org/jira/browse/KYLIN-2515 and https://issues.apache.org/jira/browse/KYLIN-2646 being added into kylin 2.1, we have to revert KYLIN-2720 as it conflicts with above issues. We're refining the authorization process recently. Discussions will be carried on in mail list or JIRA, please get informed > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming >Assignee: qiumingming > Fix For: v2.1.0 > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2646) Project level query authorization
[ https://issues.apache.org/jira/browse/KYLIN-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] hongbin ma resolved KYLIN-2646. --- Resolution: Fixed Fix Version/s: v2.1.0 > Project level query authorization > - > > Key: KYLIN-2646 > URL: https://issues.apache.org/jira/browse/KYLIN-2646 > Project: Kylin > Issue Type: Improvement >Reporter: hongbin ma >Assignee: hongbin ma > Fix For: v2.1.0 > > > As we introduced ad-hoc queries in > https://issues.apache.org/jira/browse/KYLIN-2515, we'll need to adjust query > authorization as follows: > Query authorization is encouraged to be set as project level. If someone is > assigned READ permission on project, then he has access to query all tables > in the project, regardless thru adhoc or cubes > If a user has READ permission on cubes but no READ permission on project. He > can only issue queries only if the query can be satisfied by those cubes he > has READ permission. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2768) Wrong UI for count distinct measure
[ https://issues.apache.org/jira/browse/KYLIN-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhixiong Chen resolved KYLIN-2768. -- Resolution: Fixed > Wrong UI for count distinct measure > --- > > Key: KYLIN-2768 > URL: https://issues.apache.org/jira/browse/KYLIN-2768 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.1.0 >Reporter: Shaofeng SHI >Assignee: Zhixiong Chen > Fix For: v2.1.0 > > Attachments: > 0001-KYLIN-2768-wrong-UI-for-count-distinct-measure.patch, 屏幕快照 2017-07-30 > 下午3.16.41.png > > > I made a build from 2.1.x branch, when create a count distinct measure, it > shows "Group by Column" input widget (se attachement). This is strange, as > embeded "group by column" is just in the "TopN" case, not applicable for > count distinct. > Is it for "multiple columns" support for count distinct? if so, the lable > need be updated. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2768) Wrong UI for count distinct measure
[ https://issues.apache.org/jira/browse/KYLIN-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16108288#comment-16108288 ] Zhixiong Chen commented on KYLIN-2768: -- OK.I will double commit in master and 2.1.x. > Wrong UI for count distinct measure > --- > > Key: KYLIN-2768 > URL: https://issues.apache.org/jira/browse/KYLIN-2768 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.1.0 >Reporter: Shaofeng SHI >Assignee: Zhixiong Chen > Fix For: v2.1.0 > > Attachments: > 0001-KYLIN-2768-wrong-UI-for-count-distinct-measure.patch, 屏幕快照 2017-07-30 > 下午3.16.41.png > > > I made a build from 2.1.x branch, when create a count distinct measure, it > shows "Group by Column" input widget (se attachement). This is strange, as > embeded "group by column" is just in the "TopN" case, not applicable for > count distinct. > Is it for "multiple columns" support for count distinct? if so, the lable > need be updated. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2623) Move output(Hbase) related code from MR engine to outputside
[ https://issues.apache.org/jira/browse/KYLIN-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi resolved KYLIN-2623. -- Resolution: Fixed fixed in commit a38b02df0387541684aa1689e044927af650f1c7 > Move output(Hbase) related code from MR engine to outputside > > > Key: KYLIN-2623 > URL: https://issues.apache.org/jira/browse/KYLIN-2623 > Project: Kylin > Issue Type: Improvement > Environment: Output engine is extendable according to the design of > Kylin. So outputformat and reducer number should be defined in output side > instead of MR engine. Move these code to the right position will make it more > extendable. >Reporter: Roger Shi >Assignee: Roger Shi > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (KYLIN-2657) Cube merge TopN dictionary not found, cause NPE
[ https://issues.apache.org/jira/browse/KYLIN-2657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi resolved KYLIN-2657. -- Resolution: Fixed fixed in commit 9ad0ba3ddb391695eddaadca438dc4dfdda60d5f > Cube merge TopN dictionary not found, cause NPE > --- > > Key: KYLIN-2657 > URL: https://issues.apache.org/jira/browse/KYLIN-2657 > Project: Kylin > Issue Type: Bug >Reporter: Roger Shi >Assignee: Roger Shi > > One TopN measure with two group-by columns, and both of them are in fact > table. If one cardinality is high and the other is low, merging Cube may fail > for NPE (dict not found). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2768) Wrong UI for count distinct measure
[ https://issues.apache.org/jira/browse/KYLIN-2768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16108266#comment-16108266 ] Shaofeng SHI commented on KYLIN-2768: - Looks good, thanks Zhixiong. > Wrong UI for count distinct measure > --- > > Key: KYLIN-2768 > URL: https://issues.apache.org/jira/browse/KYLIN-2768 > Project: Kylin > Issue Type: Bug > Components: Web >Affects Versions: v2.1.0 >Reporter: Shaofeng SHI >Assignee: Zhixiong Chen > Fix For: v2.1.0 > > Attachments: > 0001-KYLIN-2768-wrong-UI-for-count-distinct-measure.patch, 屏幕快照 2017-07-30 > 下午3.16.41.png > > > I made a build from 2.1.x branch, when create a count distinct measure, it > shows "Group by Column" input widget (se attachement). This is strange, as > embeded "group by column" is just in the "TopN" case, not applicable for > count distinct. > Is it for "multiple columns" support for count distinct? if so, the lable > need be updated. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2720) Should not allow user to access to all tables' metadata of a project
[ https://issues.apache.org/jira/browse/KYLIN-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16107533#comment-16107533 ] qiumingming commented on KYLIN-2720: (y) > Should not allow user to access to all tables' metadata of a project > > > Key: KYLIN-2720 > URL: https://issues.apache.org/jira/browse/KYLIN-2720 > Project: Kylin > Issue Type: Improvement >Reporter: qiumingming >Assignee: qiumingming > Fix For: v2.1.0 > > Attachments: KYLIN-2720.patch > > > Currently, user can access to all tables and columns metadata of a specific > project as long as he can access to this project, which is not reasonable. > User should just allow to access to tables that he owned cubes dependent to. > However, user can see some other tables in the web UI in current version. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2758) Query pushdown should be able to skip database prefix
[ https://issues.apache.org/jira/browse/KYLIN-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jiatao.tao updated KYLIN-2758: -- Attachment: KYLIN-2578_patch.diff Complete input SQL's default database name when the query is entering query pushdown engine > Query pushdown should be able to skip database prefix > - > > Key: KYLIN-2758 > URL: https://issues.apache.org/jira/browse/KYLIN-2758 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Reporter: jiatao.tao >Assignee: jiatao.tao >Priority: Minor > Attachments: KYLIN-2578_patch.diff > > > Kylin allows query to skip table's database prefix when the database is the > default database. > Query pushdown should provides the same availability. It supposed to be > invisible to to user. But currently not because it push the raw query > directly to external sql executors.The external sql executors(pushdown > engine, like spark sql, hive) don't recognize the query if the query's > default database is not 'DEFAULT' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (KYLIN-2762) Get "Owner required" error on saving data model
[
https://issues.apache.org/jira/browse/KYLIN-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jiatao.tao updated KYLIN-2762:
--
Attachment: KYLIN-2762_patch.diff
Fixed by move KYLIN_HOME/tool in front of the CLASSPATH
> Get "Owner required" error on saving data model
> ---
>
> Key: KYLIN-2762
> URL: https://issues.apache.org/jira/browse/KYLIN-2762
> Project: Kylin
> Issue Type: Bug
>Affects Versions: v2.1.0
>Reporter: Shaofeng SHI
>Assignee: jiatao.tao
> Fix For: v2.1.0
>
> Attachments: KYLIN-2762_patch.diff
>
>
> Use the latest 2.1 build, when save a new data model, get "Owner required"
> error. In kylin.log, there are the following errors:
> {code}
> 2017-07-27 15:26:55,144 DEBUG [http-bio-7070-exec-2]
> controller.ModelController:214 : Saving MODEL {
> "name": "test21",
> "description": "",
> "fact_table": "DEFAULT.KYLIN_SALES",
> "lookups": [
> {
> "table": "DEFAULT.KYLIN_CAL_DT",
> "alias": "KYLIN_CAL_DT",
> "joinTable": "KYLIN_SALES",
> "kind": "LOOKUP",
> "join": {
> "type": "inner",
> "primary_key": [
> "KYLIN_CAL_DT.CAL_DT"
> ],
> "foreign_key": [
> "KYLIN_SALES.PART_DT"
> ],
> "isCompatible": [
> true
> ],
> "pk_type": [
> "date"
> ],
> "fk_type": [
> "date"
> ]
> }
> }
> ],
> "filter_condition": "",
> "dimensions": [
> {
> "table": "KYLIN_SALES",
> "columns": [
> "TRANS_ID",
> "PART_DT",
> "LSTG_FORMAT_NAME",
> "LEAF_CATEG_ID",
> "LSTG_SITE_ID",
> "BUYER_ID"
> ]
> },
> {
> "table": "KYLIN_CAL_DT",
> "columns": [
> "CAL_DT",
> "YEAR_BEG_DT",
> "QTR_BEG_DT",
> "MONTH_BEG_DT",
> "WEEK_BEG_DT"
> ]
> }
> ],
> "metrics": [
> "KYLIN_SALES.PRICE",
> "KYLIN_SALES.ITEM_COUNT"
> ],
> "partition_desc": {
> "partition_date_column": "KYLIN_SALES.PART_DT",
> "partition_type": "APPEND",
> "partition_date_format": "-MM-dd"
> },
> "last_modified": 0
> }
> 2017-07-27 15:26:55,172 DEBUG [pool-10-thread-1] cachesync.Broadcaster:132 :
> Servers in the cluster: [localhost:7070]
> 2017-07-27 15:26:55,172 DEBUG [pool-10-thread-1] cachesync.Broadcaster:139 :
> Announcing new broadcast event: BroadcastEvent{entity=data_model,
> event=create, cacheKey=test21}
> 2017-07-27 15:26:55,182 DEBUG [pool-10-thread-1] cachesync.Broadcaster:132 :
> Servers in the cluster: [localhost:7070]
> 2017-07-27 15:26:55,182 DEBUG [pool-10-thread-1] cachesync.Broadcaster:139 :
> Announcing new broadcast event: BroadcastEvent{entity=project, event=update,
> cacheKey=learn_kylin}
> 2017-07-27 15:26:55,191 DEBUG [http-bio-7070-exec-2] service.AclService:198 :
> ACL of org.springframework.security.acls.domain.ObjectIdentityImpl[Type:
> org.apache.kylin.metadata.model.DataModelDesc; Identifier:
> bafa3eca-be31-4918-9354-acd8243ca058] created successfully.
> 2017-07-27 15:26:55,208 DEBUG [http-bio-7070-exec-10]
> project.ProjectL2Cache:191 : Loading L2 project cache for LEARN_KYLIN
> 2017-07-27 15:26:55,208 WARN [http-bio-7070-exec-10]
> realization.RealizationRegistry:125 : No provider for realization type
> INVERTED_INDEX
> 2017-07-27 15:26:55,213 DEBUG [http-bio-7070-exec-2] service.AclService:255 :
> ACL of org.springframework.security.acls.domain.ObjectIdentityImpl[Type:
> org.apache.kylin.metadata.model.DataModelDesc; Identifier:
> bafa3eca-be31-4918-9354-acd8243ca058] updated successfully.
> 2017-07-27 15:26:55,216 INFO [http-bio-7070-exec-10] cube.CubeManager:834 :
> Reloaded cube kylin_sales_cube being CUBE[name=kylin_sales_cube] having 0
> segments
> 2017-07-27 15:26:55,217 INFO [http-bio-7070-exec-10]
> service.CacheService:136 : removeOLAPDataSource is called for project
> learn_kylin
> 2017-07-27 15:26:55,217 INFO [http-bio-7070-exec-10]
> service.CacheService:118 : cleaning cache for project learn_kylin (currently
> remove all entries)
> 2017-07-27 15:26:55,217 DEBUG [http-bio-7070-exec-10]
> cachesync.Broadcaster:236 : Done broadcasting metadata change:
> entity=project_schema, event=UPDATE, cacheKey=learn_kylin
> 2017-07-27 15:26:55,218 DEBUG [http-bio-7070-exec-10]
> cachesync.Broadcaster:236 : Done broadcasting metadata change:
> entity=data_model, event=CREATE, cacheKey=test21
> 2017-07-27 15:26:55,226 ERROR [http-bio-7070-exec-2]
> controller.BasicController:57 :
> java.lang.IllegalArgumentException: Owner required
> at org.springframework.util.Assert.notNull(Assert.java:115)
> at
> org.springframework.security.acls.domain.AclImpl.(AclImpl.java:102)
> at
>
[jira] [Resolved] (KYLIN-2762) Get "Owner required" error on saving data model
[
https://issues.apache.org/jira/browse/KYLIN-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jiatao.tao resolved KYLIN-2762.
---
Resolution: Fixed
> Get "Owner required" error on saving data model
> ---
>
> Key: KYLIN-2762
> URL: https://issues.apache.org/jira/browse/KYLIN-2762
> Project: Kylin
> Issue Type: Bug
>Affects Versions: v2.1.0
>Reporter: Shaofeng SHI
>Assignee: jiatao.tao
> Fix For: v2.1.0
>
>
> Use the latest 2.1 build, when save a new data model, get "Owner required"
> error. In kylin.log, there are the following errors:
> {code}
> 2017-07-27 15:26:55,144 DEBUG [http-bio-7070-exec-2]
> controller.ModelController:214 : Saving MODEL {
> "name": "test21",
> "description": "",
> "fact_table": "DEFAULT.KYLIN_SALES",
> "lookups": [
> {
> "table": "DEFAULT.KYLIN_CAL_DT",
> "alias": "KYLIN_CAL_DT",
> "joinTable": "KYLIN_SALES",
> "kind": "LOOKUP",
> "join": {
> "type": "inner",
> "primary_key": [
> "KYLIN_CAL_DT.CAL_DT"
> ],
> "foreign_key": [
> "KYLIN_SALES.PART_DT"
> ],
> "isCompatible": [
> true
> ],
> "pk_type": [
> "date"
> ],
> "fk_type": [
> "date"
> ]
> }
> }
> ],
> "filter_condition": "",
> "dimensions": [
> {
> "table": "KYLIN_SALES",
> "columns": [
> "TRANS_ID",
> "PART_DT",
> "LSTG_FORMAT_NAME",
> "LEAF_CATEG_ID",
> "LSTG_SITE_ID",
> "BUYER_ID"
> ]
> },
> {
> "table": "KYLIN_CAL_DT",
> "columns": [
> "CAL_DT",
> "YEAR_BEG_DT",
> "QTR_BEG_DT",
> "MONTH_BEG_DT",
> "WEEK_BEG_DT"
> ]
> }
> ],
> "metrics": [
> "KYLIN_SALES.PRICE",
> "KYLIN_SALES.ITEM_COUNT"
> ],
> "partition_desc": {
> "partition_date_column": "KYLIN_SALES.PART_DT",
> "partition_type": "APPEND",
> "partition_date_format": "-MM-dd"
> },
> "last_modified": 0
> }
> 2017-07-27 15:26:55,172 DEBUG [pool-10-thread-1] cachesync.Broadcaster:132 :
> Servers in the cluster: [localhost:7070]
> 2017-07-27 15:26:55,172 DEBUG [pool-10-thread-1] cachesync.Broadcaster:139 :
> Announcing new broadcast event: BroadcastEvent{entity=data_model,
> event=create, cacheKey=test21}
> 2017-07-27 15:26:55,182 DEBUG [pool-10-thread-1] cachesync.Broadcaster:132 :
> Servers in the cluster: [localhost:7070]
> 2017-07-27 15:26:55,182 DEBUG [pool-10-thread-1] cachesync.Broadcaster:139 :
> Announcing new broadcast event: BroadcastEvent{entity=project, event=update,
> cacheKey=learn_kylin}
> 2017-07-27 15:26:55,191 DEBUG [http-bio-7070-exec-2] service.AclService:198 :
> ACL of org.springframework.security.acls.domain.ObjectIdentityImpl[Type:
> org.apache.kylin.metadata.model.DataModelDesc; Identifier:
> bafa3eca-be31-4918-9354-acd8243ca058] created successfully.
> 2017-07-27 15:26:55,208 DEBUG [http-bio-7070-exec-10]
> project.ProjectL2Cache:191 : Loading L2 project cache for LEARN_KYLIN
> 2017-07-27 15:26:55,208 WARN [http-bio-7070-exec-10]
> realization.RealizationRegistry:125 : No provider for realization type
> INVERTED_INDEX
> 2017-07-27 15:26:55,213 DEBUG [http-bio-7070-exec-2] service.AclService:255 :
> ACL of org.springframework.security.acls.domain.ObjectIdentityImpl[Type:
> org.apache.kylin.metadata.model.DataModelDesc; Identifier:
> bafa3eca-be31-4918-9354-acd8243ca058] updated successfully.
> 2017-07-27 15:26:55,216 INFO [http-bio-7070-exec-10] cube.CubeManager:834 :
> Reloaded cube kylin_sales_cube being CUBE[name=kylin_sales_cube] having 0
> segments
> 2017-07-27 15:26:55,217 INFO [http-bio-7070-exec-10]
> service.CacheService:136 : removeOLAPDataSource is called for project
> learn_kylin
> 2017-07-27 15:26:55,217 INFO [http-bio-7070-exec-10]
> service.CacheService:118 : cleaning cache for project learn_kylin (currently
> remove all entries)
> 2017-07-27 15:26:55,217 DEBUG [http-bio-7070-exec-10]
> cachesync.Broadcaster:236 : Done broadcasting metadata change:
> entity=project_schema, event=UPDATE, cacheKey=learn_kylin
> 2017-07-27 15:26:55,218 DEBUG [http-bio-7070-exec-10]
> cachesync.Broadcaster:236 : Done broadcasting metadata change:
> entity=data_model, event=CREATE, cacheKey=test21
> 2017-07-27 15:26:55,226 ERROR [http-bio-7070-exec-2]
> controller.BasicController:57 :
> java.lang.IllegalArgumentException: Owner required
> at org.springframework.util.Assert.notNull(Assert.java:115)
> at
> org.springframework.security.acls.domain.AclImpl.(AclImpl.java:102)
> at
> org.apache.kylin.rest.service.AclService.readAclsById(AclService.java:166)
> at
> org.apache.kylin.rest.service.AclService.readAclById(AclService.java:127)
>
[jira] [Resolved] (KYLIN-2758) Query pushdown should be able to skip database prefix
[ https://issues.apache.org/jira/browse/KYLIN-2758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jiatao.tao resolved KYLIN-2758. --- Resolution: Fixed > Query pushdown should be able to skip database prefix > - > > Key: KYLIN-2758 > URL: https://issues.apache.org/jira/browse/KYLIN-2758 > Project: Kylin > Issue Type: Bug > Components: Query Engine >Reporter: jiatao.tao >Assignee: jiatao.tao >Priority: Minor > > Kylin allows query to skip table's database prefix when the database is the > default database. > Query pushdown should provides the same availability. It supposed to be > invisible to to user. But currently not because it push the raw query > directly to external sql executors.The external sql executors(pushdown > engine, like spark sql, hive) don't recognize the query if the query's > default database is not 'DEFAULT' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
