Re: [DISCUSS] Adding the generation of sboms to our build?
Cool, CycloneDX is famous. Look forward! --- Xiangdong Huang Christofer Dutz 于2023年7月15日周六 22:59写道： > > Well in PLC4X the plugin generates an XML version of the SBOM. > We’re using this plugin: > https://github.com/CycloneDX/cyclonedx-maven-plugin > > Chris > > Von: Xiangdong Huang > Datum: Samstag, 15. Juli 2023 um 07:58 > An: dev@iotdb.apache.org > Betreff: Re: [DISCUSS] Adding the generation of sboms to our build? > Hi Chris, > > Look forward! SBOM has also received a lot of attention in China. > Which kind of format/standard it will obey? > > Best, > --- > Xiangdong Huang > > Christofer Dutz 于2023年7月14日周五 21:28写道： > > > > Hi all, > > > > here in Europe we’re currently preparing for quite a bit of an earthquake > > caused by the Cyber-Resiliency-Act. In some projects I’m involved in > > (Mainly PLC4X) I’ve started initiating small changes which could make us > > come out without too many problems. > > > > One thing that seems to be coming up in both the EU as well as the US acts, > > are the requirement to publish SBOM information (Software Bill Of > > Material). As we are also using Maven as a build tool, I’ve got a > > configuration in our poms that ensures an Apache release also produces an > > SBOM, that we will be able to deploy. > > > > Are we interested in adding that to the IoTDB build? > > > > Chris
Re: Great job on the restructuring!
welcome to continuously refactor and optimize the project structure :D --- Xiangdong Huang Christofer Dutz 于2023年7月27日周四 22:48写道： > > Hi Folks, > > I sort of missed most of it as git tends to keep the moved directories, if > there’s something in there … as they all contained “target” directories, > I just noticed the cleaned-up structure of the project … awesome work. > > I took the liberty of applying the same structural changes on the reactor (No > worries, in a branch) > There I introduced intermediate sub-parent poms. > Also did I clean up the pom structure, where it needed some cleaning up. > > Now in IntelliJ (and probably every other Maven-Enabled IDE) the project > should also be structured nicely, and the modules have equally formatted > names. > > The changes should not have any real impact on the project and the build. > > In general, I would prefer adjusting the artifact-ids to replicate the module > structure, but this is already a lot better, and I wasn’t sure of the > implications of artifact renaming in upstream builds. > > Chris
Re: [DISCUSS] Refactor the way we're building/using Thrift
Hi Chris, > I would like to move the compile-tools directory into the root of the project > and detach it from the rest of the project (So it’s not called from the build > if we build the project). I quickly check current compile-tool, now it is only used by client-cpp. So is it really necessary to move to the root folder? > This only needs to be run every now and then if something fundamental changes > (Like new OSes or new CPU Architectures). Yes, I also agree to compile tools ourselves, rather than download from somewhere.. (and just run once for each operation system.) > I would like to update that module, so it will not only build an executable, > but also package the includes and the libraries for that OS and Architecture +1. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Christofer Dutz 于2023年7月28日周五 20:42写道： > > Hi, > > So, I've been fighting to simplify our use of Thrift, as there were several > problems with how we do it today on my M2 Mac (Mostly however to an updated > Homebrew, which uses different paths). > > While going through the project, I noticed that everything in "protocol" > downloads a pre-built executable, which is simply downloaded and run this > doesn’t seem to run on Arm64 (new M1 and M2 Macs). > > I would like to move the compile-tools directory into the root of the project > and detach it from the rest of the project (So it’s not called from the build > if we build the project). > > This only needs to be run every now and then if something fundamental changes > (Like new OSes or new CPU Architectures). > I would like to update that module, so it will not only build an executable, > but also package the includes and the libraries for that OS and Architecture, > so we can use that in the client-cpp and the client-cpp-example. > I'd like to give it a try if we could also use this approach for the libs and > completely get rid of the thrift compilation as part of the build. > > What do you think? > > Chris >
[BUILD-STABLE]: Job 'IoTDB/IoTDB-pip-new/master [master] [304]'
BUILD-STABLE: Job 'IoTDB/IoTDB-pip-new/master [master] [304]': Is back to normal.
[DISCUSS] Refactor the way we're building/using Thrift
Hi, So, I've been fighting to simplify our use of Thrift, as there were several problems with how we do it today on my M2 Mac (Mostly however to an updated Homebrew, which uses different paths). While going through the project, I noticed that everything in "protocol" downloads a pre-built executable, which is simply downloaded and run this doesn’t seem to run on Arm64 (new M1 and M2 Macs). I would like to move the compile-tools directory into the root of the project and detach it from the rest of the project (So it’s not called from the build if we build the project). This only needs to be run every now and then if something fundamental changes (Like new OSes or new CPU Architectures). I would like to update that module, so it will not only build an executable, but also package the includes and the libraries for that OS and Architecture, so we can use that in the client-cpp and the client-cpp-example. I'd like to give it a try if we could also use this approach for the libs and completely get rid of the thrift compilation as part of the build. What do you think? Chris
[ANNOUNCE] Apache IoTDB 1.1.2 released
The Apache IoTDB team is pleased to announce the release of Apache IoTDB 1.1.2. Apache IoTDB (Database for Internet of Things) is an IoT native database with high performance for data management and analysis, deployable on the edge and the cloud. Apache IoTDB 1.1.2 is the latest version of the v1 series. Feel free to upgrade from 1.1.1 or earlier version. ## New Feature * [IOTDB-5919]show variables add a variable timestamp_precision * Add Python SessionPool ## Improvement/Bugfix * [IOTDB-5901] Load: load tsfile without data will throw NPE * [IOTDB-5903] Fix cannot select any inner space compaction task when there is only unsequence data * [IOTDB-5878] Allow ratis-client retry when gRPC IO Unavailable * [IOTDB-5939] Correct Flusing Task Timeout Detect Thread * [IOTDB-5905] Fix aligned timeseries data point lost after flushed in some scenario * [IOTDB-5963] Make sure that TsBlock blocked on memory is added in queue before the next TsBlock returned by root operator * [IOTDB-5819] Fix npe when booting net metrics * [IOTDB-6023] Pipe: Fix load tsfile error while handling empty value chunk * [IOTDB-5971] Fix potential QUOTE problem in iotdb reporter * [IOTDB-5993] ConfigNode leader changing causes lacking some DataPartition allocation result in the response of getOrCreateDataPartition method * [IOTDB-5910] Fix compaction scheduler thread pool is not shutdown when aborting compaction * [IOTDB-6056] Pipe: Failed to load tsfile with empty pages (NPE occurs when loading) * [IOTDB-5916]Fix exception when file is deleted during compaction selection * [IOTDB-5896] Fix the NPE issue when taking snapshot in WAL combined with Aligned Binary * [IOTDB-5929] Enable DataPartition inherit policy * [IOTDB-5934] Optimize cluster partition policy * [IOTDB-5926] Remove Useless Rater in Timer * [IOTDB-6030] Improve efficiency of ConfigNode PartitionInfo takeSnapshot * [IOTDB-5997] Improve efficiency of ConfigNode PartitionInfo loadSnapshot * Fix potential deadlock when freeing memory in MemoryPool * Release resource of FI after all drivers have been closed * Set default degree of parallelism back to the num of CPU * Make SequenceStrategy and MaxDiskUsableSpaceFirstStrategy are allowed in cluster mode * Fix npe exception when invalid in metric module * Fix CQ does not take effect in ns time_precision * Fix storage engine memory config initialization * Fix template related schema query * add default charset setting in start-datanode.bat and print default charset when starting * Fix TsfileResource error after delete device in sequence working memtable * load TsFile bugs: Not checking whether the tsfile data loaded locally is in the same time partition during the loading process & LoadTsFilePieceNode error when loading tsfile with empty value chunks * Fix alias query failure after restarting DataNode The full release note is available at: https://dlcdn.apache.org/iotdb/1.1.2/RELEASE_NOTES.md The release is available for download at: http://iotdb.apache.org/Download Maven artifacts for JDBC driver, session SDK, TsFile SDK, Spark-connector, Hadoop-connector, Hive-connector and Flink-connector can be found at: https://search.maven.org/search?q=3Dg:org.apache.iotdb Regards, The Apache IoTDB team
如何设置10720和10750端口的监听地址
您好！ 目前10720和10750两个端口的监听地址是全IP范围，如何设置监听指定的IP地址？ [root@localhost iotdb-cluster]# netstat -nltp|grep -E '10667|10710|10720|10730|10740|10750|10760' tcp6 0 0 :::10750:::*LISTEN 10015/java tcp6 0 0 :::10720:::*LISTEN 7607/java tcp6 0 0 192.168.1.1:10760 :::*LISTEN 10015/java tcp6 0 0 192.168.1.1:10730 :::*LISTEN 10015/java tcp6 0 0 192.168.1.1:10667 :::*LISTEN 10015/java tcp6 0 0 192.168.1.1:10740 :::*LISTEN 10015/java tcp6 0 0 192.168.1.1:10710 :::*LISTEN 7607/java
