[jira] [Updated] (KYLIN-201) Save as image in visualization result
[ https://issues.apache.org/jira/browse/KYLIN-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-201: Component/s: Web > Save as image in visualization result > - > > Key: KYLIN-201 > URL: https://issues.apache.org/jira/browse/KYLIN-201 > Project: Kylin > Issue Type: Wish > Components: Web >Reporter: Luke Han >Assignee: Zhong,Jason > Labels: github-import > Fix For: Backlog > > > As a user, I would like to be able to save visualization as image > The "Export" should perform different approach for Grid and Visualization > view. > ![image|https://cloud.githubusercontent.com/assets/1104017/5556235/af5ddb12-8d0f-11e4-91f9-34bafe13c163.png] > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/304 > Created by: [lukehan|https://github.com/lukehan] > Labels: enhancement, > Created at: Fri Dec 26 14:58:59 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-195) Enable switch fact table in cube metadata
[ https://issues.apache.org/jira/browse/KYLIN-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-195: Labels: github-import metadata (was: github-import) > Enable switch fact table in cube metadata > - > > Key: KYLIN-195 > URL: https://issues.apache.org/jira/browse/KYLIN-195 > Project: Kylin > Issue Type: Wish > Components: Metadata, Web >Reporter: Luke Han >Priority: Minor > Labels: github-import, metadata > Fix For: Backlog > > > As a cube owner, I would like to be able to design my cube with sample fact > table first then build and run to verify in design time, with small data but > same structure to speed up design and troubleshooting. > And when I release it to production, I would like to be able to switch to > production fact table with real data. > Also would like to have this capability be enabled on lookup table. > > This feature should only available when cube could be edit status. > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/310 > Created by: [lukehan|https://github.com/lukehan] > Labels: > Milestone: Backlog > Created at: Fri Dec 26 15:06:46 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-193) Show cubes and tables relationship with network visualization
[ https://issues.apache.org/jira/browse/KYLIN-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-193: Labels: github-import web-enhance (was: github-import) > Show cubes and tables relationship with network visualization > - > > Key: KYLIN-193 > URL: https://issues.apache.org/jira/browse/KYLIN-193 > Project: Kylin > Issue Type: Wish > Components: Web >Reporter: Luke Han >Priority: Minor > Labels: github-import, web-enhance > Fix For: Backlog > > > As a user, I would like to know the tables be using in one cube > also would to know all the cubes refereed to one table. > Using network diagram to show this relationship. > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/312 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: Backlog > Created at: Fri Dec 26 15:09:18 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-192) Preview data from SQL when creating/editing Cube
[ https://issues.apache.org/jira/browse/KYLIN-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-192: Labels: github-import web-enhance (was: github-import) > Preview data from SQL when creating/editing Cube > > > Key: KYLIN-192 > URL: https://issues.apache.org/jira/browse/KYLIN-192 > Project: Kylin > Issue Type: Wish > Components: Web >Reporter: Luke Han >Assignee: Zhong,Jason > Labels: github-import, web-enhance > Fix For: Future > > > As a cube designer, when I'm creating/editing my cube, I would like to have > ability to preview data which will generate cube for validation/verify and so > on, return limited records is ok, such as 100, 500. > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/313 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: Backlog > Created at: Fri Dec 26 15:11:17 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-192) Preview data from SQL when creating/editing Cube
[ https://issues.apache.org/jira/browse/KYLIN-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-192: Summary: Preview data from SQL when creating/editing Cube (was: Preview data from cube's SQL) > Preview data from SQL when creating/editing Cube > > > Key: KYLIN-192 > URL: https://issues.apache.org/jira/browse/KYLIN-192 > Project: Kylin > Issue Type: Wish > Components: Web >Reporter: Luke Han >Assignee: Zhong,Jason > Labels: github-import, web-enhance > Fix For: Future > > > As a cube designer, when I'm creating/editing my cube, I would like to have > ability to preview data which will generate cube for validation/verify and so > on, return limited records is ok, such as 100, 500. > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/313 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: Backlog > Created at: Fri Dec 26 15:11:17 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-190) Visualize Editor for cube creation/edition
[ https://issues.apache.org/jira/browse/KYLIN-190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-190: Labels: github-import web-enhance (was: github-import) > Visualize Editor for cube creation/edition > -- > > Key: KYLIN-190 > URL: https://issues.apache.org/jira/browse/KYLIN-190 > Project: Kylin > Issue Type: Wish > Components: Web >Reporter: Luke Han >Assignee: Luke Han >Priority: Minor > Labels: github-import, web-enhance > Fix For: Backlog > > > Reference: > ![image|https://cloud.githubusercontent.com/assets/1104017/5556285/b79947b0-8d11-11e4-8b4c-84d6edeee5de.png] > ![image|https://cloud.githubusercontent.com/assets/1104017/5556287/bb0e5368-8d11-11e4-8285-cb05b3dcb7f6.png] > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/315 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: Backlog > Created at: Fri Dec 26 15:13:36 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-191) Unix ODBC Driver
[ https://issues.apache.org/jira/browse/KYLIN-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-191: Labels: github-import gsoc2016 odbc (was: github-import gsoc2016) > Unix ODBC Driver > > > Key: KYLIN-191 > URL: https://issues.apache.org/jira/browse/KYLIN-191 > Project: Kylin > Issue Type: Wish > Components: Driver - ODBC >Reporter: Luke Han >Assignee: Luke Han >Priority: Minor > Labels: github-import, gsoc2016, odbc > Fix For: Backlog > > > To support more BI platform and tools, the unix ODBC driver version is > required to be enabled on the Linux/Unix based application and platform which > consume Kylin through ODBC protocol > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/314 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: Backlog > Created at: Fri Dec 26 15:12:11 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-187) Data Statistics Collection and Auto Modeling
[ https://issues.apache.org/jira/browse/KYLIN-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-187: Summary: Data Statistics Collection and Auto Modeling (was: Data Statistics Analyzer ) > Data Statistics Collection and Auto Modeling > - > > Key: KYLIN-187 > URL: https://issues.apache.org/jira/browse/KYLIN-187 > Project: Kylin > Issue Type: New Feature > Components: Tools, Build and Test >Reporter: Luke Han > Labels: github-import > Fix For: Backlog > > > 1 Overview > We need the statistics data for the following domains: > * Design cube metadata based on query log > * Design HBase row-key based on data distribution (e.g. histogram and > cardinality) > * Choose execution plan based on cuboid data > 2 Data Analyzer > We need to analyzer the hive data and cube data in 2 phases. Firstly, we will > analyze the hive to guide the 1st round design of row key. Then we will > analyze the cube data to refine the design of row key and to estimate the > cost of query. > 2.1 Analyze Hive Data > We need to analyze the following statistics data on hive table: > * Cardinality of each dimension > * Cardinality of dimension combination (optional) > * Value distribution of each dimension (optional) > Based on the statistics of hive data, we can design row key group from high > cardinality dimension to low cardinality dimension. BTW, we should evenly > split dimension into the row key group that will reduce the number of cuboid. > 2.2 Analyze Cube Data > We need to analyze the following statistics on data cube: > * Count of each cuboid > * Group ratio of each cuboid = current cuboid count / lower group base cuboid > count > 3 Query Analyzer > TBD > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/318 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: Backlog > Created at: Fri Dec 26 15:21:24 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KYLIN-2305) Unable to use long searchBase/Pattern for LDAP
[
https://issues.apache.org/jira/browse/KYLIN-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925559#comment-15925559
]
Shaofeng SHI commented on KYLIN-2305:
-
Kanta, the JIRAs won't be closed until be formally released. You can set it as
"Resolved" now to indicate it has been resolved.
> Unable to use long searchBase/Pattern for LDAP
> --
>
> Key: KYLIN-2305
> URL: https://issues.apache.org/jira/browse/KYLIN-2305
> Project: Kylin
> Issue Type: Bug
>Affects Versions: v1.6.0
>Reporter: mathias kluba
>Assignee: Kanta Kuramoto
> Fix For: v2.0.0
>
> Attachments: KYLIN-2305.patch
>
>
> I try to use LDAP authentication.
> I set the ldap.user.searchBase & ldap.user.searchPattern &
> ldap.user.groupSearchBase
> I followed the documentation
> http://kylin.apache.org/docs/howto/howto_ldap_and_sso.html
> It crashed because of:
> {code}
> Failed to parse DN; nested exception is
> org.springframework.ldap.core.TokenMgrError: Lexical error at line 1, column
> 38. Encountered: "." (46), after : ""
> {code}
> I change the logger configuration to have debug to understand the query done
> using Spring Security LdapTemplate.
> It seems that it trim the value at column 38 and add "..."
> I can't tell you my real AD path, but here is an example:
> in kylin.properties:
> {code}
>
> ldap.user.searchBase=OU=Users,OU=Accounts,OU=FR,OU=ABCDE,OU=FGHIJ,DC=MYCOMPANY,DC=COM
> {code}
> Debug log:
> {code}
> 2016-12-20 14:04:41,242 DEBUG [http-bio-7070-exec-1]
> search.FilterBasedLdapUserSearch:107 : Searching for user 'mylogin', with
> user search [ searchFilter: '(sAMAccountName={0})', searchBase:
> 'OU=Users,OU=Accounts,OU=FR,OU=ABCDE,O...', scope: subtree, searchTimeLimit:
> 0, derefLinkFlag: false ]
> {code}
> I change the searchBase to be shorted (less than 38 char) and it seems that
> the bug is the same with the searchPattern and the groupSearchBase.
> I don't know where Kylin is reading these properties, but it seems that it
> doesn't use the right function (maybe toString() that trim the value?)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (KYLIN-185) Display Hadoop System Components Status
[ https://issues.apache.org/jira/browse/KYLIN-185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roger Shi updated KYLIN-185: Summary: Display Hadoop System Components Status (was: Display Hadoo System Components Status) > Display Hadoop System Components Status > --- > > Key: KYLIN-185 > URL: https://issues.apache.org/jira/browse/KYLIN-185 > Project: Kylin > Issue Type: Wish > Components: Web >Reporter: Luke Han > Labels: github-import > Fix For: Backlog > > > As an administrator, I would like to have one single view to know all > dependency's status, including: > 1. HDFS > 2. Hive > 3. HBase > 4. ZooKeeper > 5. MySQL > 6. Kerberos > 7. LDAP > 8. Others. > Imported from GitHub > Url: https://github.com/KylinOLAP/Kylin/issues/320 > Created by: [lukehan|https://github.com/lukehan] > Labels: newfeature, > Milestone: Backlog > Created at: Fri Dec 26 15:22:53 CST 2014 > State: open -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KYLIN-2507) curl usage in kylin
[
https://issues.apache.org/jira/browse/KYLIN-2507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
prasannaP updated KYLIN-2507:
-
Description:
Hi all,
can you please tell me what values i have to give in curl command for kylin
rebuild.can you explain me where i have to get startTime,endTime values.I am
using like the below,
/usr/bin/curl -c /home/hdfs/cookiefile.txt -X POST -H "Authorization: Basic
QURNSU46S1lMSU4 =" -H 'Content-Type: application/json'
http://ipaddress:7070/kylin/api/user/authentication
/usr/bin/curl -b /home/hdfs/cookiefile.txt -X PUT -H 'Content-Type:
application/json' -d '{"startTime":'142538400', "endTime": '148915650',
"buildType":"BUILD"}'
http://ipaddress:7070/kylin/api/cubes/analytics_cube/rebuild
here i am getting startTime and endTime from
http://ipaddress:7070/kylin/api/cubes/analytics_cube of date_range_start and
date_range_end.am i using proper once or not.
In manual build we can specify endDate of cube,but in curl where we can specify
end Date?anybody can you please explain me all these doubts.
was:
Hi all,
can you please tell me what values i have to give in curl command for kylin
rebuild.can you explain me where i have to get those values.I am using like the
below,
/usr/bin/curl -c /home/hdfs/cookiefile.txt -X POST -H "Authorization: Basic
QURNSU46S1lMSU4 =" -H 'Content-Type: application/json'
http://ipaddress:7070/kylin/api/user/authentication
/usr/bin/curl -b /home/hdfs/cookiefile.txt -X PUT -H 'Content-Type:
application/json' -d '{"startTime":'142538400', "endTime": '148915650',
"buildType":"BUILD"}'
http://ipaddress:7070/kylin/api/cubes/analytics_cube/rebuild
here i am getting startTime and endTime from
http://ipaddress:7070/kylin/api/cubes/analytics_cube of date_range_start and
date_range_end.am i using proper once or not.
In manual build we can specify endDate of cube,but in curl where we can specify
end Date?anybody can you please explain me all these doubts.
> curl usage in kylin
> ---
>
> Key: KYLIN-2507
> URL: https://issues.apache.org/jira/browse/KYLIN-2507
> Project: Kylin
> Issue Type: Bug
>Affects Versions: v1.6.0
> Environment: kylin
>Reporter: prasannaP
>
> Hi all,
> can you please tell me what values i have to give in curl command for kylin
> rebuild.can you explain me where i have to get startTime,endTime values.I am
> using like the below,
> /usr/bin/curl -c /home/hdfs/cookiefile.txt -X POST -H "Authorization: Basic
> QURNSU46S1lMSU4 =" -H 'Content-Type: application/json'
> http://ipaddress:7070/kylin/api/user/authentication
> /usr/bin/curl -b /home/hdfs/cookiefile.txt -X PUT -H 'Content-Type:
> application/json' -d '{"startTime":'142538400', "endTime":
> '148915650', "buildType":"BUILD"}'
> http://ipaddress:7070/kylin/api/cubes/analytics_cube/rebuild
> here i am getting startTime and endTime from
> http://ipaddress:7070/kylin/api/cubes/analytics_cube of date_range_start and
> date_range_end.am i using proper once or not.
> In manual build we can specify endDate of cube,but in curl where we can
> specify end Date?anybody can you please explain me all these doubts.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (KYLIN-2507) curl usage in kylin
[
https://issues.apache.org/jira/browse/KYLIN-2507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
prasannaP updated KYLIN-2507:
-
Issue Type: Wish (was: Bug)
> curl usage in kylin
> ---
>
> Key: KYLIN-2507
> URL: https://issues.apache.org/jira/browse/KYLIN-2507
> Project: Kylin
> Issue Type: Wish
>Affects Versions: v1.6.0
> Environment: kylin
>Reporter: prasannaP
>
> Hi all,
> can you please tell me what values i have to give in curl command for kylin
> rebuild.can you explain me where i have to get those values.I am using like
> the below,
> /usr/bin/curl -c /home/hdfs/cookiefile.txt -X POST -H "Authorization: Basic
> QURNSU46S1lMSU4 =" -H 'Content-Type: application/json'
> http://ipaddress:7070/kylin/api/user/authentication
> /usr/bin/curl -b /home/hdfs/cookiefile.txt -X PUT -H 'Content-Type:
> application/json' -d '{"startTime":'142538400', "endTime":
> '148915650', "buildType":"BUILD"}'
> http://ipaddress:7070/kylin/api/cubes/analytics_cube/rebuild
> here i am getting startTime and endTime from
> http://ipaddress:7070/kylin/api/cubes/analytics_cube of date_range_start and
> date_range_end.am i using proper once or not.
> In manual build we can specify endDate of cube,but in curl where we can
> specify end Date?anybody can you please explain me all these doubts.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (KYLIN-2507) curl usage in kylin
[
https://issues.apache.org/jira/browse/KYLIN-2507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
prasannaP updated KYLIN-2507:
-
Issue Type: Bug (was: Wish)
> curl usage in kylin
> ---
>
> Key: KYLIN-2507
> URL: https://issues.apache.org/jira/browse/KYLIN-2507
> Project: Kylin
> Issue Type: Bug
>Affects Versions: v1.6.0
> Environment: kylin
>Reporter: prasannaP
>
> Hi all,
> can you please tell me what values i have to give in curl command for kylin
> rebuild.can you explain me where i have to get those values.I am using like
> the below,
> /usr/bin/curl -c /home/hdfs/cookiefile.txt -X POST -H "Authorization: Basic
> QURNSU46S1lMSU4 =" -H 'Content-Type: application/json'
> http://ipaddress:7070/kylin/api/user/authentication
> /usr/bin/curl -b /home/hdfs/cookiefile.txt -X PUT -H 'Content-Type:
> application/json' -d '{"startTime":'142538400', "endTime":
> '148915650', "buildType":"BUILD"}'
> http://ipaddress:7070/kylin/api/cubes/analytics_cube/rebuild
> here i am getting startTime and endTime from
> http://ipaddress:7070/kylin/api/cubes/analytics_cube of date_range_start and
> date_range_end.am i using proper once or not.
> In manual build we can specify endDate of cube,but in curl where we can
> specify end Date?anybody can you please explain me all these doubts.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (KYLIN-2507) curl usage in kylin
[
https://issues.apache.org/jira/browse/KYLIN-2507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
prasannaP updated KYLIN-2507:
-
Affects Version/s: v1.6.0
> curl usage in kylin
> ---
>
> Key: KYLIN-2507
> URL: https://issues.apache.org/jira/browse/KYLIN-2507
> Project: Kylin
> Issue Type: Bug
>Affects Versions: v1.6.0
> Environment: kylin
>Reporter: prasannaP
>
> Hi all,
> can you please tell me what values i have to give in curl command for kylin
> rebuild.can you explain me where i have to get those values.I am using like
> the below,
> /usr/bin/curl -c /home/hdfs/cookiefile.txt -X POST -H "Authorization: Basic
> QURNSU46S1lMSU4 =" -H 'Content-Type: application/json'
> http://ipaddress:7070/kylin/api/user/authentication
> /usr/bin/curl -b /home/hdfs/cookiefile.txt -X PUT -H 'Content-Type:
> application/json' -d '{"startTime":'142538400', "endTime":
> '148915650', "buildType":"BUILD"}'
> http://ipaddress:7070/kylin/api/cubes/analytics_cube/rebuild
> here i am getting startTime and endTime from
> http://ipaddress:7070/kylin/api/cubes/analytics_cube of date_range_start and
> date_range_end.am i using proper once or not.
> In manual build we can specify endDate of cube,but in curl where we can
> specify end Date?anybody can you please explain me all these doubts.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (KYLIN-2507) curl usage in kylin
prasannaP created KYLIN-2507:
Summary: curl usage in kylin
Key: KYLIN-2507
URL: https://issues.apache.org/jira/browse/KYLIN-2507
Project: Kylin
Issue Type: Bug
Environment: kylin
Reporter: prasannaP
Hi all,
can you please tell me what values i have to give in curl command for kylin
rebuild.can you explain me where i have to get those values.I am using like the
below,
/usr/bin/curl -c /home/hdfs/cookiefile.txt -X POST -H "Authorization: Basic
QURNSU46S1lMSU4 =" -H 'Content-Type: application/json'
http://ipaddress:7070/kylin/api/user/authentication
/usr/bin/curl -b /home/hdfs/cookiefile.txt -X PUT -H 'Content-Type:
application/json' -d '{"startTime":'142538400', "endTime": '148915650',
"buildType":"BUILD"}'
http://ipaddress:7070/kylin/api/cubes/analytics_cube/rebuild
here i am getting startTime and endTime from
http://ipaddress:7070/kylin/api/cubes/analytics_cube of date_range_start and
date_range_end.am i using proper once or not.
In manual build we can specify endDate of cube,but in curl where we can specify
end Date?anybody can you please explain me all these doubts.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (KYLIN-2506) Refactor Global Dictionary
[ https://issues.apache.org/jira/browse/KYLIN-2506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925495#comment-15925495 ] kangkaisen commented on KYLIN-2506: --- The cube only has one segment means the cube doesn't have Partition Date Column, which is a common situation. User queries don't need aggregate across segments is also a common situation, which doesn't mean user need to guarantee how many segments would be and doesn't conflict with the merge. As to the transparency of segment, I think which is a ideal target we always pursue. But actually，If user don't know what is segment, how should we explain "MERGE", "Retention" some concepts to user. Besides，the concept of segment isn't complex and which is a common concept of OLAP domain. If I think wrong, please correct me. Thanks you. > Refactor Global Dictionary > -- > > Key: KYLIN-2506 > URL: https://issues.apache.org/jira/browse/KYLIN-2506 > Project: Kylin > Issue Type: Improvement > Components: General >Affects Versions: v2.0.0 >Reporter: kangkaisen >Assignee: kangkaisen > Fix For: v2.0.0 > > > The main points of this refactor: > 1 Fix the bug that the RemoveListener of LoadingCache swallowed any > exceptions when building the GlobalDict. > 2 Fix the bug that the HDFS filename of DictSliceKey had Illegal characters. > 3 Fix the bug that the HDFS filename of DictSliceKey maybe longer than 255. > 4 Fix the bug that DictNode split failed if value length greater than 255 > bytes. > 5 Decouple the build and query of GlobalDict: > Abstract the builder of AppendTrieDictionary to AppendTrieDictionaryBuilder; > Add LoadingCache to AppendTrieDictionary and make AppendTrieDictionary is > only readable. > 6 Remove dependence of LoadingCache when building the GlobalDict. > 7 Abstract the HDFS operations to GlobalDictStore. > 8 Abstract the metadata of GlobalDict to GlobalDictMetadata. > 9 Delete CachedTreeMap. > 10 Remove the support of multithreading concurrent build and I will add > distributed lock for GlobalDict later. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (KYLIN-2305) Unable to use long searchBase/Pattern for LDAP
[
https://issues.apache.org/jira/browse/KYLIN-2305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15925422#comment-15925422
]
Kanta Kuramoto commented on KYLIN-2305:
---
Thank you for the review and merging the patch, [~yimingliu] and
[~Shaofengshi]. Can I close this JIRA?
> Unable to use long searchBase/Pattern for LDAP
> --
>
> Key: KYLIN-2305
> URL: https://issues.apache.org/jira/browse/KYLIN-2305
> Project: Kylin
> Issue Type: Bug
>Affects Versions: v1.6.0
>Reporter: mathias kluba
>Assignee: Kanta Kuramoto
> Fix For: v2.0.0
>
> Attachments: KYLIN-2305.patch
>
>
> I try to use LDAP authentication.
> I set the ldap.user.searchBase & ldap.user.searchPattern &
> ldap.user.groupSearchBase
> I followed the documentation
> http://kylin.apache.org/docs/howto/howto_ldap_and_sso.html
> It crashed because of:
> {code}
> Failed to parse DN; nested exception is
> org.springframework.ldap.core.TokenMgrError: Lexical error at line 1, column
> 38. Encountered: "." (46), after : ""
> {code}
> I change the logger configuration to have debug to understand the query done
> using Spring Security LdapTemplate.
> It seems that it trim the value at column 38 and add "..."
> I can't tell you my real AD path, but here is an example:
> in kylin.properties:
> {code}
>
> ldap.user.searchBase=OU=Users,OU=Accounts,OU=FR,OU=ABCDE,OU=FGHIJ,DC=MYCOMPANY,DC=COM
> {code}
> Debug log:
> {code}
> 2016-12-20 14:04:41,242 DEBUG [http-bio-7070-exec-1]
> search.FilterBasedLdapUserSearch:107 : Searching for user 'mylogin', with
> user search [ searchFilter: '(sAMAccountName={0})', searchBase:
> 'OU=Users,OU=Accounts,OU=FR,OU=ABCDE,O...', scope: subtree, searchTimeLimit:
> 0, derefLinkFlag: false ]
> {code}
> I change the searchBase to be shorted (less than 38 char) and it seems that
> the bug is the same with the searchPattern and the groupSearchBase.
> I don't know where Kylin is reading these properties, but it seems that it
> doesn't use the right function (maybe toString() that trim the value?)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (KYLIN-2457) Should copy the latest dictionaries on dimension tables in a batch merge job
[ https://issues.apache.org/jira/browse/KYLIN-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] cheney.liu updated KYLIN-2457: -- Attachment: kylintools.7z we develop a tool executed by command line to fix historic data . > Should copy the latest dictionaries on dimension tables in a batch merge job > > > Key: KYLIN-2457 > URL: https://issues.apache.org/jira/browse/KYLIN-2457 > Project: Kylin > Issue Type: Bug >Affects Versions: v1.6.0 >Reporter: zhengdong >Assignee: zhengdong >Priority: Critical > Fix For: v2.0.0 > > Attachments: > 0001-KYLIN-2457-Should-copy-the-latest-dictionaries-on-di.patch, kylintools.7z > > > In a batch merge job, we need to create dictionaries for all dimensions for > the new segment. For those dictionaries on dimension table, we currently just > copy them from the earliest segment of the merging segments. > However, we should select the newest dictionary for the new segment, since > the incremental dimension table is allowed. The older dictionary can't find > the records corresponding to the new key added to a dimension table and lead > wrong query result. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
