Hi,
+1 for the rpcPort and CLI timezone. I create two issues [1] [2] and mark as easy-fixed. As for the source build, do you mean that we need to mark the generated code as a source folder? [1] https://issues.apache.org/jira/browse/IOTDB-871 [2] https://issues.apache.org/jira/browse/IOTDB-872 Thanks, ————————————————— Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院 Christofer Dutz <christofer.d...@c-ware.de> 于2020年9月6日周日 下午11:53写道： > HI Xiangdong, > > it seems however that for SNAPSHOTs we're not generating and deploying > these source jars. > > Also I encountered another thing: > It seems that when using the CLI this is fixed to a timezone, which seems > to be +08:00 (Guess somewhere in China). > It would however be good, if the local systems timezone was used instead. > I had to edit the default properties and recompile IoTDB in order to access > IoTDB using the CLI with a different timezone. > > Chris > > > > Am 06.09.20, 17:00 schrieb "Xiangdong Huang" <saint...@gmail.com>: > > Hi Chris, > > Thanks for trying IoTDB as a user role. :D > > > so how about we rename that parameter to “rpcPort”? > > Totally agree. > > > so in IntelliJ I couldn’t easily debug as it was using its > auto-decompiled sources > > I do not get your issue.. If you claim iotdb jars in your project's pom > file, then in IDEAJ, I think it can download the source code of the > jars > automatically and then it will be easy to debug. > > > Wanted to use IntelliJs JDBC panel to see what my service is writing > in > the beginning I got errors that the remote was hanging up and on the > server > side I could read that some thrift-frame-size stuff was wrong. > > Which version of the iotdb and jdbc? I think from 0.9.x on, we are > trying > to add version detection.. (though we have not implement it very well) > > Best, > ----------------------------------- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > Christofer Dutz <christofer.d...@c-ware.de> 于2020年9月6日周日 下午6:35写道： > > > Hi all, > > > > even if I‘ve been a Mentor of the project and helped quite a bit > with the > > build etc … unfortunately I’m currently doing my first steps > actually using > > it. > > > > I noticed a few things that could make things easier for folks like > me. > > > > Here goes: > > > > > > * In “Session” the constructor takes the arguments host and port > … > > while the “host” is sort of pretty self-explanatory, for me the > “port” > > wasn’t quite. The problem is that IoTDB does open quite a number of > ports, > > however from just “port” I couldn’t see which type it’s actually > looking > > for. In the end I found out that it’s looking for the rpc port > (which makes > > sense) … so how about we rename that parameter to “rpcPort”? > > * The build builds and deploys jars for the code, but not the > sources, > > so in IntelliJ I couldn’t easily debug as it was using its > auto-decompiled > > sources, which don’t really align perfectly and which don’t contain > any > > comments. > > * When using the JDBC driver to connect (Wanted to use IntelliJs > JDBC > > panel to see what my service is writing in the beginning I got > errors that > > the remote was hanging up and on the server side I could read that > some > > thrift-frame-size stuff was wrong. In the end I was using the last > released > > version of the driver, but using the SNAPSHOT version of IoTDB. I > think it > > would be good to have some means to check the versions for > compatibility > > first as not everyone will be able to continue on his own when > seeing this > > sort of behavior. > > > > Ok … so far the stuff I noticed and didn’t want to forget. With the > > deployment of sources, I could probably help. > > > > > > Chris > > > > > >
