AW: Refactor the package structure of IoTDB
LOL … well …. Then I still agree ;-) But I am sure that starting Monday I’ll be doing a hell of a lot more work on and with IoTDB … looking forward to it ;-) Chris Von: Jialin Qiao Datum: Freitag, 30. Juni 2023 um 17:00 An: dev@iotdb.apache.org Betreff: Re: Refactor the package structure of IoTDB Hi Chris, This change originated from your advice in Slack :) Thanks, ― Jialin Qiao Apache IoTDB PMC Christofer Dutz 于2023年6月30日周五 16:07写道： > > Hi Gaofei, > > I totally agree and support changing the package structure, as it was > something I stumbled over some time ago when I was trying to integrate IoTDB > into something. > > Chris > > > > Von: Gaofei Cao > Datum: Dienstag, 27. Juni 2023 um 15:19 > An: dev@iotdb.apache.org > Betreff: Refactor the package structure of IoTDB > Hi All, > > To make the the package structure of IoTDB more concise and tidy, we > have moved the package `antlr`, `confignode`, `consensus`, `metrics`, > `mlnode`, 'node-commons' and `server` to a new package `iotdb-core`. > > The package structure before changed: > Parent > ├──antrl > ├──confignode > ├──consensus > ├──iotdb-api > ├──iotdb-client > ├──iotdb-connector > ├──iotdb-protocol > ├──library-udf > ├──metrics > ├──mlnode > ├──node-commons > ├──server > ├──tsfile > > > The package structure after changed (master branch): > Parent > ├── iotdb-api > ├── iotdb-client > ├── iotdb-connector > ├── iotdb-core > └── antlr > └── confignode > └── consensus > └── datanode (sever package before changed) > └── metrics > └── mlnode > └── node-commons > └── tsfile > ├── iotdb-protocol > ├── library-udf > > > Thanks. > > Gaofei Cao > Apache IoTDB PMC
Re: Refactor the package structure of IoTDB
Hi Chris, This change originated from your advice in Slack :) Thanks, — Jialin Qiao Apache IoTDB PMC Christofer Dutz 于2023年6月30日周五 16:07写道： > > Hi Gaofei, > > I totally agree and support changing the package structure, as it was > something I stumbled over some time ago when I was trying to integrate IoTDB > into something. > > Chris > > > > Von: Gaofei Cao > Datum: Dienstag, 27. Juni 2023 um 15:19 > An: dev@iotdb.apache.org > Betreff: Refactor the package structure of IoTDB > Hi All, > > To make the the package structure of IoTDB more concise and tidy, we > have moved the package `antlr`, `confignode`, `consensus`, `metrics`, > `mlnode`, 'node-commons' and `server` to a new package `iotdb-core`. > > The package structure before changed: > Parent > ├──antrl > ├──confignode > ├──consensus > ├──iotdb-api > ├──iotdb-client > ├──iotdb-connector > ├──iotdb-protocol > ├──library-udf > ├──metrics > ├──mlnode > ├──node-commons > ├──server > ├──tsfile > > > The package structure after changed (master branch): > Parent > ├── iotdb-api > ├── iotdb-client > ├── iotdb-connector > ├── iotdb-core > └── antlr > └── confignode > └── consensus > └── datanode (sever package before changed) > └── metrics > └── mlnode > └── node-commons > └── tsfile > ├── iotdb-protocol > ├── library-udf > > > Thanks. > > Gaofei Cao > Apache IoTDB PMC
AW: [discuss] move jenkins build message to a new mailing list
Hi, well … I would like to bring the idea of making the build more solid, that there are less failures? It did seem as if there are some flaky tests. Not quite sure, but I think having build failures on “develop” on the list is good. Build failures of non-develop branches however not. We’re currently working hard in PLC4X in fixing issues failing the build regularly/randomly. If we move them somewhere else, we’re running danger to simply no longer pay attention to the build failing. Chris Von: Jialin Qiao Datum: Freitag, 30. Juni 2023 um 11:33 An: dev@iotdb.apache.org Betreff: Re: [discuss] move jenkins build message to a new mailing list +1 for option 1 Thanks, ― Jialin Qiao Apache IoTDB PMC Haonan Hou 于2023年6月30日周五 17:31写道： > > +1 for option 1. > > Best, > Haonan Hou > > > On Jun 29, 2023, at 11:44 PM, Xiangdong Huang wrote: > > > > Hi all, > > > > How do you think about move jenkins's notification > > "build-failure"/"build-stable" to a new mailing list? > > > > Now, it is sent to dev@, and some people may think it is annoying.. > > > > So, how do you think about it? > > > > option 1: move to an existed mailing list: notifications@ (which is > > for jira issues now) > > option 2: create a new mailing list. > > option 3: keep current status > > > > Best, > > --- > > Xiangdong Huang >
Re: [discuss] move jenkins build message to a new mailing list
+1 for option 1 Thanks, — Jialin Qiao Apache IoTDB PMC Haonan Hou 于2023年6月30日周五 17:31写道： > > +1 for option 1. > > Best, > Haonan Hou > > > On Jun 29, 2023, at 11:44 PM, Xiangdong Huang wrote: > > > > Hi all, > > > > How do you think about move jenkins's notification > > "build-failure"/"build-stable" to a new mailing list? > > > > Now, it is sent to dev@, and some people may think it is annoying.. > > > > So, how do you think about it? > > > > option 1: move to an existed mailing list: notifications@ (which is > > for jira issues now) > > option 2: create a new mailing list. > > option 3: keep current status > > > > Best, > > --- > > Xiangdong Huang >
Re: [discuss] move jenkins build message to a new mailing list
+1 for option 1. Best, Haonan Hou > On Jun 29, 2023, at 11:44 PM, Xiangdong Huang wrote: > > Hi all, > > How do you think about move jenkins's notification > "build-failure"/"build-stable" to a new mailing list? > > Now, it is sent to dev@, and some people may think it is annoying.. > > So, how do you think about it? > > option 1: move to an existed mailing list: notifications@ (which is > for jira issues now) > option 2: create a new mailing list. > option 3: keep current status > > Best, > --- > Xiangdong Huang
AW: Refactor the package structure of IoTDB
Hi Gaofei, I totally agree and support changing the package structure, as it was something I stumbled over some time ago when I was trying to integrate IoTDB into something. Chris Von: Gaofei Cao Datum: Dienstag, 27. Juni 2023 um 15:19 An: dev@iotdb.apache.org Betreff: Refactor the package structure of IoTDB Hi All, To make the the package structure of IoTDB more concise and tidy, we have moved the package `antlr`, `confignode`, `consensus`, `metrics`, `mlnode`, 'node-commons' and `server` to a new package `iotdb-core`. The package structure before changed: Parent ├──antrl ├──confignode ├──consensus ├──iotdb-api ├──iotdb-client ├──iotdb-connector ├──iotdb-protocol ├──library-udf ├──metrics ├──mlnode ├──node-commons ├──server ├──tsfile The package structure after changed (master branch): Parent ├── iotdb-api ├── iotdb-client ├── iotdb-connector ├── iotdb-core └── antlr └── confignode └── consensus └── datanode (sever package before changed) └── metrics └── mlnode └── node-commons └── tsfile ├── iotdb-protocol ├── library-udf Thanks. Gaofei Cao Apache IoTDB PMC
