[jira] [Created] (IOTDB-140) TsFile write interface does not support string with Unicode characters

Zihan Meng created IOTDB-140: Summary: TsFile write interface does not support string with Unicode characters Key: IOTDB-140 URL: https://issues.apache.org/jira/browse/IOTDB-140 Project: Apache IoTDB

About documents updating

Hi, As is mentioned in Development instructions [1], whenever updating User Guide documents structure, it is important to modify "0-Content.md" in the same time. Otherwise, it will result in official website linking 404 error. In PR #251 [2], I modified file "0-Content.md" according to recent

Re: Binary Release of IoTDB

Hi, I would prefer structure 2 and I really like it. And we should add a readme.txt with short usage instructions. Julian Am 16.07.19, 13:58 schrieb "Xiangdong Huang" : Hi, I think the structure of the binaries can be: (Structure 1): . ├── LICENSE ├── NOTICE

[jira] [Closed] (IOTDB-46) Can not find overflow file

[ https://issues.apache.org/jira/browse/IOTDB-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] XuYi closed IOTDB-46. - Resolution: Fixed > Can not find overflow file > -- > > Key: IOTDB-46 >

Re: Binary Release of IoTDB

Look forward to others opinion.. By the way, I find that iotdb-grafana-connector.war is sooo large (19MB). Maybe we should not put it into iotdb's binary files... And, there are some libs that should be in the test lifecycle (e.g. powermock* and mockito*...). Best.

Re: Binary Release of IoTDB

If you guys clearly define how the distribution should look like, I'll whip up the assembly descriptor in no time. Chris Holen Sie sichOutlook für Android From: Xiangdong Huang Sent: Tuesday, July 16, 2019 1:57:52 PM To:

Re: Volunteer as Release Manager for release 0.8

Hi, I have updated the RELEASE_NOTES and submit a PR to rel/0.8: https://github.com/apache/incubator-iotdb/pull/250/files Best, -- Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院 > -原始邮件- > 发件人: "Julian Feinauer" > 发送时间: 2019-07-16 16:17:58 (星期二) > 收件人:

Re: Binary Release of IoTDB

Hi, I think the structure of the binaries can be: (Structure 1): . ├── LICENSE ├── NOTICE ├── bin │ ├── export-csv.bat │ ├── export-csv.sh │ ├── import-csv.bat │ ├── import-csv.sh │ ├── run-client.bat │ ├── start-WalChecker.bat │ ├── start-WalChecker.sh │ ├── start-client.bat │

[jira] [Closed] (IOTDB-105) IoTDB lock bug

[ https://issues.apache.org/jira/browse/IOTDB-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] EJTTianyu closed IOTDB-105. --- Resolution: Fixed > IoTDB lock bug > -- > > Key: IOTDB-105 > URL:

AW: Binary Release of IoTDB

No objections Chris, if you give some help we will manage it and I agree that's the technically superior solution. J Von meinem Mobiltelefon gesendet Ursprüngliche Nachricht Betreff: Re: Binary Release of IoTDB Von: Christofer Dutz An: dev@iotdb.apache.org Cc: Bash scripts

[jira] [Closed] (IOTDB-107) WAL log node is missing after recovery.

[ https://issues.apache.org/jira/browse/IOTDB-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tian Jiang closed IOTDB-107. > WAL log node is missing after recovery. > --- > > Key:

Re: Binary Release of IoTDB

Bash scripts are not portable. I would strongly advise not to use them and with the assembly plugin, the binary stuff gets packaged alongside the source bundle during the release build. Chris Holen Sie sichOutlook für Android From: Julian

AW: Binary Release of IoTDB

Hey Chris, I also thought about that and... Contacting you :P But I thought about a bash script :) Julian Von meinem Mobiltelefon gesendet Ursprüngliche Nachricht Betreff: Re: Binary Release of IoTDB Von: Christofer Dutz An: dev@iotdb.apache.org Cc: We could whip up a maven

Re: Binary Release of IoTDB

We could whip up a maven assembly für building that binary distribution. I could help with that, if you exactly define how it should look. Chris Holen Sie sichOutlook für Android From: Kevin A. McGrail Sent: Tuesday, July 16, 2019

Re: Binary Release of IoTDB

+1 to a binary release along side a source release as a convenience. On Tue, Jul 16, 2019, 05:40 Justin Mclean wrote: > Hi, > > Apache releases source code not binaries, but you make can also release a > convenance binary along side a source release as noted in the link Julian > provided. Note

Re: Binary Release of IoTDB

Hi, Apache releases source code not binaries, but you make can also release a convenance binary along side a source release as noted in the link Julian provided. Note that the LICENSE and NOTICE requirements may be diffract as a binary contents may differ. Thanks, Justin

Re: Volunteer as Release Manager for release 0.8

Hi, > But I'm unsure if we have to write everything as "change" because this is the > "first" release with regards to the ASF so I'm unsure if we would point to > 0.7 as "previous" release. > > @cdutz, @jmclean what is your point on that, how do other podlings handle > that? Some podlings

Cherry-picking without PR

Hi, as I'm working through the rel/0.8 branch I observed Tests that failed for me. This is due to minor issues with the Locale. I changed it already in the rel branch but is everybody okay to cherry-pick this to master directly or do you prefer a PR for everything? In other projects we handle

Re: Volunteer as Release Manager for release 0.8

Hi Jialin, of course it is. Adding Jira is just a service to point readers (or people who did a jira) directly to the issue and detailed description. But if you look at early PLC4X releases, we basically had non issues at all __ Julian Am 16.07.19, 10:16 schrieb "Jialin Qiao" : Hi

Re: Volunteer as Release Manager for release 0.8

Hi Julian, I will submit the PR about updating RELEASE_NOTES to rel/0.8. Just one question, some PRs are not associated with Jira issues, is "listing them in the bottom of the corresponding list without a Jira number" ok? for example: Bug Fixes - IOTDB-7 OpenFileNumUtilTest

Please follow the correct code style when submitting PRs

Hi, IoTDB follows Google Code Style (see the checkstyle.xml file at the root path of the project). I find some PRs does not follow that. For new committers, you can use your IDE to help you format the codes before submitting PRs. Best, --- Xiangdong Huang School

Re: Volunteer as Release Manager for release 0.8

Hi all, so I created a release branch now called rel/0.8, see [1]. Master branch is now set to the new development version 0.9.0-SNAPSHOT. This means, that all PRs should be rebased (which should be no problem in 99% of cases). So all changes we do regarding the release should go into rel/0.8.

Re: Volunteer as Release Manager for release 0.8

Yes, I can spin up a release branch now and then everybody who does things for "release stabilization" should work there or point the PRs to there (like updating release notes and stuff). Am 16.07.19, 09:32 schrieb "Xiangdong Huang" : Hi, So, do we need to confirm the source

Re: Volunteer as Release Manager for release 0.8

Hi, So, do we need to confirm the source codes and create a release branch now? Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Julian Feinauer 于2019年7月16日周二 下午12:54写道： > Hey Jialin, > > that is a very kind offer! > Some time

Re: Binary Release of IoTDB

Hi, +1. Binary package is useful to attack users.. Out of the box should be a target of IoTDB. As IoTDB has some modules, like Hadoop adaptor, Spark adaptor, and Grafana-IoTDB connector, I think we also need to discuss whether do we need to include them all in the binary version. For my