[jira] [Commented] (IOTDB-1591) release-0.12.2 RC1 cluster : Execute CREATE FUNCTION on 1 node, this FUNCTION is invisible to other nodes
[
https://issues.apache.org/jira/browse/IOTDB-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17405526#comment-17405526
]
刘珍 commented on IOTDB-1591:
---
This is not a bug.
It's need to copy ${UDF}.jar to all nodes .(ext/udf)
> release-0.12.2 RC1 cluster : Execute CREATE FUNCTION on 1 node, this
> FUNCTION is invisible to other nodes
> --
>
> Key: IOTDB-1591
> URL: https://issues.apache.org/jira/browse/IOTDB-1591
> Project: Apache IoTDB
> Issue Type: Bug
>Affects Versions: 0.12.2
>Reporter: 刘珍
>Priority: Minor
> Attachments: image-2021-08-26-13-51-54-754.png,
> udf-example-0.12.2-SNAPSHOT.jar
>
>
> iotdb info:
> release 0.12.2 RC1
> cluster :
> ip5/ip10/ip13
> default_replica_num=1
> ip13 :
> cp udf-example-0.12.2-SNAPSHOT.jar${release_1202_dir}/ext/udf/
> ip13 cli ：
> CREATE FUNCTION example AS "org.apache.iotdb.udf.UDTFExample"
> SHOW FUNCTIONS;
> !image-2021-08-26-13-51-54-754.png!
> ip5/ip10 cli:
> SHOW FUNCTIONS;
>
> FUNCTION example is invisible .
> ./sbin/start-cli.sh -h 192.168.130.10 -p 6688 -e "SELECT s1,
> example(s1), s2, example(s2) FROM root.sg1.d1;"
> Msg: 411: Error occurred in query process: Failed to reflect UDF instance,
> because UDF EXAMPLE {color:#DE350B}*has not been registered.*{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1594) Show timeseries returns incorrect tag value
Haonan Hou created IOTDB-1594: - Summary: Show timeseries returns incorrect tag value Key: IOTDB-1594 URL: https://issues.apache.org/jira/browse/IOTDB-1594 Project: Apache IoTDB Issue Type: Bug Components: Core/Schema Manager Reporter: Haonan Hou Attachments: 2851629947501_.pic_hd.jpg !2851629947501_.pic_hd.jpg! -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IOTDB-1367) [Distributed] Runtime exception is not properly handled during forwarding
[
https://issues.apache.org/jira/browse/IOTDB-1367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17405017#comment-17405017
]
Jianyun Cheng commented on IOTDB-1367:
--
I think the issue has been fixed. Right now, client could get the right
response. But it's strange that it doesn't promote the error message but with
empty query result when the client connect to leader directly.
{code:java}
Msg: 500: [INTERNAL_SERVER_ERROR] Exception occurred while executing "select
avg(s6) from root.sg1.d1". Boolean statistics does not support: avg
{code}
> [Distributed] Runtime exception is not properly handled during forwarding
> -
>
> Key: IOTDB-1367
> URL: https://issues.apache.org/jira/browse/IOTDB-1367
> Project: Apache IoTDB
> Issue Type: Bug
> Components: Core/Cluster
>Reporter: Tian Jiang
>Priority: Major
> Labels: client-me, distributed, query
> Attachments: image-2021-05-07-20-14-47-670.png
>
>
> When I executed `select avg(s_0) from root.group_0.d_20` (notice that s_0 is
> boolean and does not support avg), I got `Msg: 313: Request "Query aggregate:
> root.group_0.d_20.s_0 in [Node(internalIp:192.168.130.4, metaPort:9003,
> nodeIdentifier:1436654207, dataPort:40003, clientPort:6667,
> clientIp:0.0.0.0)]" timeout`. While the log on node 192.168.130.4 says:
> !image-2021-05-07-20-14-47-670.png|thumbnail!
> The cause is that RunTimeExceptions are not caught explicitly in
> DataClusterServer and MetaClusterServer, so they are converted to TExceptions
> by Thrift and are recognized as network problems by the coordinator.
> The solution is either to catch runtime exceptions explicitly and create
> status codes for them or make the coordinator capable of resolving more
> TExceptions. Both ways have their difficulties, for the first one, it is
> nearly impossible to know how many runtime exceptions can occur; for the
> second one, when an exception is converted to a TException, only its message
> remains, so it is not easy to determine what exactly the problem is.
> ps: this only occurs when the coordinator does not have the corresponding
> data, so try querying another node if you can not repeat it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IOTDB-1593) generated files in client-py have unapproved license
Jialin Qiao created IOTDB-1593: -- Summary: generated files in client-py have unapproved license Key: IOTDB-1593 URL: https://issues.apache.org/jira/browse/IOTDB-1593 Project: Apache IoTDB Issue Type: Bug Affects Versions: 0.12.2-SNAPSHOT Reporter: Jialin Qiao When mvn clean package, I got: [*WARNING*] Files with unapproved licenses: /Users/qiaojialin/Desktop/apache-iotdb-0.12.2/client-py/iotdb/thrift/__init__.py /Users/qiaojialin/Desktop/apache-iotdb-0.12.2/client-py/iotdb/thrift/rpc/__init__.py [*ERROR*] Failed to execute goal org.apache.rat:apache-rat-plugin:0.13:check *(license-check)* on project iotdb-python-api: *Too many files with unapproved license: 2 See RAT report in: /Users/qiaojialin/Desktop/apache-iotdb-0.12.2/client-py/target/rat.txt* -> *[Help 1]* -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IOTDB-1592) SLimit Not effective in align by device
ijihang created IOTDB-1592: -- Summary: SLimit Not effective in align by device Key: IOTDB-1592 URL: https://issues.apache.org/jira/browse/IOTDB-1592 Project: Apache IoTDB Issue Type: Bug Reporter: ijihang Fix For: master branch Attachments: image-2021-08-26-14-46-20-810.png !image-2021-08-26-14-46-20-810.png! -- This message was sent by Atlassian Jira (v8.3.4#803005)
