btw "Calculate HTable Region Splits" should not cause OOM, can you do an
analysis on the dump?
On Mon, Jan 18, 2016 at 3:48 PM, hongbin ma wrote:
> what's the size of the cube you're building? the default configuration for
> Xmx and Xms is not very big.
>
> kylin does provided sth similar to wha
what's the size of the cube you're building? the default configuration for
Xmx and Xms is not very big.
kylin does provided sth similar to what you meant by "different
lifecycles", checkout
http://kylin.apache.org/docs/install/kylin_cluster.html. The reason why we
put them into same tomcat instanc
Dong Li created KYLIN-1327:
--
Summary: Tool for batch updating host information of htables
Key: KYLIN-1327
URL: https://issues.apache.org/jira/browse/KYLIN-1327
Project: Kylin
Issue Type: Improvement
Hi,
I was trying to play Kylin 1.2 in HDP sandbox, but unfortunately it always
fails while it builds cube through Kylin service. The symptom is that Kylin
tomcat service failed each time when it is about in the step 12, which
is "Calculate
HTable Region Splits"
I suspected it is out-of-memory iss
Firstly, kylin do not distinguish which kind table in hive, if only you
can query it in hive, so the table can be normal table, external table,
view or table with some serdes.
then I think it is hard to build cube backward along the time in kylin.
maybe someone has some good ideas at this point.
Hi All,
I'm wondering can I build the Kylin cube backward along the time. More
specifically, can I build the cube from the current time to six months ago
and then from six months ago to 12 months ago and go on? In this way, I can
have the latest six months' cube result first.
It's well known that
Yes the "acceptPartial" may cause confusion and we decided to disable it,
will roll out in v1.3.
Kylin will introduce the "approximate" TopN measure in the future release
(maybe v2.1), with which the Top records will be pre-calculated during cube
build; then Kylin can quickly answer instead of get
I was looking at the commits. 10 days back, 2 files (QueryReqeust and
SQLRequest.java) were touched that have fixed the issue for clients using
REST API, changing the default acceptPartial to false.
I tried with Zeppelin and it works and results from Hive and Zeppelin (via
REST API) work. However
post in wrong project?
On Sun, Jan 17, 2016 at 2:58 PM, Roy Levin (JIRA) wrote:
> Roy Levin created KYLIN-1326:
>
>
> Summary: Changes to support KMeans with large feature space
> Key: KYLIN-1326
> URL: https://issue
