Hi team,
When I am trying to create a top n measure, I am not able to see the group
by field on UI. I have attached a screenshot of the error for the reference.
-- Srishti Bhargava
wangrupeng created KYLIN-4760:
-
Summary: Optimize TopN
Key: KYLIN-4760
URL: https://issues.apache.org/jira/browse/KYLIN-4760
Project: Kylin
Issue Type: Improvement
Reporter
Zhong Yanghong created KYLIN-4758:
-
Summary: Introduce a new measure to allow input to be negative for
topn
Key: KYLIN-4758
URL: https://issues.apache.org/jira/browse/KYLIN-4758
Project: Kylin
Zhong Yanghong created KYLIN-4707:
-
Summary: Add one config to disable mapper side combiner especially
there's topn measure
Key: KYLIN-4707
URL: https://issues.apache.org/jira/browse/KYLIN
Zhong Yanghong created KYLIN-4651:
-
Summary: TopN does not work when force hit cube enabled
Key: KYLIN-4651
URL: https://issues.apache.org/jira/browse/KYLIN-4651
Project: Kylin
Issue Type
Zhong Yanghong created KYLIN-4650:
-
Summary: Make it possible to support topn measure by only defining
topn without sum
Key: KYLIN-4650
URL: https://issues.apache.org/jira/browse/KYLIN-4650
Project
Guangxu Cheng created KYLIN-4567:
Summary: Improve TopN merge performance in MR engine
Key: KYLIN-4567
URL: https://issues.apache.org/jira/browse/KYLIN-4567
Project: Kylin
Issue Type
wangrupeng created KYLIN-4467:
-
Summary: Support TopN by kylin on Parquet
Key: KYLIN-4467
URL: https://issues.apache.org/jira/browse/KYLIN-4467
Project: Kylin
Issue Type: Improvement
Yifei Wu created KYLIN-4327:
---
Summary: TOPN compator may violates its general contract
Key: KYLIN-4327
URL: https://issues.apache.org/jira/browse/KYLIN-4327
Project: Kylin
Issue Type: Improvement
Marc Wu created KYLIN-4260:
--
Summary: When using server side PreparedStatement cache, the query
result are not match on TopN scenario
Key: KYLIN-4260
URL: https://issues.apache.org/jira/browse/KYLIN-4260
zhao jintao created KYLIN-3961:
--
Summary: Optimize TopN measure merge function to reduce
mistaks
Key: KYLIN-3961
URL: https://issues.apache.org/jira/browse/KYLIN-3961
Project: Kylin
Issue
yangwei created KYLIN-3696:
--
Summary: TOPN度量在同一个模型下2个cube同时开启统计值不准与真实值差得较多
Key: KYLIN-3696
URL: https://issues.apache.org/jira/browse/KYLIN-3696
Project: Kylin
Issue Type: Bug
Components
Shaofeng SHI created KYLIN-3693:
---
Summary: TopN, Count distinct incorrect in Spark engine
Key: KYLIN-3693
URL: https://issues.apache.org/jira/browse/KYLIN-3693
Project: Kylin
Issue Type: Bug
KANG-SEN LU created KYLIN-3636:
--
Summary: in kylin 2.4.1 and 2.5.1 topn aggregation query caused
exception
Key: KYLIN-3636
URL: https://issues.apache.org/jira/browse/KYLIN-3636
Project: Kylin
TopN is a predefinied measure in Apache Kylin, furthermore row_number is
not needed (and isn't recomended because you are in a cube)
"What is the link to the list of functions supported by kylin?" I think you
refer to predefined measures: (Reference:
http://kylin.apache.or
What is the solution for the row_number() function? I need to take the group
TOPN
I am using kylin 2.4.1. What is the link to the list of functions supported by
kylin?
zhengyangju...@163.com
Shaofeng SHI created KYLIN-3472:
---
Summary: TopN merge in Spark engine is slow
Key: KYLIN-3472
URL: https://issues.apache.org/jira/browse/KYLIN-3472
Project: Kylin
Issue Type: Bug
shaofengshi closed pull request #172: KYLIN-3453 Improve cube size estimation
for topn,count distinct
URL: https://github.com/apache/kylin/pull/172
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance
asfgit commented on issue #172: KYLIN-3453 improve cube size estimation for
topn,count distinct
URL: https://github.com/apache/kylin/pull/172#issuecomment-407251898
Can one of the admins verify this patch?
This is an
Wayne1c opened a new pull request #172: KYLIN-3453 improve cube size estimation
for topn,count distinct
URL: https://github.com/apache/kylin/pull/172
This is an automated message from the Apache Git Service.
To respond to
Chao Long created KYLIN-3453:
Summary: Improve cube size estimation for TOPN, COUNT DISTINCT
Key: KYLIN-3453
URL: https://issues.apache.org/jira/browse/KYLIN-3453
Project: Kylin
Issue Type
Yifei Wu created KYLIN-3387:
---
Summary: validate duplicate check after TopN remove dumplicate
meaures automaticaly
Key: KYLIN-3387
URL: https://issues.apache.org/jira/browse/KYLIN-3387
Project: Kylin
Yifei Wu created KYLIN-3386:
---
Summary: the TopN measure validate code refactor to make it more
clear
Key: KYLIN-3386
URL: https://issues.apache.org/jira/browse/KYLIN-3386
Project: Kylin
Issue
liyang created KYLIN-3322:
-
Summary: TopN requires a SUM to work
Key: KYLIN-3322
URL: https://issues.apache.org/jira/browse/KYLIN-3322
Project: Kylin
Issue Type: Bug
Reporter: liyang
Roger Shi created KYLIN-2657:
Summary: 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
Lin Tingmao created KYLIN-2620:
--
Summary: Check for "ORDER BY LIMIT" clause when rewrite SUM query
as TOPN
Key: KYLIN-2620
URL: https://issues.apache.org/jira/browse/KYLIN-2620
Proj
liyang created KYLIN-2617:
-
Summary: SUM when rewritten as TOPN does not give consistent
(correct) result?
Key: KYLIN-2617
URL: https://issues.apache.org/jira/browse/KYLIN-2617
Project: Kylin
Issue
Shaofeng SHI created KYLIN-2543:
---
Summary: Still build dictionary for TopN group by column even
using non-dict encoding
Key: KYLIN-2543
URL: https://issues.apache.org/jira/browse/KYLIN-2543
Project
c") group by city, product_name order by occurancy desc limit 100;
>
> To get a better understanding of TopN, please check
> https://kylin.apache.org/blog/2016/03/19/approximate-topn-measure/
>
> 2017-04-02 22:33 GMT+08:00 ShaoFeng Shi :
>
> > Kylin TopN's "s
The sample SQL missed product_name in group by, it should be:
select city, product_name, sum(1) as occurancy from fact_table where city
in ("abc") group by city, product_name order by occurancy desc limit 100;
To get a better understanding of TopN, please check
https://kylin.apache.org
Kylin TopN's "sum|order by" supports two options a) a numeric column, b)
constant 1.
The option b) can match your requirement in my understanding. You just need
define "product_name" as the "group by" column in TopN, and constant 1 as
the "sum|order b
group by SUM, or group by COUNT is reasonable and supported. There is no
order by name alphabetical support.
2017-03-31 20:16 GMT+08:00 hongbin ma :
> hi,
>
> i believe it's not supported. besides, how do you define "order" on string?
> I don't think it's a reasonable requirement
>
> --
> Regard
hi,
i believe it's not supported. besides, how do you define "order" on string?
I don't think it's a reasonable requirement
--
Regards,
*Bin Mahone | 马洪宾*
Hi,
I am using kylin 1.6 and trying to define a topN measure on string column
(in SUM | ORDER BY field), which is giving me Number format exception. I
understand that kylin is expecting a numeric column to do sum operation on
it. But, I just wanted to ask that is there any way to define topN on
Shaofeng SHI created KYLIN-2248:
---
Summary: TopN merge further optimization after KYLIN-1917
Key: KYLIN-2248
URL: https://issues.apache.org/jira/browse/KYLIN-2248
Project: Kylin
Issue Type
Shaofeng SHI created KYLIN-2244:
---
Summary: "kylin.job.cuboid.size.memhungry.ratio" shouldn't be
applied on measures like TopN
Key: KYLIN-2244
URL: https://issues.apache.org/jira/br
Shaofeng SHI created KYLIN-2243:
---
Summary: TopN memory estimation is inaccurate in some cases
Key: KYLIN-2243
URL: https://issues.apache.org/jira/browse/KYLIN-2243
Project: Kylin
Issue Type
hongbin ma created KYLIN-2152:
-
Summary: TopN group by column does not distinguish between NULL
and ""
Key: KYLIN-2152
URL: https://issues.apache.org/jira/browse/KYLIN-2152
Project: Kylin
Shaofeng SHI created KYLIN-2112:
---
Summary: Allow a column be a dimension as well as "group by"
column in TopN measure
Key: KYLIN-2112
URL: https://issues.apache.org/jira/browse/KYLIN-2112
Shaofeng SHI created KYLIN-2098:
---
Summary: TopN support query UHC column without sorting by sum value
Key: KYLIN-2098
URL: https://issues.apache.org/jira/browse/KYLIN-2098
Project: Kylin
Issue
Shaofeng SHI created KYLIN-2097:
---
Summary: Get 'Column does not exist in row key desc" on cube has
TopN measure
Key: KYLIN-2097
URL: https://issues.apache.org/jira/browse/KYLIN-2097
Proj
Shaofeng SHI created KYLIN-2075:
---
Summary: TopN measure: need select "constant" + "1" as the
SUM|ORDER parameter
Key: KYLIN-2075
URL: https://issues.apache.org/jira/browse/KYLIN-2075
ity.it will be cool if I
> could create a topN measure to cover both PV and UV,but right now topN only
> support ORDER|SUM by Column,so if I create a PV topN measure,then UV is
> resitricted because I could neither create a topN count distinct measure
> nor a normal count distinct in th
I have a cube that I need to compute PV and UV at the same time within each
cuboid which contain ultra high cardinality.it will be cool if I could create a
topN measure to cover both PV and UV,but right now topN only support ORDER|SUM
by Column,so if I create a PV topN measure,then UV is
Kris created KYLIN-2024:
---
Summary: kylin TopN only support the first measure
Key: KYLIN-2024
URL: https://issues.apache.org/jira/browse/KYLIN-2024
Project: Kylin
Issue Type: Bug
Components
hongbin ma created KYLIN-2011:
-
Summary: Query without order by should not leverage topn measure
Key: KYLIN-2011
URL: https://issues.apache.org/jira/browse/KYLIN-2011
Project: Kylin
Issue Type
Zhong Yanghong created KYLIN-1980:
-
Summary: TopN issue: result not consistent with hive
Key: KYLIN-1980
URL: https://issues.apache.org/jira/browse/KYLIN-1980
Project: Kylin
Issue Type: Bug
Shaofeng SHI created KYLIN-1917:
---
Summary: TopN counter merge performance improvement
Key: KYLIN-1917
URL: https://issues.apache.org/jira/browse/KYLIN-1917
Project: Kylin
Issue Type
Shaofeng SHI created KYLIN-1767:
---
Summary: Update UI for TopN: specify encoding and multiple "group
by"
Key: KYLIN-1767
URL: https://issues.apache.org/jira/browse/KYLIN-1767
Proj
The embeded "group by" column of TopN shouldn't be declared as a dimension
in the cube definition; otherwise you wouldn't benefit from this measure;
In v1.5.1 there is no such check when saving the cube; From 1.5.2, kylin
will report error message on such case.
Please ch
{
"name": "SELLER_FORMAT_CNT",
"function": {
"expression": "COUNT_DISTINCT",
"parameter": {
"type": "column",
"value": "LSTG_FORMAT_NAME",
{
"name": "SELLER_FORMAT_CNT",
"function": {
"expression": "COUNT_DISTINCT",
"parameter": {
"type": "column",
"value": "LSTG_FORMAT_NAME",
Copperfield created KYLIN-1755:
--
Summary: TopN Measure IndexOutOfBoundsException
Key: KYLIN-1755
URL: https://issues.apache.org/jira/browse/KYLIN-1755
Project: Kylin
Issue Type: Bug
Shaofeng SHI created KYLIN-1631:
---
Summary: Web UI of TopN, "group by" column only need fact column
Key: KYLIN-1631
URL: https://issues.apache.org/jira/browse/KYLIN-1631
Project: Kylin
Zhong,Jason created KYLIN-1622:
--
Summary: sql not executed and report topN error
Key: KYLIN-1622
URL: https://issues.apache.org/jira/browse/KYLIN-1622
Project: Kylin
Issue Type: Bug
Shaofeng SHI created KYLIN-1551:
---
Summary: Should check and ensure TopN measure has two parameters
specified
Key: KYLIN-1551
URL: https://issues.apache.org/jira/browse/KYLIN-1551
Project: Kylin
Shaofeng SHI created KYLIN-1478:
---
Summary: TopN measure should support non-dictionary encoding for
ultra high cardinality
Key: KYLIN-1478
URL: https://issues.apache.org/jira/browse/KYLIN-1478
Project
Shaofeng SHI created KYLIN-1477:
---
Summary: TopN measure should support ascending order
Key: KYLIN-1477
URL: https://issues.apache.org/jira/browse/KYLIN-1477
Project: Kylin
Issue Type: Wish
Shaofeng SHI created KYLIN-1392:
---
Summary: Support fixedLength encoding for TopN measure
Key: KYLIN-1392
URL: https://issues.apache.org/jira/browse/KYLIN-1392
Project: Kylin
Issue Type: Sub
Shaofeng SHI created KYLIN-1378:
---
Summary: Add UI for TopN measure
Key: KYLIN-1378
URL: https://issues.apache.org/jira/browse/KYLIN-1378
Project: Kylin
Issue Type: Sub-task
also need to support order by desc as well as asc
On Thu, Jan 28, 2016 at 6:30 PM, Shaofeng SHI (JIRA)
wrote:
> Shaofeng SHI created KYLIN-1377:
> ---
>
> Summary: TopN measure should support more expressions
>
Shaofeng SHI created KYLIN-1377:
---
Summary: TopN measure should support more expressions
Key: KYLIN-1377
URL: https://issues.apache.org/jira/browse/KYLIN-1377
Project: Kylin
Issue Type: New
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
liyang created KYLIN-1344:
-
Summary: Bitmap measure defined after TopN measure can cause merge
to fail
Key: KYLIN-1344
URL: https://issues.apache.org/jira/browse/KYLIN-1344
Project: Kylin
Issue
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 quick
.nabble.com/TopN-Results-Differ-in-Hive-and-Kylin-tp3288p3296.html
Sent from the Apache Kylin mailing list archive at Nabble.com.
will "Show All" button provide you with the correct answer?
--
Regards,
*Bin Mahone | 马洪宾*
Apache Kylin: http://kylin.io
Github: https://github.com/binmahone
ceptPartialResults" mode, and you'll get a right result.
Notice "AcceptPartialResults" is only enabled by default at web client,
you'll not meet such problems if you're using JDBC, ODBC or standard REST
API.
--
View this message in context:
http://apache-kylin.74782.
Kylin Web UI
--
View this message in context:
http://apache-kylin.74782.x6.nabble.com/TopN-Results-Differ-in-Hive-and-Kylin-tp3288p3291.html
Sent from the Apache Kylin mailing list archive at Nabble.com.
in which way are you connecting to Kylin, ODBC, JDBC, Rest API or the web
UI?
I'm hitting an issue and am not able to understand clearly what the root
cause is.
I have customer,time dimension and a transaction fact table. Customer table
has 1MM rows and transaction fact 154MM.
I have to find topN customers by transaction volume for a year. I ran the
following que
71 matches
Mail list logo
