Sure, why not. Let me post a question.
On Fri, Dec 11, 2015 at 10:09 AM, hongbin ma wrote:
> shall we drop by the Cassandra community and ask them if they have a plan
> to support coprocessor-like feature? this is quite normal requirement, and
> should not be too difficult for them, HBase was n
I can see the need from user perspective. Let me look again at the query
parsing logic and see if any tweak is possible.
On Fri, Dec 11, 2015 at 7:59 AM, Luke Han wrote:
> It should transparent to users, they should always use "count(distinct
> seller_id)"
>
> How about one setting value when us
Hi chunen
It's great if you could open source your related work! I'm not sure how you
guys implemented your kylin-tools (which sounds very functional), however I
may provide some "rules" that I think our client library should follow:
1. No direct access to metadata store. Client library should on
Cube size will affect how to split region when creating htable, smaller
cube size will cause more region with regard to the same source dara.
2015-12-10 16:51 GMT+08:00 Li Yang :
> Em.. do need more document.
>
> The "Cube Size" under the advanced setting affects the MR job
> configuration. Unde
Shaofeng SHI created KYLIN-1221:
---
Summary: Allow user to kill Hadoop job in the job list page
Key: KYLIN-1221
URL: https://issues.apache.org/jira/browse/KYLIN-1221
Project: Kylin
Issue Type: Wi
cheers!
On Thu, Dec 10, 2015 at 5:21 PM, Hao Chen wrote:
> Congrats, Apache™ Kylin™
>
> --
>
> Hao
>
>
> On Thu, Dec 10, 2015 at 4:09 PM, Li Yang wrote:
>
> > Cheers!
> >
> > On Wed, Dec 9, 2015 at 12:13 PM, Xiaoyu Wang wrote:
> >
> >> Congratulations!
> >>
> >>
> >> 在 2015年12月09日 11:22, Abh
shall we drop by the Cassandra community and ask them if they have a plan
to support coprocessor-like feature? this is quite normal requirement, and
should not be too difficult for them, HBase was not born with coprocessor,
I believe.
On Thu, Dec 10, 2015 at 5:54 PM, Li Yang wrote:
> Not for th
It should transparent to users, they should always use "count(distinct
seller_id)"
How about one setting value when user pickup "DistinctCount"? We already
have error range, it should be easy to have one more option say "Precise"
(but yes, also have to display warn message about the disadvantage f
You’re right, I ignored that can’t get return type from query context.
I’m not familiar with Calcite UDF, do you mean a new sql writing like “count
(distinct_precise seller_id)”? That’s not transparent for user, seems not the
best way.
Another way is still mapping count distinct query to one ag
wangxianbin created KYLIN-1220:
--
Summary: JsonMappingException: Can not deserialize instance of
java.lang.String out of START_ARRAY
Key: KYLIN-1220
URL: https://issues.apache.org/jira/browse/KYLIN-1220
P
I've considered exactly the same point. It does not work when mapping a
query to the aggregation functions. A query will simply say "count
(distinct seller_id)", and won't mention any return type.
The way out is adding a new aggregation for your count distinct using
Calcite UDF, then it can be cor
Not for the core team at least. Cassandra lacks of a CoProcessor equivalent
(the last time I checked).
However it is highly welcome if some one want to do a Proof of Concept in
this direction. Not limited to Cassandra, consider Kudu and other K-V store
options. If a PoC shows another storage can b
What Marek described is as designed (an early design though, and we can
discuss if the design makes sense).
Out of simplicity, Kylin 1.x requires all segment be continuous and there's
no gap in between. So a new incremental segment always starts from where
the last segment ends. I agree the Rest
Congrats, Apache™ Kylin™
--
Hao
On Thu, Dec 10, 2015 at 4:09 PM, Li Yang wrote:
> Cheers!
>
> On Wed, Dec 9, 2015 at 12:13 PM, Xiaoyu Wang wrote:
>
>> Congratulations!
>>
>>
>> 在 2015年12月09日 11:22, Abhilash L L 写道:
>>
>>> Congrats!
>>>
>>> Regards,
>>> Abhilash
>>>
>>> On Wed, Dec 9, 2015 at
Welcome Xianbin~
On Tue, Dec 8, 2015 at 3:25 PM, whenwin wrote:
> hi all!
>
> thank for the warm welcome, and help from hongbin, xiaoyu, luke.
>
> big smile on face!
>
> regards
>
> --
> View this message in context:
> http://apache-kylin.74782.x6.nabble.com/Xianbin-volunteers-to-work-on-KYLIN-1
Em.. do need more document.
The "Cube Size" under the advanced setting affects the MR job
configuration. Under KYLIN_HOME/conf, you can have optional job_conf xml
for particular size of cube.
-rw-r--r-- 1 b_kylin hdmi-technology 2564 Dec 7 00:45 kylin_hive_conf.xml
-rw-r--r-- 1 b_kylin hdmi-te
It’s really great job, Yang!
I have a question about the MeasureTypeFactory. In the current 2.x-stating
code, two built-in measure types (hll and topn) were registered, and the
factory create the corresponding MeasureType only by funcName (‘COUNT_DISTINCT’
for hll and ‘TOP_N’ for topn).
Howeve
Cheers!
On Wed, Dec 9, 2015 at 12:13 PM, Xiaoyu Wang wrote:
> Congratulations!
>
>
> 在 2015年12月09日 11:22, Abhilash L L 写道:
>
>> Congrats!
>>
>> Regards,
>> Abhilash
>>
>> On Wed, Dec 9, 2015 at 6:51 AM, 王猛 wrote:
>>
>> Great ！
>>>
>>> 2015-12-08 22:25 GMT+08:00 Luke Han :
>>>
>>> Hi community,
Which version of Kylin are you on? I cannot reproduce this on 2.x branch.
On Wed, Dec 9, 2015 at 4:29 PM, DroopyHoo wrote:
> Equal or more than 2 elements in NOT IN clause is also a bug in calcite ...
> https://issues.apache.org/jira/browse/CALCITE-980
> ..
>
>
> 在 15/12/9 下午4:09, Wang Hua(大数据中
19 matches
Mail list logo
