答复: Totally outdated Spottless version?

According to the latest report, Java 8 still has the highest developer share, although the 17+11 share is not significantly different. But what we need to ensure for the upgrade is that all code can still be compiled and run in Java 8, or consider updating it on Apache/tsfile first https://www.j

AW: Splitting up the repos

Well, as I said … I’ve already done the work of splitting things up (I had waited 5 days for any comments here) If we would now do it differently, I am sure someone would be able to re-do the split based on my work and then simply delete the double examples from the extras repo. So, I would b

Re: Splitting up the repos

Hi, The examples could be classified into two parts (1) Connector example: flink, hadoop, kafka, pulsar, rabiitmq, rocketmq (2) IoTDB native api example: jdbc, mqtt, pipe, rest, schema, session, trigger, udf For (1), we could move into extra repo. For (2) , they should be retained in the IoTDB re

[PR] chore(deps): Bump com.google.guava:guava from 32.1.2-jre to 32.1.3-jre [iotdb-extras]

dependabot[bot] opened a new pull request, #5: URL: https://github.com/apache/iotdb-extras/pull/5 Bumps [com.google.guava:guava](https://github.com/google/guava) from 32.1.2-jre to 32.1.3-jre. Release notes Sourced from https://github.com/google/guava/releases";>com.google.guava:gu

[PR] chore(deps): Bump spring.version from 5.3.33 to 5.3.34 [iotdb-extras]

dependabot[bot] opened a new pull request, #4: URL: https://github.com/apache/iotdb-extras/pull/4 Bumps `spring.version` from 5.3.33 to 5.3.34. Updates `org.springframework:spring-tx` from 5.3.33 to 5.3.34 Release notes Sourced from https://github.com/spring-projects/spring-frame

[PR] chore(deps-dev): Bump org.apache.flink:flink-shaded-zookeeper-3 from 3.8.1-17.0 to 3.8.3-18.0 [iotdb-extras]

dependabot[bot] opened a new pull request, #3: URL: https://github.com/apache/iotdb-extras/pull/3 Bumps org.apache.flink:flink-shaded-zookeeper-3 from 3.8.1-17.0 to 3.8.3-18.0. [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?d

[PR] chore(deps): Bump spark-scala.2.12.version from 3.5.0 to 3.5.1 [iotdb-extras]

dependabot[bot] opened a new pull request, #2: URL: https://github.com/apache/iotdb-extras/pull/2 Bumps `spark-scala.2.12.version` from 3.5.0 to 3.5.1. Updates `org.apache.spark:spark-core_2.12` from 3.5.0 to 3.5.1 Updates `org.apache.spark:spark-common-utils_2.12` from 3.5.0 to 3.5

AW: Splitting up the repos

Hmpf, a little bit sooner reply would have been good … I’m already done with the changes, also with moving all examples and the parts of the distribution bundling the connectors. I do think also moving the examples is a good idea. Usually, examples pull in all sorts of dependencies, which show

答复: Splitting up the repos

+1 for Only iotdb-connector need to be moved 发件人: Jialin Qiao 日期: 星期一, 2024年4月15日 17:20 收件人: dev@iotdb.apache.org 主题: Re: Splitting up the repos Hi, 1. Which Parts: Only iotdb-connector need to be moved, distribution and examples will impact the release and users. 2. How to split up: I prefer

Re: Splitting up the repos

Hi, 1. Which Parts: Only iotdb-connector need to be moved, distribution and examples will impact the release and users. 2. How to split up: I prefer【Simply ignore the history, copy the files to the new repo and delete them from the old】. Jialin Qiao Christofer Dutz 于2024年4月15日周一 16:27写道： > >

[PR] chore(deps): Bump org.springframework:spring-web from 5.3.33 to 6.0.18 [iotdb-extras]

dependabot[bot] opened a new pull request, #1: URL: https://github.com/apache/iotdb-extras/pull/1 Bumps [org.springframework:spring-web](https://github.com/spring-projects/spring-framework) from 5.3.33 to 6.0.18. Release notes Sourced from https://github.com/spring-projects/spring

AW: Splitting up the repos

Hi all, So, I’ve set a tag on the main repository “before-moving-extras” (https://github.com/apache/iotdb/releases/tag/before-moving-extras) Also have I copied the content of the examples and integration modules to the new repo, duplicated the build there and updated the versions to artifacts

Totally outdated Spottless version?

Hi all, while going through the plugins in the new split-up repository, I came across the profile, that disabled spotless on Java 21 and above. It seems this issue was fixed quite some time ago and simply updating to an a lot more recent version of spotless should resolve the issue. I think the

AW: Splitting up the repos

Ok … So, no comment I will simply treat as lazy consensus, therefore I will move forward with tagging the main repo with the latest changes as last revision before the split and reference that in the commit to the new repo. Then I’ll simply copy over the files and delete them from the main repo.