[jira] [Created] (KYLIN-4295) Instances displayed on Query Node are inconsistent with Job Node
Temple Zhou created KYLIN-4295: -- Summary: Instances displayed on Query Node are inconsistent with Job Node Key: KYLIN-4295 URL: https://issues.apache.org/jira/browse/KYLIN-4295 Project: Kylin Issue Type: Bug Components: Web Affects Versions: v3.0.0-alpha2 Reporter: Temple Zhou Attachments: 4691576071454_.pic_hd.jpg, 4731576071552_.pic_hd.jpg As shown in attachments -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KYLIN-4265) SQL tab of cube failed when filter is not empty
Temple Zhou created KYLIN-4265: -- Summary: SQL tab of cube failed when filter is not empty Key: KYLIN-4265 URL: https://issues.apache.org/jira/browse/KYLIN-4265 Project: Kylin Issue Type: Bug Components: Metadata Affects Versions: all Reporter: Temple Zhou Assignee: Temple Zhou Attachments: screenshot.png The SQL tab of Cube with filter condition will be failed to display. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KYLIN-4229) String index out of range -1
Temple Zhou created KYLIN-4229: -- Summary: String index out of range -1 Key: KYLIN-4229 URL: https://issues.apache.org/jira/browse/KYLIN-4229 Project: Kylin Issue Type: Bug Components: Job Engine Affects Versions: v3.0.0-beta Reporter: Temple Zhou Assignee: Temple Zhou Build cube with "where clause to filter data from source" will get the error "String index out of range -1" -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KYLIN-4228) Not a valid ID: xxx while executing SQL
Temple Zhou created KYLIN-4228: -- Summary: Not a valid ID: xxx while executing SQL Key: KYLIN-4228 URL: https://issues.apache.org/jira/browse/KYLIN-4228 Project: Kylin Issue Type: Bug Components: Query Engine Affects Versions: v3.0.0-beta Reporter: Temple Zhou Assignee: Temple Zhou -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KYLIN-4202) Tableau Server failed with "Access violation - no RTTI data!"
Temple Zhou created KYLIN-4202: -- Summary: Tableau Server failed with "Access violation - no RTTI data!" Key: KYLIN-4202 URL: https://issues.apache.org/jira/browse/KYLIN-4202 Project: Kylin Issue Type: Bug Affects Versions: v3.0.0-alpha2, v2.6.0, v2.5.0 Reporter: Temple Zhou Assignee: Temple Zhou I can open the reports using Tableau Desktop with *JDBC Driver*, but the reposts will failed if I publish it to Tableau Server. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KYLIN-4189) Prevent abnormal CPU usage by limiting lookup table's rows
Temple Zhou created KYLIN-4189:
--
Summary: Prevent abnormal CPU usage by limiting lookup table's rows
Key: KYLIN-4189
URL: https://issues.apache.org/jira/browse/KYLIN-4189
Project: Kylin
Issue Type: Improvement
Components: Query Engine
Affects Versions: v2.6.0, v2.5.0, v2.4.0
Reporter: Temple Zhou
Assignee: Temple Zhou
Although lookup table size is limited, snapshot table with too many rows will
break the server.
Such as:
{code:sql}
select
dim.b
FROM
fact
INNER JOIN dim ON fact.B = dim.B
group by
dim.b
{code}
If the number of rows in column dim.B is million, the query will execute for
dozens seconds and the CPU utilization is extremely high.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (KYLIN-4181) Schedule Kylin using Kubernetes
Temple Zhou created KYLIN-4181: -- Summary: Schedule Kylin using Kubernetes Key: KYLIN-4181 URL: https://issues.apache.org/jira/browse/KYLIN-4181 Project: Kylin Issue Type: New Feature Components: Others Reporter: Temple Zhou Assignee: Temple Zhou Fix For: Future -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KYLIN-4180) Prevent abnormal CPU usage by limiting flat filters length
Temple Zhou created KYLIN-4180:
--
Summary: Prevent abnormal CPU usage by limiting flat filters length
Key: KYLIN-4180
URL: https://issues.apache.org/jira/browse/KYLIN-4180
Project: Kylin
Issue Type: Improvement
Components: Metadata
Affects Versions: v2.6.0, v2.5.0, v2.4.0
Reporter: Temple Zhou
Assignee: Temple Zhou
The following SQL will lead to the list returned by
org.apache.kylin.metadata.filter.TupleFilter#cartesianProduct become very
large, and the process to producing the List will use lots of CPU.
{code:sql}
select * from temp.test_filter
where ((a >= 0 and a <= 1)
or(a >= 1 and a <= 2)
or(a >= 2 and a <= 3)
...
or(a >= 300 and a <= 301)
) and ((b >= 0 and b <= 1)
or(b >= 1 and b <= 2)
or(b >= 2 and b <= 3)
...
or(b >= 300 and b <= 301)
)
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (KYLIN-4137) Delete expired table resource path in metastore
Temple Zhou created KYLIN-4137: -- Summary: Delete expired table resource path in metastore Key: KYLIN-4137 URL: https://issues.apache.org/jira/browse/KYLIN-4137 Project: Kylin Issue Type: Bug Components: Metadata Affects Versions: v2.6.0, v2.5.0, v2.4.0, v2.3.0, v2.2.0, Future Reporter: Temple Zhou Assignee: Temple Zhou -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (KYLIN-4074) Exception in thread "Memcached IO over {MemcachedConnection to ..." java.lang.NullPointerException
Temple Zhou created KYLIN-4074:
--
Summary: Exception in thread "Memcached IO over
{MemcachedConnection to ..." java.lang.NullPointerException
Key: KYLIN-4074
URL: https://issues.apache.org/jira/browse/KYLIN-4074
Project: Kylin
Issue Type: Bug
Affects Versions: v2.6.2, v2.5.0, v2.4.0
Reporter: Temple Zhou
Assignee: Temple Zhou
This exception will lead to the failure of thread "Memcached IO over
{MemcachedConnection to ...}",
so, the inputQueue of memcache client will be blocked, and every request will
take 2000ms (timeout).
The log is as follows:
{code:log}
2019-07-01 15:21:24,039 INFO [Query
3f75c477-9c38-35bf-24a0-656459d9ebb1-212641] v2.CubeHBaseEndpointRPC:197 :
Query-3f75c477-9c38-35bf-24a0-656459d9ebb1: no segment result is cached for
segment:1102_pv_uv_users_di[2016070100_2017010100], take time:2000ms
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KYLIN-4053) Compare date with timestamp
Temple Zhou created KYLIN-4053: -- Summary: Compare date with timestamp Key: KYLIN-4053 URL: https://issues.apache.org/jira/browse/KYLIN-4053 Project: Kylin Issue Type: Sub-task Affects Versions: Future Reporter: Temple Zhou Assignee: Temple Zhou -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-4052) Improve compatibility with the Tableau 2019.x
Temple Zhou created KYLIN-4052: -- Summary: Improve compatibility with the Tableau 2019.x Key: KYLIN-4052 URL: https://issues.apache.org/jira/browse/KYLIN-4052 Project: Kylin Issue Type: Improvement Affects Versions: Future Reporter: Temple Zhou Assignee: Temple Zhou -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-4033) Can not access Kerberized Cluster with DebugTomcat
Temple Zhou created KYLIN-4033: -- Summary: Can not access Kerberized Cluster with DebugTomcat Key: KYLIN-4033 URL: https://issues.apache.org/jira/browse/KYLIN-4033 Project: Kylin Issue Type: Improvement Components: Tools, Build and Test Affects Versions: all Reporter: Temple Zhou Assignee: Temple Zhou When I start the Kylin Server using DebugTomcat, the cubing job will fail because of "GSSException: No valid credentials provided (Mechanism level: Failed to find any Kerberos tgt)]" -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-4028) Speed up startup progress using cached dependency
Temple Zhou created KYLIN-4028: -- Summary: Speed up startup progress using cached dependency Key: KYLIN-4028 URL: https://issues.apache.org/jira/browse/KYLIN-4028 Project: Kylin Issue Type: Improvement Components: Others Affects Versions: all Reporter: Temple Zhou Assignee: Temple Zhou The hive/hadoop/hbase dependencies are not volatile, and finding the dependencies every time I start the Kylin server will slow down the startup speed. So, if there are dependencies generated by previous running, we can use it to start the server without finding the dependencies again. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3978) InternalErrorException: null with precise count distinct
Temple Zhou created KYLIN-3978: -- Summary: InternalErrorException: null with precise count distinct Key: KYLIN-3978 URL: https://issues.apache.org/jira/browse/KYLIN-3978 Project: Kylin Issue Type: Bug Reporter: Temple Zhou Assignee: Temple Zhou when kylin.query.segment-cache-enabled=true and sql with precise count distinct, the InternalErrorException: null happens sometimes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3898) Cube level properties are ineffective in the some build steps
Temple Zhou created KYLIN-3898: -- Summary: Cube level properties are ineffective in the some build steps Key: KYLIN-3898 URL: https://issues.apache.org/jira/browse/KYLIN-3898 Project: Kylin Issue Type: Bug Components: Job Engine Affects Versions: v2.6.0, v2.5.0, v2.4.0 Reporter: Temple Zhou Assignee: Temple Zhou -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3892) Set cubing job priority
Temple Zhou created KYLIN-3892: -- Summary: Set cubing job priority Key: KYLIN-3892 URL: https://issues.apache.org/jira/browse/KYLIN-3892 Project: Kylin Issue Type: New Feature Components: Job Engine Affects Versions: v2.6.0, v2.5.0, v2.4.0 Reporter: Temple Zhou Assignee: Temple Zhou The cubing job with high priority will be delayed when there are too many tasks running. So I want to set the job priority for the important cubing jobs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3819) kylin.sh run in the foreground
Temple Zhou created KYLIN-3819: -- Summary: kylin.sh run in the foreground Key: KYLIN-3819 URL: https://issues.apache.org/jira/browse/KYLIN-3819 Project: Kylin Issue Type: Improvement Components: Tools, Build and Test Affects Versions: v2.6.0, v2.5.0, v2.4.0 Reporter: Temple Zhou Assignee: Temple Zhou The "kylin.sh start" can only run kylin in the background, but it should be run in the foreground as well. Because only in this way, both streams can be captured if using a supervision system like daemontools. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3772) CubeMetaIngester works abnormally
Temple Zhou created KYLIN-3772: -- Summary: CubeMetaIngester works abnormally Key: KYLIN-3772 URL: https://issues.apache.org/jira/browse/KYLIN-3772 Project: Kylin Issue Type: Bug Components: Tools, Build and Test Affects Versions: v2.6.0, v2.5.0, v2.4.0, v2.3.0 Reporter: Temple Zhou Assignee: Temple Zhou -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3770) ZipFileUtils is not compatible CubeMetaIngester
Temple Zhou created KYLIN-3770: -- Summary: ZipFileUtils is not compatible CubeMetaIngester Key: KYLIN-3770 URL: https://issues.apache.org/jira/browse/KYLIN-3770 Project: Kylin Issue Type: Bug Components: Tools, Build and Test Affects Versions: v2.6.0, v2.5.0, v2.4.0, v2.3.0 Reporter: Temple Zhou Assignee: Temple Zhou -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3767) Print the malformed JSON data consumed from Kafka Topic
Temple Zhou created KYLIN-3767:
--
Summary: Print the malformed JSON data consumed from Kafka Topic
Key: KYLIN-3767
URL: https://issues.apache.org/jira/browse/KYLIN-3767
Project: Kylin
Issue Type: Improvement
Components: Job Engine
Affects Versions: v2.4.0, v2.3.0, v2.2.0
Reporter: Temple Zhou
Assignee: Temple Zhou
Print the malformed JSON data consumed from Kafka Topic
Recently, I found that my cube with streaming data built failed, so I checked
the syslog in the failed MR job.
But the log contents didn't help, which is as follows:
{code:java}
2019-01-11 15:12:48,774 INFO [main]
org.apache.kylin.source.kafka.hadoop.KafkaInputRecordReader:
kylin-full-site-pvuv:kafka4:9092:2 fetching offset 1537268
2019-01-11 15:12:48,776 INFO [main]
org.apache.kylin.source.kafka.hadoop.KafkaInputRecordReader:
kylin-full-site-pvuv:kafka4:9092:2 fetching offset 1537768
2019-01-11 15:12:48,778 INFO [main]
org.apache.kylin.source.kafka.hadoop.KafkaInputRecordReader:
kylin-full-site-pvuv:kafka4:9092:2 fetching offset 1538268
2019-01-11 15:12:48,781 INFO [main]
org.apache.kylin.source.kafka.hadoop.KafkaInputRecordReader:
kylin-full-site-pvuv:kafka4:9092:2 fetching offset 1538768
2019-01-11 15:12:48,783 INFO [main]
org.apache.kylin.source.kafka.hadoop.KafkaInputRecordReader:
kylin-full-site-pvuv:kafka4:9092:2 fetching offset 1539268
2019-01-11 15:12:48,787 ERROR [main]
org.apache.kylin.source.kafka.TimedJsonStreamParser: error
org.apache.kylin.job.shaded.com.fasterxml.jackson.core.JsonParseException:
Unrecognized character escape 'h' (code 104)
at [Source: (org.apache.kylin.common.util.ByteBufferBackedInputStream); line:
1, column: 207]
at
org.apache.kylin.job.shaded.com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:1804)
at
org.apache.kylin.job.shaded.com.fasterxml.jackson.core.base.ParserMinimalBase._reportError(ParserMinimalBase.java:663)
at
org.apache.kylin.job.shaded.com.fasterxml.jackson.core.base.ParserMinimalBase._handleUnrecognizedCharacterEscape(ParserMinimalBase.java:640)
at
org.apache.kylin.job.shaded.com.fasterxml.jackson.core.json.UTF8StreamJsonParser._decodeEscaped(UTF8StreamJsonParser.java:3243)
at
org.apache.kylin.job.shaded.com.fasterxml.jackson.core.json.UTF8StreamJsonParser._finishString2(UTF8StreamJsonParser.java:2452)
at
org.apache.kylin.job.shaded.com.fasterxml.jackson.core.json.UTF8StreamJsonParser._finishAndReturnString(UTF8StreamJsonParser.java:2407)
at
org.apache.kylin.job.shaded.com.fasterxml.jackson.core.json.UTF8StreamJsonParser.getText(UTF8StreamJsonParser.java:269)
at
org.apache.kylin.job.shaded.com.fasterxml.jackson.databind.deser.std.UntypedObjectDeserializer$Vanilla.deserialize(UntypedObjectDeserializer.java:672)
at
org.apache.kylin.job.shaded.com.fasterxml.jackson.databind.deser.std.MapDeserializer._readAndBindStringKeyMap(MapDeserializer.java:527)
at
org.apache.kylin.job.shaded.com.fasterxml.jackson.databind.deser.std.MapDeserializer.deserialize(MapDeserializer.java:364)
at
org.apache.kylin.job.shaded.com.fasterxml.jackson.databind.deser.std.MapDeserializer.deserialize(MapDeserializer.java:29)
at
org.apache.kylin.job.shaded.com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:4001)
at
org.apache.kylin.job.shaded.com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:3072)
at
org.apache.kylin.source.kafka.TimedJsonStreamParser.parse(TimedJsonStreamParser.java:112)
at
org.apache.kylin.source.kafka.hadoop.KafkaFlatTableMapper.doMap(KafkaFlatTableMapper.java:87)
at
org.apache.kylin.source.kafka.hadoop.KafkaFlatTableMapper.doMap(KafkaFlatTableMapper.java:48)
at org.apache.kylin.engine.mr.KylinMapper.map(KylinMapper.java:77)
at org.apache.hadoop.mapreduce.Mapper.run(Mapper.java:145)
at org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:793)
at org.apache.hadoop.mapred.MapTask.run(MapTask.java:341)
at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:164)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:422)
at
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1917)
at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158)
{code}
Maybe, the malformed json data should be printed in the syslog, which can help
me to troubleshooting.
Just like that:
{code:java}
...
2019-01-11 15:12:48,778 INFO [main]
org.apache.kylin.source.kafka.hadoop.KafkaInputRecordReader:
kylin-full-site-pvuv:kafka4:9092:2 fetching offset 1538268
2019-01-11 15:12:48,781 INFO [main]
org.apache.kylin.source.kafka.hadoop.KafkaInputRecordReader:
kylin-full-site-pvuv:kafka4:9092:2 fetching offset 1538768
2019-01-11 15:12:48,783 INFO [main]
org.apache.kylin.source.kafka.hadoop.KafkaInputRecordReader:
kylin-full-site-pvuv:kafka4:9092:2 fetching offset
[jira] [Created] (KYLIN-3718) Segments in volatile range is more than designated value
Temple Zhou created KYLIN-3718:
--
Summary: Segments in volatile range is more than designated value
Key: KYLIN-3718
URL: https://issues.apache.org/jira/browse/KYLIN-3718
Project: Kylin
Issue Type: Bug
Components: Metadata
Affects Versions: v2.5.0, v2.4.0, v2.3.0
Reporter: Temple Zhou
Assignee: Temple Zhou
I have designated the volatile value of the cube to 1 and the auto merge
thresholds is 3, but I found the former 3 segments was not merged when the 4th
segment was ready.
the ready segments are as below:
# xxx[2018120100_2018120200]
# xxx[2018120200_2018120300]
# xxx[2018120300_2018120400]
# xxx[2018120400_2018120500]
Besides, I found the log info:
{code:java}
2018-12-13 16:30:48,065 WARN [Thread-799] model.Segments:182 : segment in
volatile range: xxx[2018120300_2018120400]rangeStart:154396800,
rangeEnd154405440
2018-12-13 16:30:48,065 WARN [Thread-799] model.Segments:182 : segment in
volatile range: xxx[2018120400_2018120500]rangeStart:154405440,
rangeEnd154414080{code}
I think the expected result should be:
seg: xxx[2018120400_2018120500] should be reserved
seg:
xxx[2018120100_2018120200],xxx[2018120200_2018120300],xxx[2018120300_2018120400]
should be merged.
However, the truth is:
When the 5th segments was ready, the former 3 segments were automatically
merged.
Although the value of volatile range is 1, there are always 2 segments will be
reserved.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KYLIN-3501) Cube Data Exporter & Importer
Temple Zhou created KYLIN-3501: -- Summary: Cube Data Exporter & Importer Key: KYLIN-3501 URL: https://issues.apache.org/jira/browse/KYLIN-3501 Project: Kylin Issue Type: Wish Components: Tools, Build and Test Affects Versions: v2.4.0, v2.3.1, v2.3.0, v2.2.0, v2.1.0 Reporter: Temple Zhou I think the performance problems is inevitable. So, I often migrate the cube from PROD ENV to DEV ENV for performance tunning. My steps: 1. find the related metadata of the cube and export the metadata; 2. find the related hive table and export the table data; 3. import the cube metadata and load the hive table data 4. build the cube How about integrating the steps into a tool? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3474) get malformed token with Cluster Mode(multi-query)
Temple Zhou created KYLIN-3474:
--
Summary: get malformed token with Cluster Mode(multi-query)
Key: KYLIN-3474
URL: https://issues.apache.org/jira/browse/KYLIN-3474
Project: Kylin
Issue Type: Bug
Components: Query Engine, Security
Affects Versions: v2.4.0
Reporter: Temple Zhou
I found that when I use Tableau 10.5 with Kylin 2.4.0(multi-query) , the
Tableau Server will get the malformed token error when do query via restful API.
However, when I use Tableau 10.5 with Kylin 2.4.0(single query instance), the
error will be gone.
Now, I just annotate the following
lines(org.apache.kylin.rest.security.KylinAuthenticationProvider 84-87) and the
Tableau 10.5 can run regularly with Kylin 2.4.0(multi-query).
{code:java}
@Override
public Authentication authenticate(Authentication authentication) throws
AuthenticationException {
byte[] hashKey = hf.hashString(authentication.getName() +
authentication.getCredentials()).asBytes();
String userKey = Arrays.toString(hashKey);
// if (userService.isEvictCacheFlag()) {
// userCache.invalidateAll();
// userService.setEvictCacheFlag(false);
// }
Authentication authed = userCache.getIfPresent(userKey);
if (null != authed) {
SecurityContextHolder.getContext().setAuthentication(authed);
} else {
{code}
I don't know if you tested the Kylin(multi-query) Cluster Mode with Tableau?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (KYLIN-3460) {fn CURRENT_DATE()} parse error
Temple Zhou created KYLIN-3460:
--
Summary: {fn CURRENT_DATE()} parse error
Key: KYLIN-3460
URL: https://issues.apache.org/jira/browse/KYLIN-3460
Project: Kylin
Issue Type: Bug
Components: Driver - ODBC
Affects Versions: v2.4.0, v2.3.1, v2.3.0
Reporter: Temple Zhou
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
