[jira] [Created] (KYLIN-3643) Derived column from windowSpec not working in where
May Zhou created KYLIN-3643: --- Summary: Derived column from windowSpec not working in where Key: KYLIN-3643 URL: https://issues.apache.org/jira/browse/KYLIN-3643 Project: Kylin Issue Type: Bug Environment: Kylin 2.5.0 Reporter: May Zhou Derived column from windowSpec not working in where with error message of > -1 while executing SQL: "SELECT * FROM ( SELECT ROW_NUMBER() OVER ( PARTITION BY BUYER_ID,SELLER_ID ORDER BY PRICE ) AS ROW_NUM ,TRANS_ID ,BUYER_ID ,PRICE ,SELLER_ID ,PART_DT FROM KYLIN_SALES ) T WHERE T.ROW_NUM =1 LIMIT 5" taking kylin sample dataset as an example, ``` SELECT ROW_NUMBER() OVER ( PARTITION BY BUYER_ID,SELLER_ID ORDER BY PRICE ) AS ROW_NUM ,TRANS_ID ,BUYER_ID ,PRICE ,SELLER_ID ,PART_DT FROM KYLIN_SALES ``` works good. But ``` SELECT * FROM ( SELECT ROW_NUMBER() OVER ( PARTITION BY BUYER_ID,SELLER_ID ORDER BY PRICE ) AS ROW_NUM ,TRANS_ID ,BUYER_ID ,PRICE ,SELLER_ID ,PART_DT FROM KYLIN_SALES ) T WHERE T.ROW_NUM =1 ``` throws error messages -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3697) check port availability when starts kylin instance
May Zhou created KYLIN-3697: --- Summary: check port availability when starts kylin instance Key: KYLIN-3697 URL: https://issues.apache.org/jira/browse/KYLIN-3697 Project: Kylin Issue Type: Bug Affects Versions: v2.5.1 Reporter: May Zhou As I ran the script and it turned out with no error message, and I ran the kylin.sh start script, the console output indicated that a kylin instance had successfully started, but when I visit the :/kylin, I found another service was running rather than kylin. I can only find the error message in the kylin.out, which is not so user-friendly. > Caused by: java.net.BindException: Address already in use (Bind failed) at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387) at java.net.ServerSocket.bind(ServerSocket.java:375) I am wondering why check-env does not check the availability of port, and the error message could be threw out more user-friendly. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3698) check-env.sh should print more details about checking items
May Zhou created KYLIN-3698: --- Summary: check-env.sh should print more details about checking items Key: KYLIN-3698 URL: https://issues.apache.org/jira/browse/KYLIN-3698 Project: Kylin Issue Type: Improvement Affects Versions: v2.5.1 Reporter: May Zhou In the current version, when users run _check-env.sh_, if there's no error message, it means everything is OK. >From my perspective, adding more details about the checking items when >executing check-env.sh is better. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
