Re: Twitter announce for our Talk at ACEU

2019-10-09 Thread Julian Feinauer
Excellent, Xiangdong. Please ensure that there are multiple PPMCs who are able 
to access the Account (we had lots of issues getting the login for Edgent). 
E.g. by sending the login data to private@... then its archived for PPMCs and 
Mentors only.

Julian

Sent from a mobile device, please excuse typos

Von: Xiangdong Huang 
Gesendet: Wednesday, October 9, 2019 4:59:06 PM
An: dev@iotdb.apache.org 
Cc: Julian Feinauer 
Betreff: Re: Twitter announce for our Talk at ACEU

Well, I registered an Twitter account: @ApacheIotdb

:P

Best,
--
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Kevin A. McGrail mailto:kmcgr...@apache.org>> 
于2019年10月8日周二 下午9:40写道:
Congrats

On 10/8/2019 6:42 AM, Julian Feinauer wrote:
> Hi all,
>
> just wanted to share the official ASF Twitter announce for Xiangdong and my 
> talk about IoTDB at ApacheCon EU
> https://twitter.com/jfeinauer2/status/1181519632349483008
>
> Best
> Julian

--
Kevin A. McGrail
kmcgr...@apache.org

Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171



Twitter announce for our Talk at ACEU

2019-10-08 Thread Julian Feinauer
Hi all,

just wanted to share the official ASF Twitter announce for Xiangdong and my 
talk about IoTDB at ApacheCon EU
https://twitter.com/jfeinauer2/status/1181519632349483008

Best
Julian


Re: How about a summary of what you're all up to?

2019-10-07 Thread Julian Feinauer
Hi,

overall my impression is that its getting better.
Initially it was way calmer here but now there are discussion threads or 
announcements about features from time to time.
So I totally agree with chris but I also think there is already a learning 
curve.

So keep it going guys : )

Julian

Am 06.10.19, 15:22 schrieb "Xiangdong Huang" :

Hi,

+1 for more discussions, rather than just opening issues, working on them
and closing them.

Indeed, there are some discussions for some issues, but we can do more
about that.
If the issue is for a new feature, we can show the main idea about how to
implement it on the mailing list.

I summarize some new features/improvements we have solved or addressed in
September according to the mailing list, and github as following with 3
columns: Feature/imporvement description. status. Is there some discussions?

(The statistics may be not accurate. Some of the issues have been solved
but the status of the issues are not changed. Some discussions are on
github but I do not review the contents of related PRs.)

- Improvement for LRUCache. Not solved. no discussion.
- Reimplementation sync module. not solved. no discussion.
- improving spark-tsfile query for narrow table view. not solved. no
discussion.
- Spark-IoTDB connector. not solved. no discussion.
- maintain hadoop-tsfile module. not solved. no discussion (but the
contributor pointed out his main idea).
- load configuration file on-site. not solved. no discussion.
- connect IoTDB with python or C. not solved. no discussion but there are
some replies for that.
- use hive to  query Tsfile data. solved. no discussion.
- switch Antlr3 to antlr4. Not solved. Some discussions (finally, the
performance using antlr4 is worse?).
- enrich session interfaces (using API rather than SQL to operate data) Not
solved. Some discussions.
- support saving data file into HDFS directly. Solved. Some discussions.
- make the result format of metadata query like "show timeseries"
consistent. solved. no discussion but the contributor keeps updating his
progress on the mailing list.
- Create metadata automatically in the insertion. not solved. Some
discussions.
- A simple tool to visualize logs. not solved. Some discussions.
- A new result set format. not solved. no discussion. Some discussions.
- Add bloom filters to TsFile. not solved. Some discussions.
- support retention policy (remove stale data automatically). not solved.
few discussion.
- Convert Path(String) to ID(Long). not solved. few discussions.
- support connection pool (e.g., Ali druid).  not solved. few discussion.
- TsFile skeleton viewer tool. solved. few discussion.
- support External sort for non-sequential data. solved. some discussions
on github.

After reviewing these "discussions", I find that there are few mails for
discussing the idea of how to implement new features.. which I think is the
same important with why the feature is needed or how to define the feature.

In my personal opinion, in the next 3 month (and then 2019 is over...), I
think there are two important features, distributed version and relational
model view.

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Christofer Dutz  于2019年10月5日周六 下午11:24写道:

> Hi Xiangdong,
>
> well a Maven release usually does exactly 2 commits.
> But it's something I noticed quite often. Two digit number of commits, 1-2
> emails on dev.
> So everyone is working hard on all sorts of stuff, but I see absolutely no
> coordination here.
> Is everything just people open Issues, and then people start working on
> these?
> Usually I would sort of expect some discussions about things.
>
> Chris
>
> Am 05.10.19, 17:12 schrieb "Xiangdong Huang" :
>
> Hi,
>
> if the mails are sent today, I think most of them are because I am
> running
> ‘mvn release:prepare’ and ‘mvn release:rollback’, others are for 
fixing
> issues in RC1. All of them are on the rep/0.8 branch.
>
> Best,
>
> Christofer Dutz 于2019年10月5日 周六下午8:48写道:
>
> > Hi all,
> >
> > Again I noticed my Mail client showed me the usual picture … a 2
> digit
> > number of emails in the commit list, and 1 in the dev list.
> > Would be cool if you could sum up what the team is currently working
> on.
> >
> > Are there any new names on the contributor side? You haven’t voted 
in
> > anyone for quite some time
> >
> > Chris
> >
> --
> ---
> Xiangdong Huang
> School of 

Re: [VOTE] Apache IoTDB 0.8.1 (incubating) RC1

2019-10-04 Thread Julian Feinauer
Hi,

sorry, I am a bit late with my vote.. but then I'll wait for RC2 to vote there.

Once again, thank you Xiandong for being RM and you are already doing an 
excellent Job!

Julian

Am 02.10.19, 17:17 schrieb "Xiangdong Huang" :

Hi all,

The vote of RC1 has lasted more than 72 hours.

There are 2 +1 votes and 1 -1 veto.

Chris, Justin, Lei Rui and Jialin pointed some issues and I will fix them
to release RC2.

As now we are on National Day Holiday and my Mac Mini which has the GPG
private key is in the laboratory...
I will  release RC2 in the evening of Oct 4, or the morning of Oct 5.

By the way, we encourage more PPMCs join the next votes. Thanks!

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Lei Rui  于2019年9月30日周一 下午3:14写道:

> Hi all, my vote is +1 (binding) PPMC Vote.
>
>
>
>
> Thanks to Feinauer, I followed [1] and checked:
>
> 1. download staged artifacts. Check their signature and hashes.
>
> ✔ [RM] verify the reported signature is for an "apache.org" address
> ("gpg: Good signature from ...")
>
> ✔ [RM] verify the reported hashes
>
> I use the tool [2] to automatically finish this step.
>
> 2. extract src bundle
>
> ✔ cd downloaded-iotdb-0.8.1rc1
>
> ✔ unzip 0.8.1/rc1/apache-iotdb-0.8.1-incubating-source-release.zip
>
> ✔ verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in
> the extracted source bundle
>
> ✔ [RM] verify the staged source README, RELEASE_NOTE files correspond to
> those in the extracted source bundle
>
> 3. staged src bundle items: content, can compile & test
>
> ✔ a. cd apache-iotdb-0.8.1-incubating
>
> ✔ b. check the contents of LICENSE, NOTICE, README, RELEASE_NOTES
>
> ❗ c. UNPACK the binary artefact and check the contents of LICENSE-binary
> and NOTICE-binary
>
> ✔ d. build from directions in README with an empty maven local repo
>
> ❗ e. [RM] review target/rat.txt (though the build should fail if RAT
> constraints aren't met)
>
> ❗ f. Search for SNAPSHOT references
>
> ✔ g. ./mvnw install
>
> ✔ h. ./mvnw site:site
>
> Btw, I don't understand the sentence "NOTE: can't do this in a
> source-bundle (only in a repo) " as noted in the step h [1].
>
> Therefore, in my practice, I run ./mvnw install and ./mvnw
> site:site under the extracted src bundle got from the previous step "unzip
> 0.8.1/rc1/apache-iotdb-0.8.1-incubating-source-release.zip".
>
> Details of three ❗ items:
>
> ❗ c. UNPACK the binary artefact and check the contents of LICENSE-binary
> and NOTICE-binary
>
> NOTICE-binary HIVE shows 2008-2018 while NOTICE HIVE shows 2008-2019.
>
> ❗ e. [RM] review target/rat.txt (though the build should fail if RAT
> constraints aren't met)
>
> I didn't find the 'rat.txt' in the download staged artifacts. I don't know
> if it is right.
>
> ❗ f. Search for SNAPSHOT references
>
> I found ./hadoop/pom.xml reference 0.8.0-SNAPSHOT. The hadoop module is
> excluded from the build.
>
>
>
>
> By the way, there are some issues in the README.md:
>
> The referenced wbesite https://iotdb.apache.org/#/Download does not have
> 0.8.1 version yet. Maybe we can update the website quickly after this
> release.
>
> Out-of-date information in the Configure chapter: Now we have two more
> configuration files: logback-tool.xml and iotdb-sync-client.properties.
>
>
>
>
> Sincerely,
>
> Lei Rui
>
> ---
>
> [1]
> 
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
>
> [2] https://github.com/apache/incubator-iotdb/pull/441
>
>
>
> On 9/30/2019 09:18,Willem Jiang wrote:
> Hi Xiangdong,
>
> You may close this vote before starting a new vote.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Sun, Sep 29, 2019 at 7:17 PM Xiangdong Huang 
> wrote:
>
> Hi,
>
> As Chris and Jialin pointed out some issues, I will release RC2 to fix 
them
> later.
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
> 黄向东
> 清华大学 软件学院
>
>
> Jialin Qiao  于2019年9月29日周日 上午11:00写道:
>
> Hi,
>
> -1 (binding)
>
> Major bug: The version printed in client is still 0.8.0
>
> Others are all ok, I checked:
>
> Binary release:
> has NOTICE, LICENSE and DISCLAIMER
> Start server ok
> Start client ok
> compatible with 0.8.0, both client-0.8.1 with server-0.8.0 and
> 

Re: Release of 0.8.1

2019-09-27 Thread Julian Feinauer
Wow, that is unexpected and probably something you should also share with infra 
if they do not know already...

Thank you very much for bringing it up and spotting it!

Julian

From: Xiangdong Huang 
Sent: Friday, September 27, 2019 6:18:09 PM
To: dev@iotdb.apache.org 
Subject: Re: Release of 0.8.1

Hi,

Hm... I finally solve the problem and for *ALL* committers *in China*
please pay attention:

If you do not have a VPN (a regular VPN like L2TP), and you never uploaded
your GPG KEY to a key server,
then you can not use pgp.mit.edu as the destination of the key server...
I think all of you Chinese guys know why...

And, you even can not use pool.sks-keyservers.net:11371 because the
terminal will say: gpg: keyserver search failed: No route to host

So, how to upload your key to a key server?..

Fortunately you can find a dozen of server addresses from [1], I tried two
of them, [2] and [3]. Then I tried another [4].

Actually you still can not use command `gpg --keyserver --send-key` to
upload your key successfully.

But, if you open these urls using your browser, you can find a button
called `Submit Key`! Just paste your ascii public key here..

Your ascii public key looks like:

-BEGIN PGP PUBLIC KEY BLOCK-

mQINBF2LLTABEACRM0lzt9BMSsIg9cCfcEBRH6Fc2etS7vrOt8NPq2VTuHYHUMzA
...
-END PGP PUBLIC KEY BLOCK-

Then, you can search your key id from [4] or [5]. By the way, you can not
get any result if you enter key id like 2206EF8F64C35889.

But, if you input the key id as your email address (that you wrote when you
generate the key), you will find a result, and it means you have uploaded
your GPG key successfully!

(What confusing me is that I still can not get my public key from [2] or
[3])

Then you can close the staging repository successfully. Cheers!

[1] https://sks-keyservers.net/overview-of-pools.php
[2] ipv4.pool.sks-keyservers.net
[3] p80.pool.sks-keyservers.net
[4] http://keys.gnupg.net
[5] http://pool.sks-keyservers.net:11371/#

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Xiangdong Huang  于2019年9月27日周五 下午10:19写道:

> Hi Julian,
>
> Thanks for your reply. I think I uploaded the key about 20 hours ago, so
> does it really need so long time to sync...?
>
> Then I tried to search your key id and Chris's key id on the website (
> http://pool.sks-keyservers.net:11371/), the website also says not
> found...
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> Julian Feinauer  于2019年9月27日周五 下午10:03写道:
>
>> Hi,
>>
>> it can take some time fort he keyservers to sync, so this could be one
>> issue.
>> Just try it again later.
>>
>> Julian
>>
>> Am 27.09.19, 16:00 schrieb "Xiangdong Huang" :
>>
>> Hi all,
>>
>> Thanks for taking care of this release...
>>
>> One more question that I am facing...
>>
>> Now I am trying to closing the staging repository from the Nexus [1],
>> but fails because "No public key: Key with id: (2206ef8f64c35889) was
>> not
>> able to be located on http://pool.sks-keyservers.net:11371;>
>> http://pool.sks-keyservers.net:11371."
>>
>> Actually I have created a GPG KEY by following the documents [2] and
>> [3],
>> attached the public key to KEYS file, uploaded the new KEYS to SVN
>> [4],
>> and have uploaded the key to keyserver by using `gpg2 --keyserver
>> pgp.mit.edu --send-keys MY KEY ID` .
>> Now, if I run `gpg2 --keyserver pgp.mit.edu --search-keys
>> Xiangdong`. I can
>> find the public key like:
>>
>> gpg: data source: http://pgp.mit.edu:11371
>> (1) Xiangdong Huang (Apache IoTDB release signing key) <
>> h...@apache.org>
>>  4096 bit RSA key 2206EF8F64C35889, created: 2019-09-25
>>
>> Would someone kind to help me to tell me why the public key is not
>> able to
>> be located on pool.sks-keyservers.net?
>>
>> Best,
>>
>> [1] https://repository.apache.org/#stagingRepositories
>> [2] https://spark.apache.org/release-process.html
>> [3] https://www.apache.org/dev/openpgp.html#generate-key
>> [4] https://dist.apache.org/repos/dist/dev/incubator/iotdb/KEYS
>>
>> ---
>> Xiangdong Huang
>> School of Software, Tsinghua University
>>
>>  黄向东
>> 清华大学 软件学院
>>
>>
>> Julian Feinauer  于2019年9月27日周五
>> 下午8:13写道:
>>
>> > Hey,
>> >
>> > but I think we are totally covered here by Ap

Re: Release of 0.8.1

2019-09-27 Thread Julian Feinauer
Hi,

it can take some time fort he keyservers to sync, so this could be one issue.
Just try it again later.

Julian

Am 27.09.19, 16:00 schrieb "Xiangdong Huang" :

Hi all,

Thanks for taking care of this release...

One more question that I am facing...

Now I am trying to closing the staging repository from the Nexus [1],
but fails because "No public key: Key with id: (2206ef8f64c35889) was not
able to be located on http://pool.sks-keyservers.net:11371;>
http://pool.sks-keyservers.net:11371."

Actually I have created a GPG KEY by following the documents [2] and [3],
attached the public key to KEYS file, uploaded the new KEYS to SVN [4],
and have uploaded the key to keyserver by using `gpg2 --keyserver
pgp.mit.edu --send-keys MY KEY ID` .
Now, if I run `gpg2 --keyserver pgp.mit.edu --search-keys Xiangdong`. I can
find the public key like:

gpg: data source: http://pgp.mit.edu:11371
(1) Xiangdong Huang (Apache IoTDB release signing key) 
 4096 bit RSA key 2206EF8F64C35889, created: 2019-09-25

Would someone kind to help me to tell me why the public key is not able to
be located on pool.sks-keyservers.net?

Best,

[1] https://repository.apache.org/#stagingRepositories
[2] https://spark.apache.org/release-process.html
[3] https://www.apache.org/dev/openpgp.html#generate-key
[4] https://dist.apache.org/repos/dist/dev/incubator/iotdb/KEYS

---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院

    
Julian Feinauer  于2019年9月27日周五 下午8:13写道:

> Hey,
>
> but I think we are totally covered here by Apache Policy as a Release is
> only a release (and released) if its source in the svn.
> So although this thing has the "name" release in the tag it has strictly
> speaking nothing to do with an APACHE release at all.
>
> In fact, this is the practice we also use in PLC4X (and in many other
> projects).
>
> Julian
>
> Am 27.09.19, 11:58 schrieb "Justin Mclean" :
>
> Hi,
>
> > That's what maven automatically does ... it tags the potential
> release in the repo.
> > That Github shows these release tags as "released" versions is a
> issue that has been discussed in the past.
>
> Which I believe why you should do do maven release after you have
> voted on the release. Maven is not where Apache releases software, it’s
> only a secondary distribution mechinism.
>
> Thanks,
> Justin
>
>




Re: Release of 0.8.1

2019-09-27 Thread Julian Feinauer
Hey,

but I think we are totally covered here by Apache Policy as a Release is only a 
release (and released) if its source in the svn.
So although this thing has the "name" release in the tag it has strictly 
speaking nothing to do with an APACHE release at all.

In fact, this is the practice we also use in PLC4X (and in many other projects).

Julian

Am 27.09.19, 11:58 schrieb "Justin Mclean" :

Hi,

> That's what maven automatically does ... it tags the potential release in 
the repo.
> That Github shows these release tags as "released" versions is a issue 
that has been discussed in the past.

Which I believe why you should do do maven release after you have voted on 
the release. Maven is not where Apache releases software, it’s only a secondary 
distribution mechinism.

Thanks,
Justin



Re: Release of 0.8.1

2019-09-26 Thread Julian Feinauer
Hi Xiangdong,

thank you very much for taking care of the release as RM.
Normal practice would be to keep all work in the rel/0.8 branch and just merge 
in the develop there and do the release tags and stuff in there.

Feel free to ask me (or also Chris) if you have questions or issues!
Julian

Am 26.09.19, 07:03 schrieb "Jialin Qiao" :

Hi,

may be this PR:

* Bug about 'serializedSize' in ChunkGroupMetaData.java
* https://github.com/apache/incubator-iotdb/pull/396/files

--
Jialin Qiao
School of Software, Tsinghua University

乔嘉林
清华大学 软件学院

> -原始邮件-
> 发件人: "Xiangdong Huang" 
> 发送时间: 2019-09-26 12:37:31 (星期四)
> 收件人: dev@iotdb.apache.org
> 抄送: 
> 主题: Re: Release of 0.8.1
> 
> Hi,
> 
> I am working on it. Any else PRs that should be involved in 0.8.1?
> 
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
> 
>  黄向东
> 清华大学 软件学院
> 
> 
> Jialin Qiao  于2019年9月17日周二 下午12:53写道:
> 
> > Hi,
> >
> > I went through recent PRs and list those related to bug-fix of 0.8.0.
> >
> > * bug in updating startTime and endTime in TsFileResource
> > * https://github.com/apache/incubator-iotdb/pull/347
> > * bug of Mix unsequence folder in sequence folder
> > * https://github.com/apache/incubator-iotdb/pull/393
> > * bug in tsfile batch write interface
> > * https://github.com/apache/incubator-iotdb/pull/344
> > * https://github.com/apache/incubator-iotdb/pull/385
> > * bug in query with partition info of TsFile
> > * https://github.com/apache/incubator-iotdb/pull/382
> > * bug in tsfile module in example
> > * https://github.com/apache/incubator-iotdb/pull/378
> > * bug of the serialized size of String
> > * https://github.com/apache/incubator-iotdb/pull/377
> > * bug of docs (maven version)
> > * https://github.com/apache/incubator-iotdb/pull/364
> >
> > The 0.8.1 could contain these commits.
> >
> > Best,
> > --
> > Jialin Qiao
> > School of Software, Tsinghua University
> >
> > 乔嘉林
> > 清华大学 软件学院
> >
> > > -原始邮件-
> > > 发件人: "Jialin Qiao (Jira)" 
> > > 发送时间: 2019-09-17 11:53:00 (星期二)
> > > 收件人: dev@iotdb.apache.org
> > > 抄送:
> > > 主题: [jira] [Created] (IOTDB-216) Release of 0.8.1
> > >
> > > Jialin Qiao created IOTDB-216:
> > > -
> > >
> > >  Summary: Release of 0.8.1
> > >  Key: IOTDB-216
> > >  URL: https://issues.apache.org/jira/browse/IOTDB-216
> > >  Project: Apache IoTDB
> > >   Issue Type: Task
> > > Reporter: Jialin Qiao
> > >
> > >
> > > This is a bug-fix version of 0.8.0
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > --
> > > This message was sent by Atlassian Jira
> > > (v8.3.2#803003)
> >




Re: Reminding of changes in RPC

2019-09-23 Thread Julian Feinauer
+1

Am 20.09.19, 08:07 schrieb "Jialin Qiao" :

Hi,

+1, we will only pick bug-fix commits to 0.8.x, PRs that are not compatible 
with 0.8.0 will go to 0.9. 

Best,
--
Jialin Qiao
School of Software, Tsinghua University

乔嘉林
清华大学 软件学院

> -原始邮件-
> 发件人: "Julian Feinauer" 
> 发送时间: 2019-09-19 23:07:16 (星期四)
> 收件人: "dev@iotdb.apache.org" 
> 抄送: 
> 主题: AW: Reminding of changes in RPC
> 
> Totally agree. This should be considered a change not just a fix and thus 
be in a version 0.9.x but not in 0.8.x
> 
> Julian
> 
> Von meinem Mobiltelefon gesendet
> 
> 
>  Ursprüngliche Nachricht 
> Betreff: Re: Reminding of changes in RPC
> Von: 徐毅
> An: dev@iotdb.apache.org
> Cc:
> 
> Hi,
> 
> 
> Change definitions in rpc.thrift should be careful.
> For example, you have jdbc with 0.8.0 and iotdb with 0.8.1 whose 
rpc.thrit are a little bit different. It is most likely that you cannot use  
jdbc with 0.8.0 to connect iotdb with 0.8.1 since they are not compatible.  
This may confuse our users why two 0.8.x are not compatible?
> 
> 
> Therefore, i would suggest that if there is no great improvement,  
the original definitions should be remained.
> 
> 
> Thanks
> XuYi
> 
> 
> On 9/19/2019 20:03,孙泽嵩 wrote:
> Hi,
> 
> 
> I have renamed some variable and struct names in RPC in PR [1]:
> Rename TS_Status to TSStatus;
> Rename TS_StatusType to TSStatusType;
> Use TSStatus to replace TSRPCRsp. (Since it only contains TSStatus field)
> 
> 
> If you are working on JDBC or session, please pull latest master code to 
avoid more conflicts.
> 
> 
> Besides, if any people changed RPC, remember  to maintain the file 
`rpc-changelist.md` in service-rpc module. It is helpful for other developers : 
)
> 
> 
> [1] https://github.com/apache/incubator-iotdb/pull/404
> 
> 
> 
> 
> BR,
> 
> 
> --
> Zesong Sun
> School of Software, Tsinghua University
> 
> 孙泽嵩
> 清华大学 软件学院




AW: Reminding of changes in RPC

2019-09-19 Thread Julian Feinauer
Totally agree. This should be considered a change not just a fix and thus be in 
a version 0.9.x but not in 0.8.x

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: Reminding of changes in RPC
Von: 徐毅
An: dev@iotdb.apache.org
Cc:

Hi,


Change definitions in rpc.thrift should be careful.
For example, you have jdbc with 0.8.0 and iotdb with 0.8.1 whose rpc.thrit 
are a little bit different. It is most likely that you cannot use  jdbc with 
0.8.0 to connect iotdb with 0.8.1 since they are not compatible.  This may 
confuse our users why two 0.8.x are not compatible?


Therefore, i would suggest that if there is no great improvement,  the 
original definitions should be remained.


Thanks
XuYi


On 9/19/2019 20:03,孙泽嵩 wrote:
Hi,


I have renamed some variable and struct names in RPC in PR [1]:
Rename TS_Status to TSStatus;
Rename TS_StatusType to TSStatusType;
Use TSStatus to replace TSRPCRsp. (Since it only contains TSStatus field)


If you are working on JDBC or session, please pull latest master code to avoid 
more conflicts.


Besides, if any people changed RPC, remember  to maintain the file 
`rpc-changelist.md` in service-rpc module. It is helpful for other developers : 
)


[1] https://github.com/apache/incubator-iotdb/pull/404




BR,


--
Zesong Sun
School of Software, Tsinghua University

孙泽嵩
清华大学 软件学院


Re: Release of 0.8.1

2019-09-18 Thread Julian Feinauer
Hi,

I like the idea of more releases.
But I suggest to do one at a time during learning... would you do the RM this 
time @Xiangdong Huang?

Julian

Am 17.09.19, 01:02 schrieb "Xiangdong Huang" :

Hi,

Thanks Jialin.

As there is so many bugs that be solved, how about starting to release
0.8.1?

I think we can make the release more frequent to let more PPMCs know how to
release.

By the way, as the new API is introduced (session API), I think we can
release a new version 0.9 at the same time.

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Jialin Qiao  于2019年9月17日周二 下午12:53写道:

> Hi,
>
> I went through recent PRs and list those related to bug-fix of 0.8.0.
>
> * bug in updating startTime and endTime in TsFileResource
> * https://github.com/apache/incubator-iotdb/pull/347
> * bug of Mix unsequence folder in sequence folder
> * https://github.com/apache/incubator-iotdb/pull/393
> * bug in tsfile batch write interface
> * https://github.com/apache/incubator-iotdb/pull/344
> * https://github.com/apache/incubator-iotdb/pull/385
> * bug in query with partition info of TsFile
> * https://github.com/apache/incubator-iotdb/pull/382
> * bug in tsfile module in example
> * https://github.com/apache/incubator-iotdb/pull/378
> * bug of the serialized size of String
> * https://github.com/apache/incubator-iotdb/pull/377
> * bug of docs (maven version)
> * https://github.com/apache/incubator-iotdb/pull/364
>
> The 0.8.1 could contain these commits.
>
> Best,
> --
> Jialin Qiao
> School of Software, Tsinghua University
>
> 乔嘉林
> 清华大学 软件学院
>
> > -原始邮件-
> > 发件人: "Jialin Qiao (Jira)" 
> > 发送时间: 2019-09-17 11:53:00 (星期二)
> > 收件人: dev@iotdb.apache.org
> > 抄送:
> > 主题: [jira] [Created] (IOTDB-216) Release of 0.8.1
> >
> > Jialin Qiao created IOTDB-216:
> > -
> >
> >  Summary: Release of 0.8.1
> >  Key: IOTDB-216
> >  URL: https://issues.apache.org/jira/browse/IOTDB-216
> >  Project: Apache IoTDB
> >   Issue Type: Task
> > Reporter: Jialin Qiao
> >
> >
> > This is a bug-fix version of 0.8.0
> >
> >
> >
> >
> >
> >
> >
> > --
> > This message was sent by Atlassian Jira
> > (v8.3.2#803003)
>




Re: Add bloom filters to TsFile

2019-09-10 Thread Julian Feinauer
Hi,

I like the idea. I'm just adding Claude here as we talked yesterday about a 
bloom filter implementation he has already done.

@cla...@apache.org what do you think? : )

Julian

From: Tian Jiang 
Sent: Tuesday, September 10, 2019 5:14:33 AM
To: dev@iotdb.apache.org 
Subject: Add bloom filters to TsFile



Greetings,


The recent readings remind me that the bloom filter is standard equipment in 
K-VDBs. Although IoTDB is not one of them (at least not typically), the bloom 
filter still helps a lot in various situations. For example, our recent 
experiments gave us an illusion that the time series in a storage group remains 
unchanged. However, that is not the case.


Naturally, in real situations, the number of time series grows over time, due 
to reasons like adding new gears. The old files do not contain such a time 
series. Without the help of bloom filters, we have to check each old file only 
to find that there is no such time series. To my knowledge, this may take a lot 
of time.


So, I suggest we add a bloom filter (or some more efficient one) to each TsFile 
to help skip unwanted files.


| |
Tian Jiang
|
|
jt2594...@163.com
|
签名由网易邮箱大师定制


Re: A simple tool to visualize logs

2019-09-08 Thread Julian Feinauer
Hi,

I definetly need that (to adopt to our stuff!)

Julian

Am 08.09.19, 09:13 schrieb "Xiangdong Huang" :

Hi,

Sounds COOOL!

Analyzing system log is one of the most thing for a complex system
(especially for distributed system).

Will try this feature ASAP :D

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Tian Jiang  于2019年9月4日周三 下午7:59写道:

> Greetings,
>
>
>
>
> Usually, the very first thing we will do on finding a bug is to search the
> logs. Logs play a vital role in debugging especially in some environment
> that attaching a debugger is impossible. In such circumstance, logs will
> hopefully become the only information sources for the developers.
>
>
>
> However, a single log, which is just a string, is easy to understand. But
> when it comes to mining information from thousands of logs or even more,
> getting lost is nearly unavoidable, since humans have a much limited 
memory
> for exact truth compared to computers. From time to time, I forget what I
> have read before and I must go back to review the previous logs, as a
> result, progress is made very slowly. Reading several strings is easy, but
> when we have thousands, there must be some better way to present them than
> raw text.
>
>
>
> So, I keep thinking it would be much better if we can make the logs into
> plots. Of course there must some existing tools, but they are often
> powerful but too heavy (like Kibana) , or specialized for web or other 
logs
> (like LogStalgia). Having a fantastic web interface is great, but a simple
> but handy suit us better. What I want is something light-weighted,
> stand-alone and highly customized.
>
>
>
> As a result, I developed a simple tool that can visualize (plot) logs
> generated by IoTDB (with some modification, it can be applied to other 
type
> of logs, too) and generate report. I designed a simple GUI which provides
> full functionalities and a command line tool to fast generate reports. The
> attachment contains an example report I generated from one of my
> experiments, which reveal interesting things like how the size of 
memtables
> converges over time.
>
>
>
> I may have missed some tools that are more powerful or easier to use. If
> you know any, please inform me and I shall see what I can learn from them.
>
>
>
> | |
> Tian Jiang
> |
> |
> jt2594...@163.com
> |
> 签名由网易邮箱大师定制




Re: A new result set format

2019-09-07 Thread Julian Feinauer
Hi,

I think this is one oft he most important discussion to make it easily 
accessible to users.
As Xiangdong states, we have to make it comfortable for users to map to 
relational schemes.

And I agree that there are use cases for both, so probably really just provide 
both.

Julian

Am 07.09.19, 13:18 schrieb "Xiangdong Huang" :

Hi,

Glad to see this discussion.

I am on my travel so I have no enough time these days to join with you but
I will never miss this discussion..

The discussion is important because the query is the highest frequent
function that user use IoTDB and make data valuable.
Besides, it will impact how we transfer ioTDB's schema view to a relational
schema view (e.g., be integrated with Calcite.).

I think Lei Rui got the key difference: the wide, the narrow and the
narrowest table depends on "how to align the data".

- If we want to align all timeseries according to the timestamp, then it is
a wide table. (minor issue: I think for sql "select * from root.sg_1", the
printed result should be "d1.s1, d1.s2..." rather than "root.sg1.d1.s1,
root.sg1.d1.s2". So the table's head row can be concise)

- If we want to align all timeseries that belong to the same device (i.e.,
the data source) according to the time stamp, then it is a narrow table.

- If we do not want to align data, then it is the narrowest table.

I do not know which one that users like. If we decide support  all the
three format, maybe an ALIGN clause can be introduced in our SQL. (Well,
Jialin said it as "Group By", I  am not sure which one is better).

Best,


在 2019年9月7日星期六,Rui, Lei  写道:

> Sorry, pictures cannot be attached in the last email I sent . So I
> supplement them here in text.
> The "wide" table is:
> | time | root.sg_1.device_1.sensor_1 | root.sg_1.device_1.sensor_2 |
> root.sg_1.device_2.sensor_1 | root.sg_1.device_2.sensor_2 |
> | 1 | 100 | 2.5 | 99 | 1.3 |
> | ... | ... | ... | ... | ... |
>
>
> The "narrow" table is :
> | time | device_Id | sensor_1 | sensor_2 |
> | 1 | root.sg_1.device_1 | 100 | 2.5 |
> | ... | ... | ... | ... |
> | 1 | root.sg_1.device_2 | 99 | 1.3 |
> | ... | ... | ... | ... |
> On 9/7/2019 15:51,Rui, Lei wrote:
> Hi,
>
>
> I try to make this proposal more concrete from a semantic perspective.
>
>
> Consider the sql "select * from root.sg_1". The following format is the
> "wide" table:
>
>
> The following format is the "narrow" table:
>
>
> The levels of data from low to high are:
> - sensor data, or series data, e.g., from root.sg_1.device_1.sensor_1
> - device data, e.g., from root.sg_1.device_1
> - storage group data , e.g., from root.sg_1
>
>
> So, the sql "select * from root.sg_1" queries data at the storage group
> level. To present the results,
> the wide table aligns all series data across multiple devices in the
> storage group by timestamp,
> while the narrow table aligns series data in a single device by timestamp,
> and does the same for other devices in the storage group.
>
>
> By the way, I guess the "narrowest" table is for a single sensor's data,
> without the need to align with any other series data.
>
>
> I have one question:
> Why not make full use of sql and just use "select * from
> root.sg_1.device_1" to specify the device (or the data level) they care
> about?
> Why use "select * from root.sg_1" with a narrow table format?
>
>
> Lastly, I think the better query execution efficiency that a narrow table
> may sometimes has is not the drive purpose,
> because presenting the query result in a wide table and in a narrow table
> are two different tasks.
>
>
> Sincerely,
> Lei Rui
>
>
> From: Jialin Qiao 
> Date: 9/7/2019 15:26
> To: 
> Subject: Re: A new result set format
> Hi Julian,
>
> He is my friend and contacted me offline, because I advertise IoTDB in my
> weChat(like facebook or twitter).
>
> Next time I will try to let him put issue in the mail list himself :)
>
> Best,
> --
> Jialin Qiao
> School of Software, Tsinghua University
>
> 乔嘉林
> 清华大学 软件学院
>
> -原始邮件-
> 发件人: "Julian Feinauer" 
> 发送时间: 2019-09-07 13:52:17 (星期六)
> 收件人: "dev@iotdb.apache.org&qu

Re: A new result set format

2019-09-07 Thread Julian Feinauer
Hi Jialin,

well thats no hard requirement... ist totally fine if things come in that way 
from time to time : )
As I'm so new to IoTDB I'm just still trying to understand whats the user group 
currently and who drives feature ideas and stuff : )

I hope that we start soon with using IoTDB and then we'll very likely also 
contribute some wishes : )

Julian

Am 07.09.19, 09:26 schrieb "Jialin Qiao" :

Hi Julian,

He is my friend and contacted me offline, because I advertise IoTDB in my 
weChat(like facebook or twitter). 

Next time I will try to let him put issue in the mail list himself :)

Best,
--
Jialin Qiao
School of Software, Tsinghua University

乔嘉林
清华大学 软件学院

> -原始邮件-
> 发件人: "Julian Feinauer" 
> 发送时间: 2019-09-07 13:52:17 (星期六)
> 收件人: "dev@iotdb.apache.org" 
> 抄送: 
> 主题: Re: A new result set format
> 
> Hi Jialin,
> 
> perhaps one question about "wanted by users" means (as I didn’t see 
anything on the list).
> How do these users get in contact with you?
> 
> Julian
> 
> Am 07.09.19, 04:29 schrieb "Jialin Qiao" :
> 
> Hi,
> 
> As described in this issue, a new result set format is wanted by 
users. I'd like to open a discussion here.
> 
> For simplicity, I refer this format "time, root.sg1.d1.s1, 
root.sg1.d2.s1" to wide table, and "time, deviceId, s1" as narrow table. 
> 
> This issue is not only about how to organize the results, but also 
the query process. 
> 
> There are some advantages about narrow table.
> 
> (1) For wide table, we need to open a SeriesReader for each series at 
the same time, each SeriesReader holds some ChunkMetadatas. For narrow table, 
we only need to open SeriesReaders for one device at one time, then return 
results and open SeriesReaders for the next device, which occupies less memory 
compared to the wide table. 
> (2) Avoid reading all series at once may also improve the query 
latency.
> 
> There is also a question:
> 
> (1) If we show result in the narrow table format for users, do we 
need to highlight the concept of table and device? 
> (2) If the answer of the first question is yes, do we need to support 
sql: "select time, deviceId, s1, s2, s3 from root.sg1 where deviceId=d1"? This 
may involve a lot of work...
> 
> From my side, I prefer the answers of the two questions are all NO. 
Then we do not need to change the sql grammar and only use a new query process 
to organize the result set.
> 
> Best,
> --
> Jialin Qiao
> School of Software, Tsinghua University
> 
> 乔嘉林
> 清华大学 软件学院
> 
> > -原始邮件-
> > 发件人: "Jialin Qiao (Jira)" 
> > 发送时间: 2019-09-07 09:40:00 (星期六)
> > 收件人: dev@iotdb.apache.org
> > 抄送: 
> > 主题: [jira] [Created] (IOTDB-203) A new result set format
> > 
> > Jialin Qiao created IOTDB-203:
> > -
> > 
> >  Summary: A new result set format
> >  Key: IOTDB-203
> >  URL: 
https://issues.apache.org/jira/browse/IOTDB-203
> >  Project: Apache IoTDB
> >   Issue Type: New Feature
> > Reporter: Jialin Qiao
> > 
> > 
> > When executing a SQL like "select d1.s1, d2.s1 from root.sg1", the 
default result set format in IoTDB is 
> > 
> > "time, root.sg1.d1.s1, root.sg1.d2.s1"
> > 
> > 1 , 1, 1
> > 
> > 2, 2, 2
> > 
> > However, some users want to get another format, The results could 
be grouped by device, then sorted by time.
> > 
> > "time, deviceId, s1".
> > 
> > 1, root.sg1.d1, 1
> > 
> > 2, root.sg1.d2, 2
> > 
> >  
> > 
> > This can be done in the client, but it would be better if we 
support this format in the server.
> > 
> >  
> > 
> > 
> > 
> > --
> > This message was sent by Atlassian Jira
> > (v8.3.2#803003)
> 
> 




Re: A new result set format

2019-09-06 Thread Julian Feinauer
Hi Jialin,

perhaps one question about "wanted by users" means (as I didn’t see anything on 
the list).
How do these users get in contact with you?

Julian

Am 07.09.19, 04:29 schrieb "Jialin Qiao" :

Hi,

As described in this issue, a new result set format is wanted by users. I'd 
like to open a discussion here.

For simplicity, I refer this format "time, root.sg1.d1.s1, root.sg1.d2.s1" 
to wide table, and "time, deviceId, s1" as narrow table. 

This issue is not only about how to organize the results, but also the 
query process. 

There are some advantages about narrow table.

(1) For wide table, we need to open a SeriesReader for each series at the 
same time, each SeriesReader holds some ChunkMetadatas. For narrow table, we 
only need to open SeriesReaders for one device at one time, then return results 
and open SeriesReaders for the next device, which occupies less memory compared 
to the wide table. 
(2) Avoid reading all series at once may also improve the query latency.

There is also a question:

(1) If we show result in the narrow table format for users, do we need to 
highlight the concept of table and device? 
(2) If the answer of the first question is yes, do we need to support sql: 
"select time, deviceId, s1, s2, s3 from root.sg1 where deviceId=d1"? This may 
involve a lot of work...

From my side, I prefer the answers of the two questions are all NO. Then we 
do not need to change the sql grammar and only use a new query process to 
organize the result set.

Best,
--
Jialin Qiao
School of Software, Tsinghua University

乔嘉林
清华大学 软件学院

> -原始邮件-
> 发件人: "Jialin Qiao (Jira)" 
> 发送时间: 2019-09-07 09:40:00 (星期六)
> 收件人: dev@iotdb.apache.org
> 抄送: 
> 主题: [jira] [Created] (IOTDB-203) A new result set format
> 
> Jialin Qiao created IOTDB-203:
> -
> 
>  Summary: A new result set format
>  Key: IOTDB-203
>  URL: https://issues.apache.org/jira/browse/IOTDB-203
>  Project: Apache IoTDB
>   Issue Type: New Feature
> Reporter: Jialin Qiao
> 
> 
> When executing a SQL like "select d1.s1, d2.s1 from root.sg1", the 
default result set format in IoTDB is 
> 
> "time, root.sg1.d1.s1, root.sg1.d2.s1"
> 
> 1 , 1, 1
> 
> 2, 2, 2
> 
> However, some users want to get another format, The results could be 
grouped by device, then sorted by time.
> 
> "time, deviceId, s1".
> 
> 1, root.sg1.d1, 1
> 
> 2, root.sg1.d2, 2
> 
>  
> 
> This can be done in the client, but it would be better if we support this 
format in the server.
> 
>  
> 
> 
> 
> --
> This message was sent by Atlassian Jira
> (v8.3.2#803003)




AW: time series with double datatype insert problem

2019-09-05 Thread Julian Feinauer
Hi yes, that's javas default. Float types always with dot.

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: time series with double datatype insert problem
Von: Jialin Qiao
An: dev@iotdb.apache.org
Cc:

Hi,

When I try the following java codes, it always print 0.0.

```
float a = 0f;
System.out.println(a);
a = 0.0f;
System.out.println(a);
double b = 0d;
System.out.println(b);
b = 0.0d;
System.out.println(b);
```

I think it is fine to print 0.0 in the IoTDB Client, as long as it is a float 
value (0f). I wonder how could KairosDB print 0...

Best,
--
Jialin Qiao
School of Software, Tsinghua University

乔嘉林
清华大学 软件学院

> -原始邮件-
> 发件人: "勾王敏浩" 
> 发送时间: 2019-09-05 15:02:27 (星期四)
> 收件人: dev@iotdb.apache.org
> 抄送:
> 主题: time series with double datatype insert problem
>
> Hi,
>   Currently, we find that a time series with  DATATYPE=DOUBLE, 
> ENCODING=GORILLA ,when insert a datapoint like (1,0) , it returns (1,0.0). 
> While in KairosDB, it returns (1,0). Do we need to modify this?
>
>
> Thank you,
> Wangminhao Gou
>


Re: A serious hidden but simple bug caused by object abnormal publishing

2019-09-05 Thread Julian Feinauer
Hi,

I agree with Xiangdongs suggestion to have a separate PR for that as its easier 
to review and track it down.
In some cases such "critical bugs" would even lead to a "hotfix" release like 
0.8.1 so its good to have them in a separate commit for cherry-picking also.

Julian

Am 05.09.19, 04:15 schrieb "Xiangdong Huang" :

Hi,

The same question.

> so there must be no overlap between the two parameters

Ok, we need to have a check before startup.

> Therefore, I suspected that it was an abnormal publishing of the sequence
folder list and the unsequence folder list.

What abnormal "publishing" means?

> I tracked all the places where it was possible to use the two objects and
found that it will returned the object directly when I require them from
multi-file directory manager.

the two objects?

The bug seems critical and the solution may just be create a new Java
Object (which overrides the equals() and hashCode()? I guess.), but the
description of the bug is really not so good...

Maybe you can show how to reproduce the bug in the issue description and
then analyze why. And, finally submit a PR just for the issue (rather than
along with the sync module. As you know, the sync module PR may be blocked
for a long time to wait committers to review it, but the bug-fix PR can be
merged quickly because there is no too many code modifications).

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


徐毅  于2019年9月4日周三 上午5:19写道:

> Hi,
>
>
> After reading your explanation, I’m still confused about your problem.
> First, what's the meaning of 'object abnormal publishing’? Can you add 
some
> example codes to define your problem? Besides, you have fixed this problem
> in your sync pr, I suggest you create an individual branch to solve this
> problem since this problem is a common case.
>
>
> By the way, these are few grammar mistakes in your explanation, try to
> avoid them next time. :)
>
>
> Thanks
> XuYi
>
>
>
>
> On 09/4/2019 16:46,李天安 wrote:
> Hi,
> Recently,in developing sync module, I found a very important bug in the
> process of unit testing, which will seriously affect the normal operation
> of the system. During the unit test of sync module, I found that when I
> retrieved the next sequence folder from the multi-file directory manager, 
I
> may get an unseuqence folder, which made me confused and began to track
> down the problem.
>
>
> In IoTDB, sequence folders and unsequence folders are specified as user
> parameters, and currently the name of the sequence folder is "sequence" 
and
> the name of unsequence folder is “unsequence”, so there must be no overlap
> between the two parameters. Therefore, I suspected that it was an abnormal
> publishing of the sequence folder list and the unsequence folder list. I
> tracked all the places where it was possible to use the two objects and
> found that it wil returned the object directly when I require them from
> multi-file directory manager. It is further found that merging the two
> objects acquired in Storage Group Processor causes problems.
>
>
> The problem is very simple and hidden but serious. The reason why it has
> not been found is that this method of incorrectly modifying the contents 
of
> the list is currently only used in the delete module, which is nearly
> unused. Now that this problem has been solved in sync pr, I just want to
> share with you here. The issue of variable publishing still needs to be
> paid attention to. In addition, people interested in sync module can focus
> on https://issues.apache.org/jira/browse/IOTDB-198.
>
>
>
>
> Best Regards,
> —
> Tianan Li
> School of Software, Tsinghua University
>
> 李天安
> 清华大学 软件学院




AW: Document of master

2019-09-03 Thread Julian Feinauer
It also is a good training opportunity for new RMs :)

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: Document of master
Von: Justin Mclean
An: dev@iotdb.apache.org
Cc:

HI,

> Some users want to use the functions in master. However, when they request 
> the documents,

Then you should release more frequently.

Thanks,
Justin


AW: podling report draft - September 2019

2019-09-01 Thread Julian Feinauer
I like it. Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: podling report draft - September 2019
Von: Xiangdong Huang
An: dev@iotdb.apache.org
Cc:

Hi,

I update the draft according to Chris and Justin's suggestions. If there is
no more suggestion, I will update it to the confluence.

IoTDB is a data store for managing large amounts of time series data such
as timestamped data from IoT sensors in industrial applications.

IoTDB has been incubating since 2018-11-18.

1. Three most important unfinished issues to address before graduating:

- Make the community (both the contributors and committers/PPMCs) more
diverse  and learn to discuss things on the mailing list.

- More committers should know how to release a version.

- Write more documentation to help new contributors.

2. Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?

- No

3. How has the community developed since the last report?

- Some new contributors joined the community.  E.g., PR#339 comes from a
new contributor and it is really an interesting feature.

- Some contributors (who are not committers yet) are more active than
before. E.g., Boris Zhu and Jack Tsai.

- More users began to report their issues. E.g.,  issue #171, #184 and #186.

As all the above contributions and contributors are not from the
institutions/companies where initial committers are, we think it is a good
signal that indicates more guys noticing the community.

4. How has the project developed since the last report?

- IoTDB releases its first Apache version: v0.8.0 !

- IoTDB is more stable and the performance is far better than before.
However, the version is incompatible with previous version (which are
released before IoTDB is denoted to ASF).

- In v0.8.0, many issues are resolved (see release notes:
http://iotdb.apache.org/#/Materials/Release%20Notes )

5. How would you assess the podling's maturity? Please feel free to add
your own commentary.

 [  ] Initial setup
 [  ] Working towards first release
 [ x ] Community building
 [  ] Nearing graduation
 [  ] Other:

Date of last release:

- 08/25/2019

When were the last committers or PPMC members elected?

- 07/15/2019

Have your mentors been helpful?

- Yes

Have your mentors been helpful and responsive or are things falling through
the cracks? In the latter case, please list any open issues that need to be
addressed.

- They are helpful, especially in the process of releasing the first
version.

Signed-off-by:

 (iotdb) Justin Mclean Comments:
 (iotdb) Christofer Dutz Comments:
 (iotdb) Willem Ning Jiang Comments:
 (iotdb) Kevin A. McGrail Comments:


---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Justin Mclean  于2019年8月31日周六 下午5:31写道:

> Hi,
>
> I was going to say something similar but Chris got there first.
>
> > - Have a plan for the future releasing (e.g., how long time to release a
> > new major/minor version).
>
> I would not list this as am issue, the question is does it block
> graduation? In this case it does not as there is no need for a plan like
> this. Not having a plan may be better and fit in more with a voluntary
> group of contributors.
>
> IMO Having documentation to help new contributors is far more important.
>
> Thanks,
> Justin


Re: Short summary on what you're up to?

2019-08-28 Thread Julian Feinauer
Hi all,

I really would love to drive the Calcite integration further but am lacking 
time AND clarity about the ideal data model to exposte time series as tables 
but I guess that’s nothing for 0.9.0.
And.. I have to file a Jira for that, also : )

Julian

Am 28.08.19, 09:36 schrieb "Xiangdong Huang" :

Hi,

We have an issue to list what we want to put in 0.9.0 [1].

But I think the issue does not cover all what guys in the community are
doing. So,  if you have new ideas and think it can be finished quickly, I
think we can record them on that issue.

And, as now there are so many opened issues, we can also discuss which part
of them can be solved in 0.9.0.
(IMPORTANT: That means, we need a DEADLINE for releasing 0.9.0)

[1] https://issues.apache.org/jira/projects/IOTDB/issues/IOTDB-167

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Christofer Dutz  于2019年8月28日周三 上午12:07写道:

> Hi all,
>
> I think it would be time to post an update on what you guys are currently
> working on.
> For me it’s not very obvious and I guess for any outsider this is probably
> the same.
>
> Chris
>




[ANNOUNCE] Apache IoTDB (incubating) 0.8.0 released

2019-08-25 Thread Julian Feinauer
Hi all,

Finally, the official announce went out... See  [1] below for the mail.
Now, the release is finished.

Thanks again to all who helped!

Julian

[1] 
https://lists.apache.org/x/thread.html/e362abd59de0711bf4653f82f99192980a4c70a29844f7130ab5ddda@%3Cannounce.apache.org%3E

Von meinem Mobiltelefon gesendet


AW: [jira] [Created] (IOTDB-175) dist.apache.org must not be used for public downloads

2019-08-23 Thread Julian Feinauer
Thanks. If you close the issue Sebb will get notified and hopefully our 
announce can go out then.

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: [jira] [Created] (IOTDB-175) dist.apache.org must not be used for 
public downloads
Von: Xiangdong Huang
An: dev@iotdb.apache.org
Cc:

Hi, fixed for that.
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Sebb (Jira)  于2019年8月23日周五 下午5:49写道:

> Sebb created IOTDB-175:
> --
>
>  Summary: dist.apache.org must not be used for public
> downloads
>  Key: IOTDB-175
>  URL: https://issues.apache.org/jira/browse/IOTDB-175
>  Project: Apache IoTDB
>   Issue Type: Bug
> Reporter: Sebb
>
>
> The dist.apache.org server is only intended for use by developers in
> staging releases.
>
> It must not be used on public download pages.
> Please use https://www.apache.org/dist for KEYS, hashes and sigs
>
> The current download page uses dist.a.o for the KEYS file; please replace
> this
>
>
>
> --
> This message was sent by Atlassian Jira
> (v8.3.2#803003)
>


Re: Homepage fix

2019-08-23 Thread Julian Feinauer
Hi Xiangdong,

thank you soo much for your work.
I just resubmitted the announce and hope it gets through this time : )

So many things to learn on a first release (I also didn’t knew that stuff 
regarding download section, as you see __ ).

Julian

Am 23.08.19, 01:53 schrieb "Xiangdong Huang" :

Hi,

I have fixed these hyperlinks.

- KEYS, SHA512, ASC are linked to the dist website  [0]-[4]
- binary and source files are linked to the mirrors [5][6]
- release notes file is on the iotdb website, [7]
- Verifying Hashes and Signatures section is added

Hope it meets Apache's requirements.

[0] https://dist.apache.org/repos/dist/release/incubator/iotdb/KEYS
[1]

https://www.apache.org/dist/incubator/iotdb/0.8.0-incubating/apache-iotdb-0.8.0-incubating-bin.zip.sha512
[2]

https://www.apache.org/dist/incubator/iotdb/0.8.0-incubating/apache-iotdb-0.8.0-incubating-bin.zip.asc
[3]

https://www.apache.org/dist/incubator/iotdb/0.8.0-incubating/apache-iotdb-0.8.0-incubating-source-release.zip.sha512
[4]

https://www.apache.org/dist/incubator/iotdb/0.8.0-incubating/apache-iotdb-0.8.0-incubating-source-release.zip.asc
[5]

https://www.apache.org/dyn/closer.cgi/incubator/iotdb/0.8.0-incubating/apache-iotdb-0.8.0-incubating-bin.zip
[6]

https://www.apache.org/dyn/closer.cgi/incubator/iotdb/0.8.0-incubating/apache-iotdb-0.8.0-incubating-source-release.zip
[7] http://iotdb.apache.org/#/Materials/Release%20Notes

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


    Julian Feinauer  于2019年8月23日周五 上午3:16写道:

> Hi xiangdong,
>
> good catch there... I'm unsure how to proceed as we are not allowed to
> change the RELEASE NOTES in dist but I think it should be fine to copy the
> content on the homepage (we do this e.g. for PLC4X that way, see here
> http://plc4x.apache.org/users/download.html ).
> Then you can reformat it.
> What do you think?
>
> Julian
>
> Am 22.08.19, 07:11 schrieb "Xiangdong Huang" :
>
> Hi,
>
> Done.
>
> One more thing: the format of current RELEASE_NOTES file on
>
> 
https://www.apache.org/dist/incubator/iotdb/0.8.0-incubating/RELEASE_NOTES.md
> is
> incorrect. On MacOS, there is no line break... Therefore, I did not
> adopt
> this url.
>
> Best,
>
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> Xiangdong Huang  于2019年8月22日周四 下午12:48写道:
>
> > Hi,
> >
> > do we need the hyperlink of KEYS?
> >
> > I can only get the key file from
> > https://dist.apache.org/repos/dist/dev/incubator/iotdb/KEYS
> > However, should it be at
> > https://dist.apache.org/repos/dist/incubator/iotdb/KEYS (i.e., no
> "dev")
> >
> > Best,
> >
> >
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> >  黄向东
> > 清华大学 软件学院
> >
> >
> > Julian Feinauer  于2019年8月22日周四
> 上午12:24写道:
> >
> >> Just a short addition:
> >> I copied from the flink site the following statement (which should
> >> suffice), regarding the hash verification:
> >>
> >>
> >> Verifying Hashes and Signatures
> >>
> >> Along with our releases, we also provide sha512 hashes in *.sha512
> files
> >> and cryptographic signatures in *.asc files. The Apache Software
> Foundation
> >> has an extensive tutorial to verify hashes and signatures which you
> can
> >> follow by using any of these release-signing KEYS.
> >>
> >> Am 21.08.19, 18:22 schrieb "Julian Feinauer" <
> >> j.feina...@pragmaticminds.de>:
> >>
> >> Hey,
> >>
> >> I got some further requests to fix which we should address
> before the
> >> announce goes out...
> >> It would be good if someone could help with the fixes
> >>
> >> ===
> >>

Re: Homepage fix

2019-08-22 Thread Julian Feinauer
Hi xiangdong,

good catch there... I'm unsure how to proceed as we are not allowed to change 
the RELEASE NOTES in dist but I think it should be fine to copy the content on 
the homepage (we do this e.g. for PLC4X that way, see here 
http://plc4x.apache.org/users/download.html ).
Then you can reformat it.
What do you think?

Julian

Am 22.08.19, 07:11 schrieb "Xiangdong Huang" :

Hi,

Done.

One more thing: the format of current RELEASE_NOTES file on

https://www.apache.org/dist/incubator/iotdb/0.8.0-incubating/RELEASE_NOTES.md
is
incorrect. On MacOS, there is no line break... Therefore, I did not adopt
this url.

Best,

---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Xiangdong Huang  于2019年8月22日周四 下午12:48写道:

> Hi,
>
> do we need the hyperlink of KEYS?
>
> I can only get the key file from
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/KEYS
> However, should it be at
> https://dist.apache.org/repos/dist/incubator/iotdb/KEYS (i.e., no "dev")
>
> Best,
>
>
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
    >
>  黄向东
> 清华大学 软件学院
>
>
> Julian Feinauer  于2019年8月22日周四 上午12:24写道:
>
>> Just a short addition:
>> I copied from the flink site the following statement (which should
>> suffice), regarding the hash verification:
>>
>>
>> Verifying Hashes and Signatures
>>
>> Along with our releases, we also provide sha512 hashes in *.sha512 files
>> and cryptographic signatures in *.asc files. The Apache Software 
Foundation
>> has an extensive tutorial to verify hashes and signatures which you can
>> follow by using any of these release-signing KEYS.
>>
>> Am 21.08.19, 18:22 schrieb "Julian Feinauer" <
>> j.feina...@pragmaticminds.de>:
>>
>> Hey,
>>
>> I got some further requests to fix which we should address before the
>> announce goes out...
>> It would be good if someone could help with the fixes
>>
>> ===
>> The download page must only use https://www.apache.org/dist/... for
>> the
>> KEYS, hashes and sigs.
>> The source and binary artifacts must only use the mirror system, not
>> /dist/...
>>
>> The public download page must not link directly to the source code in
>> GitHub, as that has not been formally released.
>> Such links should be restricted to pages intended for developers.
>>
>> The same considerations apply to the News section.
>>
>> The download page needs say that downloaders should verify releases,
>> and
>> describe how to do so using KEYS + sig, or hash.
>> ===
>>
>> Thanks!
>> Julian
>>
>> Am 21.08.19, 15:28 schrieb "Julian Feinauer" <
>> j.feina...@pragmaticminds.de>:
>>
>> Hi,
>>
>> thanks fort he fast fix, I already resend the ANNOUNCE mail.. so
>> hopefully it comes through soon __
>>
>> Julian
>>
>> Am 21.08.19, 12:59 schrieb "Xiangdong Huang" > >:
>>
>> Hi,
>>
>> As something is wrong in jenkins server, I have manually
>> deployed the
>> latest website.
>>
>> Now http://iotdb.apache.org/#/Download has correct urls.
>>
>> Best,
>> ---
>> Xiangdong Huang
>> School of Software, Tsinghua University
>>
>>  黄向东
>> 清华大学 软件学院
>>
>>
>> Xiangdong Huang  于2019年8月21日周三 下午6:34写道:
>>
>>     > Hi,
>> >
>> > I fixed it. Please review PR
>> > https://github.com/apache/incubator-iotdb-website/pull/30
>> > Or I will merge it a short time later.
>> >
>> > Best,
>> > ---
>> > Xiangdong Huang
>> >

Re: Homepage fix

2019-08-22 Thread Julian Feinauer
Hi Xiangdong,

sorry I was busy whole day (we had plc4x meetup __ ).
I just copied KEYS to 
https://dist.apache.org/repos/dist/release/incubator/iotdb/KEYS which you 
should be able to reference now?

Julian

Am 22.08.19, 07:12 schrieb "Xiangdong Huang" :

Hi,

Ok, after that, I will update the page again.

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


    Julian Feinauer  于2019年8月22日周四 下午1:11写道:

> Hi xiangdong,
>
> Excellent catch... I will move it asap to the other repo and send you a
> notice.
>
> Julian
>
> Von meinem Mobiltelefon gesendet
>
>
>  Ursprüngliche Nachricht 
> Betreff: Re: Homepage fix
> Von: Xiangdong Huang
> An: dev@iotdb.apache.org
> Cc:
>
> Hi,
>
> do we need the hyperlink of KEYS?
>
> I can only get the key file from
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/KEYS
> However, should it be at
> https://dist.apache.org/repos/dist/incubator/iotdb/KEYS (i.e., no "dev")
>
> Best,
>
>
> ---
> Xiangdong Huang
    > School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> Julian Feinauer  于2019年8月22日周四 上午12:24写道:
>
> > Just a short addition:
> > I copied from the flink site the following statement (which should
> > suffice), regarding the hash verification:
> >
> >
> > Verifying Hashes and Signatures
> >
> > Along with our releases, we also provide sha512 hashes in *.sha512 files
> > and cryptographic signatures in *.asc files. The Apache Software
> Foundation
> > has an extensive tutorial to verify hashes and signatures which you can
> > follow by using any of these release-signing KEYS.
> >
> > Am 21.08.19, 18:22 schrieb "Julian Feinauer" <
> > j.feina...@pragmaticminds.de>:
> >
> > Hey,
> >
> > I got some further requests to fix which we should address before 
the
> > announce goes out...
> > It would be good if someone could help with the fixes
> >
> > ===
> > The download page must only use https://www.apache.org/dist/... for
> > the
> > KEYS, hashes and sigs.
> > The source and binary artifacts must only use the mirror system, not
> > /dist/...
> >
> > The public download page must not link directly to the source code 
in
> > GitHub, as that has not been formally released.
> > Such links should be restricted to pages intended for developers.
> >
> > The same considerations apply to the News section.
> >
> > The download page needs say that downloaders should verify releases,
> > and
> > describe how to do so using KEYS + sig, or hash.
> > ===
> >
> > Thanks!
> > Julian
> >
> > Am 21.08.19, 15:28 schrieb "Julian Feinauer" <
> > j.feina...@pragmaticminds.de>:
> >
> > Hi,
> >
> > thanks fort he fast fix, I already resend the ANNOUNCE mail.. so
> > hopefully it comes through soon __
> >
> > Julian
> >
> > Am 21.08.19, 12:59 schrieb "Xiangdong Huang"  >:
> >
> > Hi,
> >
> > As something is wrong in jenkins server, I have manually
> > deployed the
> > latest website.
> >
> > Now http://iotdb.apache.org/#/Download has correct urls.
> >
> > Best,
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> >  黄向东
> > 清华大学 软件学院
> >
> >
> > Xiangdong Huang  于2019年8月21日周三 下午6:34写道:
> >
> > > Hi,
> > >
> > > I fixed it. Please review PR
> > > https://github.com/apache/incubator-iotdb-website/pull/30
> > > Or I will merge it a short time later.
> > >
> > > Best,

AW: Homepage fix

2019-08-21 Thread Julian Feinauer
Hi xiangdong,

Excellent catch... I will move it asap to the other repo and send you a notice.

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: Homepage fix
Von: Xiangdong Huang
An: dev@iotdb.apache.org
Cc:

Hi,

do we need the hyperlink of KEYS?

I can only get the key file from
https://dist.apache.org/repos/dist/dev/incubator/iotdb/KEYS
However, should it be at
https://dist.apache.org/repos/dist/incubator/iotdb/KEYS (i.e., no "dev")

Best,


---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Julian Feinauer  于2019年8月22日周四 上午12:24写道:

> Just a short addition:
> I copied from the flink site the following statement (which should
> suffice), regarding the hash verification:
>
>
> Verifying Hashes and Signatures
>
> Along with our releases, we also provide sha512 hashes in *.sha512 files
> and cryptographic signatures in *.asc files. The Apache Software Foundation
> has an extensive tutorial to verify hashes and signatures which you can
> follow by using any of these release-signing KEYS.
>
> Am 21.08.19, 18:22 schrieb "Julian Feinauer" <
> j.feina...@pragmaticminds.de>:
>
> Hey,
>
> I got some further requests to fix which we should address before the
> announce goes out...
> It would be good if someone could help with the fixes
>
> ===
> The download page must only use https://www.apache.org/dist/... for
> the
> KEYS, hashes and sigs.
> The source and binary artifacts must only use the mirror system, not
> /dist/...
>
> The public download page must not link directly to the source code in
> GitHub, as that has not been formally released.
> Such links should be restricted to pages intended for developers.
>
> The same considerations apply to the News section.
>
> The download page needs say that downloaders should verify releases,
> and
> describe how to do so using KEYS + sig, or hash.
> ===
>
> Thanks!
> Julian
>
> Am 21.08.19, 15:28 schrieb "Julian Feinauer" <
> j.feina...@pragmaticminds.de>:
>
> Hi,
>
> thanks fort he fast fix, I already resend the ANNOUNCE mail.. so
> hopefully it comes through soon __
>
> Julian
>
> Am 21.08.19, 12:59 schrieb "Xiangdong Huang" :
>
> Hi,
>
> As something is wrong in jenkins server, I have manually
> deployed the
> latest website.
>
> Now http://iotdb.apache.org/#/Download has correct urls.
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> Xiangdong Huang  于2019年8月21日周三 下午6:34写道:
>
> > Hi,
> >
> > I fixed it. Please review PR
> > https://github.com/apache/incubator-iotdb-website/pull/30
> > Or I will merge it a short time later.
> >
> > Best,
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> >  黄向东
> > 清华大学 软件学院
> >
> >
> > Julian Feinauer 
> 于2019年8月21日周三 下午6:10写道:
> >
> >> Hi,
> >>
> >> Just got a mail from the announce guys that we need a fix
> on our download
> >> section :
> >>
> >> The links to iotdb 0.8.0 mirrors are ok.
> >> But the links to ASC and SHA512 must be direct links to
> >> https://www.apache.org/dist/incubator/iotdb/... and not to
> mirrors.
> >>
> >> Could someone take care of that?
> >> Then I can resubmit the announce mail :)
> >>
> >> Thanks!
> >> Julian
> >>
> >> Von meinem Mobiltelefon gesendet
> >>
> >
>
>
>
>
>
>
>


Re: Homepage fix

2019-08-21 Thread Julian Feinauer
Just a short addition:
I copied from the flink site the following statement (which should suffice), 
regarding the hash verification:


Verifying Hashes and Signatures

Along with our releases, we also provide sha512 hashes in *.sha512 files and 
cryptographic signatures in *.asc files. The Apache Software Foundation has an 
extensive tutorial to verify hashes and signatures which you can follow by 
using any of these release-signing KEYS.

Am 21.08.19, 18:22 schrieb "Julian Feinauer" :

Hey,

I got some further requests to fix which we should address before the 
announce goes out...
It would be good if someone could help with the fixes

===
The download page must only use https://www.apache.org/dist/... for the
KEYS, hashes and sigs.
The source and binary artifacts must only use the mirror system, not
/dist/...

The public download page must not link directly to the source code in
GitHub, as that has not been formally released.
Such links should be restricted to pages intended for developers.

The same considerations apply to the News section.

The download page needs say that downloaders should verify releases, and
describe how to do so using KEYS + sig, or hash.
===

Thanks!
Julian

Am 21.08.19, 15:28 schrieb "Julian Feinauer" :

Hi,

thanks fort he fast fix, I already resend the ANNOUNCE mail.. so 
hopefully it comes through soon __

Julian

Am 21.08.19, 12:59 schrieb "Xiangdong Huang" :

Hi,

As something is wrong in jenkins server, I have manually deployed 
the
latest website.

Now http://iotdb.apache.org/#/Download has correct urls.

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Xiangdong Huang  于2019年8月21日周三 下午6:34写道:

> Hi,
>
> I fixed it. Please review PR
> https://github.com/apache/incubator-iotdb-website/pull/30
> Or I will merge it a short time later.
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
    > 清华大学 软件学院
>
>
> Julian Feinauer  于2019年8月21日周三 
下午6:10写道:
>
>> Hi,
>>
>> Just got a mail from the announce guys that we need a fix on our 
download
>> section :
>>
>> The links to iotdb 0.8.0 mirrors are ok.
>> But the links to ASC and SHA512 must be direct links to
>> https://www.apache.org/dist/incubator/iotdb/... and not to 
mirrors.
>>
>> Could someone take care of that?
>> Then I can resubmit the announce mail :)
>>
>> Thanks!
>> Julian
>>
>> Von meinem Mobiltelefon gesendet
>>
>








Re: Homepage fix

2019-08-21 Thread Julian Feinauer
Hey,

I got some further requests to fix which we should address before the announce 
goes out...
It would be good if someone could help with the fixes

===
The download page must only use https://www.apache.org/dist/... for the
KEYS, hashes and sigs.
The source and binary artifacts must only use the mirror system, not
/dist/...

The public download page must not link directly to the source code in
GitHub, as that has not been formally released.
Such links should be restricted to pages intended for developers.

The same considerations apply to the News section.

The download page needs say that downloaders should verify releases, and
describe how to do so using KEYS + sig, or hash.
===

Thanks!
Julian

Am 21.08.19, 15:28 schrieb "Julian Feinauer" :

Hi,

thanks fort he fast fix, I already resend the ANNOUNCE mail.. so hopefully 
it comes through soon __

Julian

Am 21.08.19, 12:59 schrieb "Xiangdong Huang" :

Hi,

As something is wrong in jenkins server, I have manually deployed the
latest website.

Now http://iotdb.apache.org/#/Download has correct urls.

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Xiangdong Huang  于2019年8月21日周三 下午6:34写道:

> Hi,
>
> I fixed it. Please review PR
> https://github.com/apache/incubator-iotdb-website/pull/30
> Or I will merge it a short time later.
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
    > 清华大学 软件学院
>
>
> Julian Feinauer  于2019年8月21日周三 下午6:10写道:
>
>> Hi,
>>
>> Just got a mail from the announce guys that we need a fix on our 
download
>> section :
>>
>> The links to iotdb 0.8.0 mirrors are ok.
>> But the links to ASC and SHA512 must be direct links to
>> https://www.apache.org/dist/incubator/iotdb/... and not to mirrors.
>>
>> Could someone take care of that?
>> Then I can resubmit the announce mail :)
>>
>> Thanks!
>> Julian
>>
>> Von meinem Mobiltelefon gesendet
>>
>






FW: Showcase your project at ApacheCON at a Podling's Shark Tank

2019-08-21 Thread Julian Feinauer
Yay, we are in both Cons : )

Julian

Am 20.08.19, 23:47 schrieb "Roman Shaposhnik" :

Hi All!

thanks a million for this tremendous interest in Podling's Shark Tank.

We now have:

ApacheCON NA in Las Vegas:
Daffodil
ShardingSphere
Heron
DLab
IoTDB
Daffodil
Ratis
DataSketches

ApacheCON EU in Berlin:
 MorphL
 ShardingSphere
 DLab
 IoTDB
 Tuweni

We now have full schedule of podlings for both events and I will
be following up with individuals (and individual communities) who
volunteered for both.

Thanks,
Roman.

On Wed, Aug 14, 2019 at 1:45 PM Roman Shaposhnik  wrote:
>
> Hi Podlings!
>
> in less than a month we're going to have our first
> ApacheCON this year -- the one in Las Vegas. In
> about two month there will be one more in Berlin.
>
> These are not your regular ApacheCONs -- these are
> 20th Anniversary of ASF ApacehCONs! In other words,
> these are not to be missed!
>
> And even if your talk didn't get accepted -- you still
> get an opportunity to highlight your project to, what's
> likely going to be the biggest audience attending.
>
> Here's how: if you (or any community member who's
> passionate about your project) are going to be at either
> of those ApacheCONs consider signing up for
> Podling's Shark Tank
> events:
> https://www.apachecon.com/acna19/s/#/scheduledEvent/1038
> https://aceu19.apachecon.com/session/podlings-shark-tank
>
> Each project presenting will get ~10 min for the pitch and ~5 min
> of panel grilling them on all sorts of things. Kind of like this ;-)
>  https://www.youtube.com/watch?v=wmenN7NEdBc
>
> You've got nothing to lose (in fact, the opposite: you're likely to get
> a prize!) and you will get a chance to receive feedback that might
> actually help you grow your community and ultimately graduate to the
> TLP status. And! Given our awesome panel of judges:
>  * Myrle Krantz
>  * Justin Mclean
>  * Craig Russel
>  * Shane Curcuru
> We guarantee this to be a fun and useful event for your community!
>
> We will be tracking signups over here:
>  https://wiki.apache.org/apachecon/ACNA19PodlingSharkTank
>  https://wiki.apache.org/apachecon/ACEU19PodlingSharkTank
> but for now:
>
> SIMPLY REPLY TO THIS EMAIL if you're interested.




Re: [Discuss] how to organize PRs (for fixing bugs) to the next version or v0.8.1?

2019-08-21 Thread Julian Feinauer
Hi,

I agree with Willem.
PRs should generally go to master (develop, see discussion below).

If we discuss that one Patch is so important that we want to create a "hotfix" 
release than we will pick it to the "rel/0.8" branch and do a new release there 
(tagget then 'release/0.8.1' for example).
But I think in this case its better to first start the discussion for a release 
before starting to cherry-pick or something.

Julian

Am 21.08.19, 11:00 schrieb "Willem Jiang" :

If you want to provide patch release,  you need to create a branch
0.8.x once you cut the 0.8.0.
For the bug fix, you need to commit the change to master branch and
then back port it from master to 0.8.x.
My suggestion is you just send PR to master and then do the cherry
pick in your local 0.8.x branch and then send a PR to 0.8.x branch.

As JIRA support multiple versions, you need to update the fix version
once the PR is merged into different branch.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Wed, Aug 21, 2019 at 4:50 PM Xiangdong Huang  wrote:
>
> Hi,
>
>  v0.8.0 is released, and the IoTDB project is keeping developing.
>
> I think it is no dispute that putting new features into v0.9.0 or other
> future version.
>
> The question is, do we have plan to release bug-fix versions, i.e., 
v0.8.1,
> v0.8.2, etc.. And if so, which branch should the related PR be merged
> (rel/0.8?)
>
> For example, PR#347 (thank Lei Rui catching it) is a critical bug for a
> database (in my opinion). So, do we need to release a bug-fixed version on
> v0.8.0 (e.g., after fixing 10 bugs, we can release a minor version).
>
> By the way, as we have released versions now, please record iotdb's 
version
> when you record issues on JIRA, and add the solved versions when the issue
> is closed.
>
> Best,
>
>
>
>
> --
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院




Re: Homepage fix

2019-08-21 Thread Julian Feinauer
Hi,

thanks fort he fast fix, I already resend the ANNOUNCE mail.. so hopefully it 
comes through soon __

Julian

Am 21.08.19, 12:59 schrieb "Xiangdong Huang" :

Hi,

As something is wrong in jenkins server, I have manually deployed the
latest website.

Now http://iotdb.apache.org/#/Download has correct urls.

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Xiangdong Huang  于2019年8月21日周三 下午6:34写道:

> Hi,
>
> I fixed it. Please review PR
> https://github.com/apache/incubator-iotdb-website/pull/30
> Or I will merge it a short time later.
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
    >  黄向东
    > 清华大学 软件学院
>
>
> Julian Feinauer  于2019年8月21日周三 下午6:10写道:
>
>> Hi,
>>
>> Just got a mail from the announce guys that we need a fix on our download
>> section :
>>
>> The links to iotdb 0.8.0 mirrors are ok.
>> But the links to ASC and SHA512 must be direct links to
>> https://www.apache.org/dist/incubator/iotdb/... and not to mirrors.
>>
>> Could someone take care of that?
>> Then I can resubmit the announce mail :)
>>
>> Thanks!
>> Julian
>>
>> Von meinem Mobiltelefon gesendet
>>
>




Re: [DISCUSS] Any idea for the Apache IoTDB talk on Apache Con NA 2019?

2019-08-21 Thread Julian Feinauer
Hi,

xiangdong, I will of course help with the preparation (so it would be kind to 
add my email if not already done).
I think the most important thing for us is to show others what iotdb is and 
what to use it for.
I think we don’t have to go into the technical details that much (but should 
perhaps show how it relates to parquet and others).

Julian

Von: Xiangdong Huang 
Datum: Mittwoch, 21. August 2019 um 15:20
An: "dev@iotdb.apache.org" , Julian Feinauer 
, 乔嘉林 <646274...@qq.com>, 刘睿 <245422...@qq.com>, 
"qingxin.f...@hotmail.com" , "xingtan...@apache.org" 

Betreff: Re: [DISCUSS] Any idea for the Apache IoTDB talk on Apache Con NA 2019?

Hi,

And if someone wants to edit the file, please contact me and leave your email, 
I will add you as a cooperator.

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Xiangdong Huang mailto:saint...@gmail.com>> 于2019年8月21日周三 
下午9:17写道:
Hi all,

The apache con is coming in several days..

As I know, Julian, Jinrui Zhang and me will attend the conference (em... and I 
think all mentors will also attend :D).

I have created a Google Slides file for the talk. see:

https://docs.google.com/presentation/d/1EXi4UY1IXaAKW1Ybh3iLzgkKQIvA5B--7oL_rQ8aG0Y/edit?usp=sharing

Now, only the outline is added. (Though I have finished some chapters, I want 
to hear more advices before I publish them into the file).

1. do not hesitate to propose your idea, just tell me what  that should be 
introduced on the talk in your opinion.

2. Now I only have the performance evaluation between IoTDB 0.7 with other time 
series databases. So I need the community's help. It would be better if someone 
is interested to testing the performance of IoTDB.

(And, @Rui Liu and Qingxin Feng, I may need your help.)

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Homepage fix

2019-08-21 Thread Julian Feinauer
Hi,

Just got a mail from the announce guys that we need a fix on our download 
section :

The links to iotdb 0.8.0 mirrors are ok.
But the links to ASC and SHA512 must be direct links to 
https://www.apache.org/dist/incubator/iotdb/... and not to mirrors.

Could someone take care of that?
Then I can resubmit the announce mail :)

Thanks!
Julian

Von meinem Mobiltelefon gesendet


AW: Release 0.8.0 is finished

2019-08-20 Thread Julian Feinauer
Hey Kevin,

Then I hope even more to see you at apache con :D

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: Release 0.8.0 is finished
Von: "Kevin A. McGrail"
An: dev@iotdb.apache.org,Julian Feinauer
Cc:

Drinks are on me for the IoTDB team the next time we can all meet!

On 8/20/2019 3:11 AM, Julian Feinauer wrote:
> Hi Folks,
>
>
>
> I just sent out the official ANNOUNCE mail (see below) which will (hopefully) 
> soon appear on all official ASF channels (announce@ list, twitter, homepage, 
> …).
>
> This was the last step of the release process and I once again want to thank 
> everybody for participating and contributing to this release.
>
> Thanks also once again to our mentors who did an excellent job (there are not 
> that many projects who reach 3 +1 IPMC Votes on their PPMC Vote) with helping 
> to harden the release.
>
>
>
> It may seem a bit cumbersome and a bit bureaucratic how the ASF handles 
> releases but over time you will understand the process, go through with ease 
> and understand how this process helps us to provide high quality software 
> with full legal protection for developers and users.
>
>
>
> So I hope it didn’t scare you too much and we will find a different RM from 
> the community for the next release : )
>
>
>
> Julian
>
>
>
> --
>
>
>
> The Apache IoTDB (Incubating) team is pleased to announce the release of 
> Apache IoTDB (incubating) 0.8.0.
>
>
>
> This is the first official Apache release of IoTDB.
>
>
>
> Apache IoTDB (incubating) (Database for Internet of Things) is an integrated 
> data management engine
>
> designed for timeseries data. It provides users with services for data 
> collection, storage and analysis.
>
>
> The main features are
>
>
>
> * High-throughput read and write
>
> * Efficient directory structure
>
> * Handling of out-of-order records
>
> * Rich query semantics
>
> * Low cost on hardware
>
> * Flexible deployment
>
> * Intense integration with Open Source Ecosystem
>
>
>
> Examples of existing integrations are
>
>
>
> * Apache Hadoop
>
> * Apache Spark
>
> * Grafana
>
>
>
> Visit the Apache IoTDB website [1] for general information or
>
> the downloads page [2] for release notes and download information.
>
>
>
> Regards,
>
> The Apache IoTDB team
>
>
>
> [1] https://iotdb.apache.org/
>
> [2] https://iotdb.apache.org/#/Download
>
>
>
> =
>
>
>
> *Disclaimer*
>
>
>
> Apache IoTDB is an effort undergoing incubation at The Apache Software
>
> Foundation (ASF), sponsored by the name of Apache Incubator PMC. Incubation
>
> is required of all newly accepted projects until a further review indicates
>
> that the infrastructure, communications, and decision making process have
>
> stabilized in a manner consistent with other successful ASF projects. While
>
> incubation status is not necessarily a reflection of the completeness or
>
> stability of the code, it does indicate that the project has yet to be
>
> fully endorsed by the ASF.
>

--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171



Re: Release 0.8.0 is finished

2019-08-20 Thread Julian Feinauer
Hi Chris,

the tooling is already there in a branch (which I reference in my instructions 
on Confluence)... but yeah... __

Julian

Am 20.08.19, 09:36 schrieb "Christofer Dutz" :

Hi Julian and the rest of the IoTDB

Congratulations on this :-)

As usual, the first "cut is the deepest" ... but I guess all the 
preparation work you guys did will help ease the path of future releases. 
And as you seem to have addressed all (or at least most) concerns I think 
the next releases will be a lot easier.

Perhaps you should think of adding some tooling as we have it in Edgent and 
PLC4X (Which was "borrowed" from Edgent) that automates 
Downloading of RCs, checking the signatures and hashes. 

Keep up the good work :-)

Chris

    Am 20.08.19, 09:11 schrieb "Julian Feinauer" :

Hi Folks,



I just sent out the official ANNOUNCE mail (see below) which will 
(hopefully) soon appear on all official ASF channels (announce@ list, twitter, 
homepage, …).

This was the last step of the release process and I once again want to 
thank everybody for participating and contributing to this release.

Thanks also once again to our mentors who did an excellent job (there 
are not that many projects who reach 3 +1 IPMC Votes on their PPMC Vote) with 
helping to harden the release.



It may seem a bit cumbersome and a bit bureaucratic how the ASF handles 
releases but over time you will understand the process, go through with ease 
and understand how this process helps us to provide high quality software with 
full legal protection for developers and users.



So I hope it didn’t scare you too much and we will find a different RM 
from the community for the next release : )



Julian



--



The Apache IoTDB (Incubating) team is pleased to announce the release 
of Apache IoTDB (incubating) 0.8.0.



This is the first official Apache release of IoTDB.



Apache IoTDB (incubating) (Database for Internet of Things) is an 
integrated data management engine

designed for timeseries data. It provides users with services for data 
collection, storage and analysis.


The main features are



* High-throughput read and write

* Efficient directory structure

* Handling of out-of-order records

* Rich query semantics

* Low cost on hardware

* Flexible deployment

* Intense integration with Open Source Ecosystem



Examples of existing integrations are



* Apache Hadoop

* Apache Spark

* Grafana



Visit the Apache IoTDB website [1] for general information or

the downloads page [2] for release notes and download information.



Regards,

The Apache IoTDB team



[1] https://iotdb.apache.org/

[2] https://iotdb.apache.org/#/Download



=



*Disclaimer*



Apache IoTDB is an effort undergoing incubation at The Apache Software

Foundation (ASF), sponsored by the name of Apache Incubator PMC. 
Incubation

is required of all newly accepted projects until a further review 
indicates

that the infrastructure, communications, and decision making process 
have

stabilized in a manner consistent with other successful ASF projects. 
While

incubation status is not necessarily a reflection of the completeness or

stability of the code, it does indicate that the project has yet to be

fully endorsed by the ASF.







Release 0.8.0 is finished

2019-08-20 Thread Julian Feinauer
Hi Folks,



I just sent out the official ANNOUNCE mail (see below) which will (hopefully) 
soon appear on all official ASF channels (announce@ list, twitter, homepage, …).

This was the last step of the release process and I once again want to thank 
everybody for participating and contributing to this release.

Thanks also once again to our mentors who did an excellent job (there are not 
that many projects who reach 3 +1 IPMC Votes on their PPMC Vote) with helping 
to harden the release.



It may seem a bit cumbersome and a bit bureaucratic how the ASF handles 
releases but over time you will understand the process, go through with ease 
and understand how this process helps us to provide high quality software with 
full legal protection for developers and users.



So I hope it didn’t scare you too much and we will find a different RM from the 
community for the next release : )



Julian



--



The Apache IoTDB (Incubating) team is pleased to announce the release of Apache 
IoTDB (incubating) 0.8.0.



This is the first official Apache release of IoTDB.



Apache IoTDB (incubating) (Database for Internet of Things) is an integrated 
data management engine

designed for timeseries data. It provides users with services for data 
collection, storage and analysis.


The main features are



* High-throughput read and write

* Efficient directory structure

* Handling of out-of-order records

* Rich query semantics

* Low cost on hardware

* Flexible deployment

* Intense integration with Open Source Ecosystem



Examples of existing integrations are



* Apache Hadoop

* Apache Spark

* Grafana



Visit the Apache IoTDB website [1] for general information or

the downloads page [2] for release notes and download information.



Regards,

The Apache IoTDB team



[1] https://iotdb.apache.org/

[2] https://iotdb.apache.org/#/Download



=



*Disclaimer*



Apache IoTDB is an effort undergoing incubation at The Apache Software

Foundation (ASF), sponsored by the name of Apache Incubator PMC. Incubation

is required of all newly accepted projects until a further review indicates

that the infrastructure, communications, and decision making process have

stabilized in a manner consistent with other successful ASF projects. While

incubation status is not necessarily a reflection of the completeness or

stability of the code, it does indicate that the project has yet to be

fully endorsed by the ASF.



Download section

2019-08-19 Thread Julian Feinauer
Hi all,

I just observed that most mirrors seem to be synced so the download section 
already works for me.
I'll send the official announce out tomorrow in the morning (utc+2).

Once again thanks to Zesong and of course to all others who made this release 
possible!

Julian

Von meinem Mobiltelefon gesendet


Re: [RESULT][VOTE] Release Apache IoTDB (Incubating) 0.8.0 RC3

2019-08-19 Thread Julian Feinauer
Hi,

short update, both releases (svn and maven) are done.
The source release can be found under:
https://dist.apache.org/repos/dist/release/incubator/iotdb/0.8.0-incubating/

Notice that we do not use above link to distribute the artefacts but use the 
mirror links (most likely 
https://archive.apache.org/dist/incubator/iotdb/0.8.0-incubating/ but currently 
not yet reachable).

The maven central artefacts should be available in some minutes.

Furthermore, I discuss to rename the current `master` to develop and point the 
`master` branch then to the tagged release version (as already discussed 
several times).
Does everybody agree with that?

Julian


Am 19.08.19, 08:24 schrieb "Julian Feinauer" :

Hi,

haha, you were faster than me... I wanted to write a short "next steps" 
mail here.
The RM (me) does two things next.
First, release the maven artefacts (they will be available in 10 minutes on 
central) and second, move the artefacts in svn from the 'dev' folder to the 
'prod' folder, that’s it.
This gives us then the link to incorporate in the homepage.
The link might not be work from the first second, as not all mirrors are 
synced (see below).

Then, after 24hrs all the artefacts from 'prod' are synced to all mirrors 
of apache worldwide and then we send out the announce email via 
annou...@apache.org where we point to our download section.

That’s it : )

Julian

Am 19.08.19, 08:18 schrieb "Xiangdong Huang" :

Hi,

Great! So, what is the next step?

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院
    
    
Julian Feinauer  于2019年8月19日周一 下午2:13写道:

> Hello all,
>
> the vote to release Apache IoTDB (incubating) 0.8.0 RC3 has passed 
with 4
> +1 Votes.
> Binding Votes:
>
> Justin McLean
> Christofer Dutz
> Kevin A. McGrail
> Julian Feinauer
>
> No further Votes were cast.
>
> Vote thread:
>
> 
https://lists.apache.org/thread.html/3f4c312056f618450a0e947fe212a65deee5006a75ec6331c01aece3@%3Cgeneral.incubator.apache.org%3E
>
> As this is the first Apache Release of IoTDB a big ‘thank you’ to
> everybody who supported us in doing the release, this is a big 
milestone
> for a young podling!
>
> We will proceed with publishing the approved artefacts and send out 
the
> ANNOUNCE when everythink is ready and synced.
>
> On behalf of the Apache IoTDB Community,
> Julian
>






Re: [RESULT][VOTE] Release Apache IoTDB (Incubating) 0.8.0 RC3

2019-08-19 Thread Julian Feinauer
Hi,

haha, you were faster than me... I wanted to write a short "next steps" mail 
here.
The RM (me) does two things next.
First, release the maven artefacts (they will be available in 10 minutes on 
central) and second, move the artefacts in svn from the 'dev' folder to the 
'prod' folder, that’s it.
This gives us then the link to incorporate in the homepage.
The link might not be work from the first second, as not all mirrors are synced 
(see below).

Then, after 24hrs all the artefacts from 'prod' are synced to all mirrors of 
apache worldwide and then we send out the announce email via 
annou...@apache.org where we point to our download section.

That’s it : )

Julian

Am 19.08.19, 08:18 schrieb "Xiangdong Huang" :

Hi,

Great! So, what is the next step?

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院
    

Julian Feinauer  于2019年8月19日周一 下午2:13写道:

> Hello all,
>
> the vote to release Apache IoTDB (incubating) 0.8.0 RC3 has passed with 4
> +1 Votes.
> Binding Votes:
>
> Justin McLean
> Christofer Dutz
> Kevin A. McGrail
> Julian Feinauer
>
> No further Votes were cast.
>
> Vote thread:
>
> 
https://lists.apache.org/thread.html/3f4c312056f618450a0e947fe212a65deee5006a75ec6331c01aece3@%3Cgeneral.incubator.apache.org%3E
>
> As this is the first Apache Release of IoTDB a big ‘thank you’ to
> everybody who supported us in doing the release, this is a big milestone
> for a young podling!
>
> We will proceed with publishing the approved artefacts and send out the
> ANNOUNCE when everythink is ready and synced.
>
> On behalf of the Apache IoTDB Community,
> Julian
>




Re: [jira] [Created] (IOTDB-167) v0.9.0 roadmap

2019-08-19 Thread Julian Feinauer
Hi Xiangdong,

thanks for bringing that up.
Your suggestion contains multiple interesting topics.

As I'm active in Calcite I love Query Optimization.
What are the communities thoughts about that?
What do you plan to do or to enable?

Julian

Am 19.08.19, 05:10 schrieb "xiangdong Huang (JIRA)" :

xiangdong Huang created IOTDB-167:
-

 Summary: v0.9.0 roadmap
 Key: IOTDB-167
 URL: https://issues.apache.org/jira/browse/IOTDB-167
 Project: Apache IoTDB
  Issue Type: Task
Reporter: xiangdong Huang


The v0.9.0 can have the following function:
 # the merge of sequence files and unsequence files;
 # the sync module
 # the hadoop module
 # query optimization
 # define some subexceptions when executing SQL failed.

Please add your suggestion in this thread.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)




[RESULT][VOTE] Release Apache IoTDB (Incubating) 0.8.0 RC3

2019-08-19 Thread Julian Feinauer
Hello all,

the vote to release Apache IoTDB (incubating) 0.8.0 RC3 has passed with 4 +1 
Votes.
Binding Votes:

Justin McLean
Christofer Dutz
Kevin A. McGrail
Julian Feinauer

No further Votes were cast.

Vote thread:
https://lists.apache.org/thread.html/3f4c312056f618450a0e947fe212a65deee5006a75ec6331c01aece3@%3Cgeneral.incubator.apache.org%3E

As this is the first Apache Release of IoTDB a big ‘thank you’ to everybody who 
supported us in doing the release, this is a big milestone for a young podling!

We will proceed with publishing the approved artefacts and send out the 
ANNOUNCE when everythink is ready and synced.

On behalf of the Apache IoTDB Community,
Julian


Download section and getting started

2019-08-17 Thread Julian Feinauer
Hi all,

As the release is accepted and will be be finished soon we should prepare a 
download section and a getting started on the homepage before we send the 
official announce via all apache channels

Could someone take care of that as I do not understand the homepage code that 
well :/

Julian

Von meinem Mobiltelefon gesendet


WG: Showcase your project at ApacheCON at a Podling's Shark Tank

2019-08-14 Thread Julian Feinauer
Wer should definitely participate here!

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Showcase your project at ApacheCON at a Podling's Shark Tank
Von: Roman Shaposhnik
An: general ,Roman Shaposhnik
Cc:

Hi Podlings!

in less than a month we're going to have our first
ApacheCON this year -- the one in Las Vegas. In
about two month there will be one more in Berlin.

These are not your regular ApacheCONs -- these are
20th Anniversary of ASF ApacehCONs! In other words,
these are not to be missed!

And even if your talk didn't get accepted -- you still
get an opportunity to highlight your project to, what's
likely going to be the biggest audience attending.

Here's how: if you (or any community member who's
passionate about your project) are going to be at either
of those ApacheCONs consider signing up for
Podling's Shark Tank
events:
https://www.apachecon.com/acna19/s/#/scheduledEvent/1038
https://aceu19.apachecon.com/session/podlings-shark-tank

Each project presenting will get ~10 min for the pitch and ~5 min
of panel grilling them on all sorts of things. Kind of like this ;-)
 https://www.youtube.com/watch?v=wmenN7NEdBc

You've got nothing to lose (in fact, the opposite: you're likely to get
a prize!) and you will get a chance to receive feedback that might
actually help you grow your community and ultimately graduate to the
TLP status. And! Given our awesome panel of judges:
 * Myrle Krantz
 * Justin Mclean
 * Craig Russel
 * Shane Curcuru
We guarantee this to be a fun and useful event for your community!

We will be tracking signups over here:
 https://wiki.apache.org/apachecon/ACNA19PodlingSharkTank
 https://wiki.apache.org/apachecon/ACEU19PodlingSharkTank
but for now:

SIMPLY REPLY TO THIS EMAIL if you're interested.

It is first come, first serve -- so don't delay -- sign up today!

Thanks,
Roman.


Re: An easier way to create time series.

2019-08-14 Thread Julian Feinauer
Hi,

agree.
This was more as a first comment I wanted to throw in : )
And with such BIG changes I totally agree that a DISCUSSION Thread has to be 
openend and in the end if no consensus is found even a VOTE should be done.

Julian

Am 14.08.19, 12:18 schrieb "Tian Jiang" :

Hi Julian,


Surely naming is important to users, but different users may have different 
opinions upon naming. I think it is hard to get everyone satisfied, so maybe we 
can hold a vote or something to discuss that later.


My starting point is to provide a way to create a bunch of time series with 
fewer statements(as the title suggests) and this will not interfere with 
existing functionality. It is light-weight, and I can add this feature within a 
day or two.


Adding tags is cool, which can definitely enhance the expressive power of 
IoTDB, But, the implementation may cause a lot of changes(and potential 
troubles) in the whole system, which is beyond the discussion. Since you seem 
interested, we may open another thread to discuss about the tags(or whatever 
you want to call it) in detail.


Tian Jiang



At 2019-08-14 17:12:41, "Julian Feinauer"  
wrote:
>Hi Tian,
>
>naming i see as a minor issue to change but as a bigger issue to users 
(nomen est omen...).
>Regarding your other comment I don’t get what you mean.
>
>Think of situations like monitoring stuff from several machines of 
multiple types in multiple plants.
>Then I would like to say something like
>
>"do that for all series in plan A" or "in all series for machine Type X".
>
>Indeed its quite a "huge" change which has implications but it would 
rather "widen" the api to do "multi-series querying" rather than change it, I 
guess?
>
>Julian
>
>Am 14.08.19, 11:06 schrieb "Tian Jiang" :
>
>The naming is not a big issue, but your schema proposals seem to be 
turning IoTDB into something else.
>
>
>
>
>
>At 2019-08-14 16:55:33, "Jialin Qiao"  
wrote:
>>Hi,
>>
>>I think source or datasource is good, and it's better to use, or at 
least add the tags and fields, because many TSDBs use these conceptual module.
>>
>>Some feasible schema organization ways and "select * from the table" 
results:
>>
>>(1) Each type of datasource is a table, which has a time column, some 
tag columns and some field columns.
>>
>>Table: sourceType
>>time tag1,  field1, field2
>>1, device1, 1, 1
>>2, device1, 2, 2
>>2, device2, 2, 2
>>
>>(2) Each datasource is a table with some tags. Each table has a time 
column, and some field columns. (Tags of one datasource may be not changed, so 
just see it as metadata.)
>>
>>Table: source1(tag1=device1)
>>time, field1, field2
>>1, 1, 1
>>2, 2, 2
>>
>>Table: source2(tag1=device2)
>>time, field1, field2
>>2, 2, 2
>>
>>
>>Best,
>>--
>>Jialin Qiao
>>School of Software, Tsinghua University
>>
>>乔嘉林
>>清华大学 软件学院
>>
>>> -原始邮件-
>>> 发件人: "Julian Feinauer" 
>>> 发送时间: 2019-08-14 16:10:22 (星期三)
>>> 收件人: "dev@iotdb.apache.org" 
>>> 抄送: 
>>> 主题: Re: An easier way to create time series.
>>> 
>>> Hi,
>>> 
>>> let me stick in hier also.
>>> One of the things which was at first a bit "unfamiliar" for me was 
this device focus.
>>> It’s a bit to "one-dimensional" in my perspective.
>>> 
>>> Personally, I quite like how Influx does it that you have a name 
and can attach tags and fields to it.
>>> And even if we do not do it that way I would prefer to name it a 
bit differently as "series" or "measurement" or "source".
>>> Device is a bit specific and just sounds odd, from a users 
perspective.
>>> 
>>> I think it was good to keep it that way for 0.8.0.
>>> But for the next release we are open to break things a bit.
>>> 
>>> What do others think?
>>> 
>>> Julian
>>> 
>>&g

Re: An easier way to create time series.

2019-08-14 Thread Julian Feinauer
Hi Tian,

naming i see as a minor issue to change but as a bigger issue to users (nomen 
est omen...).
Regarding your other comment I don’t get what you mean.

Think of situations like monitoring stuff from several machines of multiple 
types in multiple plants.
Then I would like to say something like

"do that for all series in plan A" or "in all series for machine Type X".

Indeed its quite a "huge" change which has implications but it would rather 
"widen" the api to do "multi-series querying" rather than change it, I guess?

Julian

Am 14.08.19, 11:06 schrieb "Tian Jiang" :

The naming is not a big issue, but your schema proposals seem to be turning 
IoTDB into something else.





At 2019-08-14 16:55:33, "Jialin Qiao"  wrote:
>Hi,
>
>I think source or datasource is good, and it's better to use, or at least 
add the tags and fields, because many TSDBs use these conceptual module.
>
>Some feasible schema organization ways and "select * from the table" 
results:
>
>(1) Each type of datasource is a table, which has a time column, some tag 
columns and some field columns.
>
>Table: sourceType
>time tag1,  field1, field2
>1, device1, 1, 1
>2, device1, 2, 2
>2, device2, 2, 2
>
>(2) Each datasource is a table with some tags. Each table has a time 
column, and some field columns. (Tags of one datasource may be not changed, so 
just see it as metadata.)
>
>Table: source1(tag1=device1)
>time, field1, field2
>1, 1, 1
>2, 2, 2
>
>Table: source2(tag1=device2)
>time, field1, field2
>2, 2, 2
>
    >
    >Best,
>--
>Jialin Qiao
>School of Software, Tsinghua University
>
>乔嘉林
>清华大学 软件学院
>
>> -原始邮件-
>> 发件人: "Julian Feinauer" 
>> 发送时间: 2019-08-14 16:10:22 (星期三)
>> 收件人: "dev@iotdb.apache.org" 
>> 抄送: 
>> 主题: Re: An easier way to create time series.
>> 
>> Hi,
>> 
>> let me stick in hier also.
>> One of the things which was at first a bit "unfamiliar" for me was this 
device focus.
>> It’s a bit to "one-dimensional" in my perspective.
>> 
>> Personally, I quite like how Influx does it that you have a name and can 
attach tags and fields to it.
>> And even if we do not do it that way I would prefer to name it a bit 
differently as "series" or "measurement" or "source".
>> Device is a bit specific and just sounds odd, from a users perspective.
>> 
>> I think it was good to keep it that way for 0.8.0.
>> But for the next release we are open to break things a bit.
>> 
>> What do others think?
>> 
>> Julian
>> 
>> Am 14.08.19, 04:52 schrieb "Tian Jiang" :
>> 
>> Maybe starting from a sugar, we can add some improvements gradually. 
Currently, I think making timeseries creation easier should be enough. Please 
share if you have some fancy ideas that can go with the introduction of 
"device".
>> 
>> Tian Jiang
>> 
>> 
>> At 2019-08-14 10:44:14, "Xiangdong Huang"  wrote:
>> >Hi,
>> >
>> >Looks fine for me.
>> >
>> >One question, is it just a language syntax sugar, or we can as well 
as
>> >improve the schema management? Any idea?
>> >
>> >Best,
>> >---
>> >Xiangdong Huang
>> >School of Software, Tsinghua University
>> >
>> > 黄向东
>> >清华大学 软件学院
>> >
>> >
>> >Tian Jiang  于2019年8月14日周三 上午10:37写道:
>> >
>> >> Greetings,
>> >>
>> >>
>> >> In the present version, it is a little trouble some to create a 
set
>> >> timeseries that has the same measurements. On the other hand, 
although we
>> >> use the conception "device" in the code, it is not properly 
abstracted.
>> >>
>> >> Expected usage:
>> >>
>> >> Using IoTDB in a more relational way:
>> >>
>> >> CREATE DEVICE TEMPLATE vehicle (speed DOUBLE PLAIN, direction 
DOUBLE
>> >> PLAIN, temperature DOUB

Re: An easier way to create time series.

2019-08-14 Thread Julian Feinauer
Hi,

let me stick in hier also.
One of the things which was at first a bit "unfamiliar" for me was this device 
focus.
It’s a bit to "one-dimensional" in my perspective.

Personally, I quite like how Influx does it that you have a name and can attach 
tags and fields to it.
And even if we do not do it that way I would prefer to name it a bit 
differently as "series" or "measurement" or "source".
Device is a bit specific and just sounds odd, from a users perspective.

I think it was good to keep it that way for 0.8.0.
But for the next release we are open to break things a bit.

What do others think?

Julian

Am 14.08.19, 04:52 schrieb "Tian Jiang" :

Maybe starting from a sugar, we can add some improvements gradually. 
Currently, I think making timeseries creation easier should be enough. Please 
share if you have some fancy ideas that can go with the introduction of 
"device".

Tian Jiang


At 2019-08-14 10:44:14, "Xiangdong Huang"  wrote:
>Hi,
>
>Looks fine for me.
>
>One question, is it just a language syntax sugar, or we can as well as
>improve the schema management? Any idea?
>
>Best,
>---
>Xiangdong Huang
>School of Software, Tsinghua University
>
> 黄向东
>清华大学 软件学院
>
>
>Tian Jiang  于2019年8月14日周三 上午10:37写道:
>
>> Greetings,
>>
>>
>> In the present version, it is a little trouble some to create a set
>> timeseries that has the same measurements. On the other hand, although we
>> use the conception "device" in the code, it is not properly abstracted.
>>
>> Expected usage:
>>
>> Using IoTDB in a more relational way:
>>
>> CREATE DEVICE TEMPLATE vehicle (speed DOUBLE PLAIN, direction DOUBLE
>> PLAIN, temperature DOUBLE PLAIN, fuel DOUBLE PLAIN)
>>
>> If all datatypes(or encodings) are the same, you can write the equal 
form:
>>
>> CREATE DEVICE TEMPLATE vehicle MEASUREMENTS (speed, direction,
>> temperature, fuel) DATATYPE DOUBLE ENCODING PLAIN
>>
>> Then you will be able to create time series in an easier way:
>>
>> CREATE DEVICE (vehicle) root.sg1.vehicle1
>>
>> Which equals:
>>
>> CREATE TIMESERIES root.sg1.vehicle1.speed WITH
>> DATATYPE=DOUBLE,ENCODING=PLAIN
>>
>> CREATE TIMESERIES root.sg1.vehicle1.direction WITH
>> DATATYPE=DOUBLE,ENCODING=PLAIN
>>
>> CREATE TIMESERIES root.sg1.vehicle1.fuel WITH
>> DATATYPE=DOUBLE,ENCODING=PLAIN
>>
>> CREATE TIMESERIES root.sg1.vehicle1.temperature WITH
>> DATATYPE=DOUBLE,ENCODING=PLAIN
>>
>> I hope this will narrow the gap between using IoTDB and traditional
>> relation databases.
>> Jira link:
>> 
https://issues.apache.org/jira/projects/IOTDB/issues/IOTDB-163?filter=allopenissues
>>
>>
>> Tian Jiang




[LAZY][VOTE] Release Apache IoTDB (Incubating) 0.8.0 RC3

2019-08-13 Thread Julian Feinauer
Hello all,

This is a call for vote to release Apache IoTDB (Incubating) version 0.8.0, 
which is the first Apache Release for the IoTDB Project.

The Apache IoTDB community has voted on and approved a proposal to release
Apache IoTDB (Incubating) version 0.8.0.

We now kindly request the Incubator PMC members review and vote on this
incubator release.

Apache IoTDB (incubating) (Database for Internet of Things) is an integrated 
data management engine designed for timeseries data. It provides users with 
services for data collection, storage and analysis.

IoTDB community vote and result thread:
Result: 
https://lists.apache.org/thread.html/19c913987145a2dc0afced626131e084fc3b1ab7e1ca1dde07a5b977@%3Cdev.iotdb.apache.org%3E
Vote: 
https://lists.apache.org/thread.html/d1272646baf81a0d2d62308cfb7a6e4fc754e377a043068409b0b9ed@%3Cdev.iotdb.apache.org%3E

The release candidates (RC3):
https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.8.0/rc3

Git tag for the release (RC3):
https://github.com/apache/incubator-iotdb/releases/tag/release%2F0.8.0

Hash for the release tag:
2f4da03b05d1c063eaaca622c68de86abe35de22

Release Notes:
https://github.com/apache/incubator-iotdb/blob/2f4da03b05d1c063eaaca622c68de86abe35de22/RELEASE_NOTES.md

The artifacts have been signed with Key : C336E0143A553B89, which can be
found in the keys file:
https://dist.apache.org/repos/dist/dev/incubator/iotdb/KEYS

Look at here for how to verify this release candidate:
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release

The vote will be open for at least 72 hours.

From the PPMC Vote we cary over 4 binding IPMC Votes:

+1 from Justin McLean,
+1 from Christofer Dutz,
+1 from Kevin A. McGrail,
+1 from Julian Feinauer

Thus, I took the freedom to declare the Vote as Lazy as no futher positive 
votes are necessary and only a -1 Vote could cancel the vote.

Please vote accordingly:
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Julian
Apache IoTDB





[RESULT][VOTE] Apache IoTDB (Incubating) 0.8.0 RC3

2019-08-13 Thread Julian Feinauer
Hi all,

as announced the vote closes now.
The vote PASSES as we have 6 +1 votes from the PPMC, 4 +1 votes from IPMC 
members and no further 0 or -1 votes.

I will now bring the vote to 
gene...@incubator.apache.org to get 
approval by the IPMC.
If this Vote passes also, the release is accepted and will be published.

Thanks everybody for their help and a special thank to our mentors who all 
participated in the Vote!

Julian


Re: consider introduce error code in client-side

2019-08-13 Thread Julian Feinauer
Agreed, thats the best way how NOT to do it :D

Am 13.08.19, 10:15 schrieb "Xiangdong Huang" :

Hi,

Either is fine.

The only thing is that I want to get rid of checking the error message
content

Best,

---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


    Julian Feinauer  于2019年8月13日周二 下午4:12写道:

> Hi all,
>
> what one could also use is some "ResponseEnum" which could be hosted in an
> error code, perhaps?
> But, generally I agree with Tian.
>
> Julian
>
> Am 13.08.19, 10:07 schrieb "江天" :
>
> Well, I prefer to define new Exception classes over ugly error codes,
> which better utilize OOP.
>
> Tian Jiang
>
> > 在 2019年8月13日,下午4:00,Xiangdong Huang  写道:
> >
> > Hi,
> >
> > When using IoTDB-JDBC to operate data, I realize that it is not
> convenient
> > without  error codes 
> >
> > The typical application is register a new time series automatically
> if the
> > received data belongs to a not existed time series.. Now, I have to
> check
> > the error message to judge whether the keyword "exist" exists...
> >
> > I list 4 useful error codes according to my experience of using
> IoTDB, see
> > https://issues.apache.org/jira/browse/IOTDB-161
> >
> > It is an easy task comparing to other issues. Knowing how to use
> Thrift
> > will help to finish the feature.
> >
> > Best,
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> > 黄向东
> > 清华大学 软件学院
>
>
>
>
>




Re: consider introduce error code in client-side

2019-08-13 Thread Julian Feinauer
Hi all,

what one could also use is some "ResponseEnum" which could be hosted in an 
error code, perhaps?
But, generally I agree with Tian.

Julian

Am 13.08.19, 10:07 schrieb "江天" :

Well, I prefer to define new Exception classes over ugly error codes, which 
better utilize OOP. 

Tian Jiang

> 在 2019年8月13日,下午4:00,Xiangdong Huang  写道:
> 
> Hi,
> 
> When using IoTDB-JDBC to operate data, I realize that it is not convenient
> without  error codes 
> 
> The typical application is register a new time series automatically if the
> received data belongs to a not existed time series.. Now, I have to check
> the error message to judge whether the keyword "exist" exists...
> 
> I list 4 useful error codes according to my experience of using IoTDB, see
> https://issues.apache.org/jira/browse/IOTDB-161
> 
> It is an easy task comparing to other issues. Knowing how to use Thrift
> will help to finish the feature.
> 
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
> 
> 黄向东
> 清华大学 软件学院






Re: [REMINDER][VOTE] Apache IoTDB (Incubating) 0.8.0 RC3

2019-08-13 Thread Julian Feinauer
Thank you Willem, looking forward for your Vote : )

Am 13.08.19, 10:05 schrieb "Willem Jiang" :

Hi Julian,

Thanks for taking care of this.
I will take a look at the release kit later today.


Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Aug 13, 2019 at 3:55 PM Julian Feinauer
 wrote:
>
> Hi all,
>
> this is a short reminder for everybody in the iotdb community that we 
have a vote ongoing for our first Apache Release 0.8.0.
> This goes especially to all PPMCs.
>
> Please take on your duty and participate in the vote!
> We currently only have only 3 +1 PPMC votes.
>
> I would like to close the vote this evening (UTC+1) so in about 10 hours 
or so.
> But I would really like us to go over 5 PPMC votes.
>
> Best
> Julian




[REMINDER][VOTE] Apache IoTDB (Incubating) 0.8.0 RC3

2019-08-13 Thread Julian Feinauer
Hi all,

this is a short reminder for everybody in the iotdb community that we have a 
vote ongoing for our first Apache Release 0.8.0.
This goes especially to all PPMCs.

Please take on your duty and participate in the vote!
We currently only have only 3 +1 PPMC votes.

I would like to close the vote this evening (UTC+1) so in about 10 hours or so.
But I would really like us to go over 5 PPMC votes.

Best
Julian


Re: [DISCUSS] Apache IoTDB (Incubating) 0.8.0 RC3

2019-08-12 Thread Julian Feinauer
Thank you very much, Xiangdong.

I (and also chris and Justin I sometimes discuss with) see this as an important 
"exercise" as we want to help you as PPMC to stand on your own feet as soon as 
possible.
And codewise theres nothing you don’t know so we can only help with the ASF 
rules and procedures : )

Julian

Am 12.08.19, 16:56 schrieb "Xiangdong Huang" :

Hi,

Indeed there is few PPMC's votes...  I will try to contact them once again
:(.

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Kevin A. McGrail  于2019年8月12日周一 下午10:32写道:

> Please accept my vote +1 binding, them.  I have checked over the zip
> files, compiled the server and client but not run them.  Tere is the
> minor readme issue which I don't think is a hold up
> (https://github.com/apache/incubator-iotdb/pull/335)  Looking forward to
> this release.
>
> On 8/12/2019 10:27 AM, Julian Feinauer wrote:
> > Hi Xiangdong,
> >
> > I left the vote open for 2 reasons.
> > First, we currently have only 2 PPMC Votes.
> > Chris vote also counts as PPMC Vote so we could close the vote with 3 +1
> Votes (not 4, mine is not binding for PPMC).
> >
> > Second, we only have 2 binding IPMC Votes and I'd like to bring it to
> general@ with 3 IPMC Votes as I think it’s a good practice for Podlings.
> >
> > But, I suggest that some more PPMC members participate in the vote. Its
> not so good to pass votes only with mentor votes when there are enough
> people in the PPMC.
> > The PPMC currently has 20 members, so I personally would like to see at
> least 10 Votes from the PPMC but we could, of course also close it 
earlier.
> >
> > But I want at least 3 PPMC votes and 3 IPMC Votes before closing and
> this should be doable : )
> >
> > Julian
> >
> > Am 12.08.19, 15:58 schrieb "Xiangdong Huang" :
> >
> > Hi,
> >
> > If there is no more voters... how about ending the vote?  There are
> 4 +1
> > votes now.
> >
> > Best,
> > ---
> > Xiangdong Huang
> > School of Software, Tsinghua University
> >
> >  黄向东
> > 清华大学 软件学院
> >
> >
> > Julian Feinauer  于2019年8月10日周六
> 下午4:04写道:
> >
> > > Hi,
> > >
> > > One more from my side... We should not focus on the binaries in
> the Readme.
> > > 8 think it's better to prepare a nice download and getting started
> site
> > > where we explain.
> > > There we can focus on binaries, that's fine.
> > >
> > > And downdload site we need after all before sending out an
> announce (after
> > > IPMC vote finished successfully).
> > >
> > > Julian
> > >
> > > Von meinem Mobiltelefon gesendet
> > >
> > >
> > >  Ursprüngliche Nachricht 
> > > Betreff: Re: [DISCUSS] Apache IoTDB (Incubating) 0.8.0 RC3
> > > Von: Justin Mclean
> > > An: dev@iotdb.apache.org
> > > Cc:
> > >
> > > Hi,
> > >
> > > > I carefully think again and again, I still think it could be
> better that
> > > if
> > > > we can update the README.md file in the release version..
> > >
> > > Releases don’t have to be perfect, they just need to be better
> than the
> > > previous release. As this is the first release then anything you
> release is
> > > going to be better than what you had previously.
> > >
> > > If there is an issue with a previous release you can alway make a
> new one
> > > to fix any issue some time in the future.
> > >
> > > It would be good to see more of the PPMC vote on this release.
> There are
> > > after all 20 of you! When you’re a TLP you’ll not have mentors and
> need to
> > > vote on your own releases.
> > >
> > > (As an aside I can see that 6 of the 20 PPMC members are not
> signed up to
> > > the private list, it is a requirement that you do so).
> > >
> > > Thanks,
> > > Justin
> > >
> >
> >
>
> --
> Kevin A. McGrail
> Member, Apache Software Foundation
> Chair Emeritus Apache SpamAssassin Project
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
>




Re: [DISCUSS] Apache IoTDB (Incubating) 0.8.0 RC3

2019-08-12 Thread Julian Feinauer
Hi Kev,

thank you fort he vote : )
Indeed, now we are full (IPMC wise) : )

But Justin also promised me to do this (and I always have a good feeling when I 
see his +1 as hes really a world-class release voter...).

Julian

Am 12.08.19, 16:32 schrieb "Kevin A. McGrail" :

Please accept my vote +1 binding, them.  I have checked over the zip
files, compiled the server and client but not run them.  Tere is the
minor readme issue which I don't think is a hold up
(https://github.com/apache/incubator-iotdb/pull/335)  Looking forward to
this release.

On 8/12/2019 10:27 AM, Julian Feinauer wrote:
> Hi Xiangdong,
>
> I left the vote open for 2 reasons.
> First, we currently have only 2 PPMC Votes.
> Chris vote also counts as PPMC Vote so we could close the vote with 3 +1 
Votes (not 4, mine is not binding for PPMC).
>
> Second, we only have 2 binding IPMC Votes and I'd like to bring it to 
general@ with 3 IPMC Votes as I think it’s a good practice for Podlings.
>
> But, I suggest that some more PPMC members participate in the vote. Its 
not so good to pass votes only with mentor votes when there are enough people 
in the PPMC.
> The PPMC currently has 20 members, so I personally would like to see at 
least 10 Votes from the PPMC but we could, of course also close it earlier.
>
> But I want at least 3 PPMC votes and 3 IPMC Votes before closing and this 
should be doable : )
>
> Julian
>
> Am 12.08.19, 15:58 schrieb "Xiangdong Huang" :
>
> Hi,
> 
> If there is no more voters... how about ending the vote?  There are 4 
+1
> votes now.
> 
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
> 
>  黄向东
> 清华大学 软件学院
> 
> 
> Julian Feinauer  于2019年8月10日周六 下午4:04写道:
> 
> > Hi,
> >
> > One more from my side... We should not focus on the binaries in the 
Readme.
> > 8 think it's better to prepare a nice download and getting started 
site
> > where we explain.
> > There we can focus on binaries, that's fine.
> >
> > And downdload site we need after all before sending out an announce 
(after
> > IPMC vote finished successfully).
> >
> > Julian
> >
> > Von meinem Mobiltelefon gesendet
> >
> >
> >  Ursprüngliche Nachricht 
> > Betreff: Re: [DISCUSS] Apache IoTDB (Incubating) 0.8.0 RC3
> > Von: Justin Mclean
> > An: dev@iotdb.apache.org
> > Cc:
> >
> > Hi,
> >
> > > I carefully think again and again, I still think it could be 
better that
> > if
> > > we can update the README.md file in the release version..
> >
> > Releases don’t have to be perfect, they just need to be better than 
the
> > previous release. As this is the first release then anything you 
release is
> > going to be better than what you had previously.
> >
> > If there is an issue with a previous release you can alway make a 
new one
> > to fix any issue some time in the future.
> >
> > It would be good to see more of the PPMC vote on this release. 
There are
> > after all 20 of you! When you’re a TLP you’ll not have mentors and 
need to
> > vote on your own releases.
> >
> > (As an aside I can see that 6 of the 20 PPMC members are not signed 
up to
> > the private list, it is a requirement that you do so).
> >
> > Thanks,
> > Justin
> >
> 
>

-- 
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171





Re: [DISCUSS] Apache IoTDB (Incubating) 0.8.0 RC3

2019-08-12 Thread Julian Feinauer
Hi Xiangdong,

I left the vote open for 2 reasons.
First, we currently have only 2 PPMC Votes.
Chris vote also counts as PPMC Vote so we could close the vote with 3 +1 Votes 
(not 4, mine is not binding for PPMC).

Second, we only have 2 binding IPMC Votes and I'd like to bring it to general@ 
with 3 IPMC Votes as I think it’s a good practice for Podlings.

But, I suggest that some more PPMC members participate in the vote. Its not so 
good to pass votes only with mentor votes when there are enough people in the 
PPMC.
The PPMC currently has 20 members, so I personally would like to see at least 
10 Votes from the PPMC but we could, of course also close it earlier.

But I want at least 3 PPMC votes and 3 IPMC Votes before closing and this 
should be doable : )

Julian

Am 12.08.19, 15:58 schrieb "Xiangdong Huang" :

Hi,

If there is no more voters... how about ending the vote?  There are 4 +1
votes now.

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


    Julian Feinauer  于2019年8月10日周六 下午4:04写道:

> Hi,
>
> One more from my side... We should not focus on the binaries in the 
Readme.
> 8 think it's better to prepare a nice download and getting started site
> where we explain.
> There we can focus on binaries, that's fine.
>
> And downdload site we need after all before sending out an announce (after
> IPMC vote finished successfully).
>
> Julian
>
> Von meinem Mobiltelefon gesendet
>
>
>  Ursprüngliche Nachricht 
> Betreff: Re: [DISCUSS] Apache IoTDB (Incubating) 0.8.0 RC3
> Von: Justin Mclean
> An: dev@iotdb.apache.org
> Cc:
>
> Hi,
>
> > I carefully think again and again, I still think it could be better that
> if
> > we can update the README.md file in the release version..
>
> Releases don’t have to be perfect, they just need to be better than the
> previous release. As this is the first release then anything you release 
is
> going to be better than what you had previously.
>
> If there is an issue with a previous release you can alway make a new one
> to fix any issue some time in the future.
>
> It would be good to see more of the PPMC vote on this release. There are
> after all 20 of you! When you’re a TLP you’ll not have mentors and need to
> vote on your own releases.
>
> (As an aside I can see that 6 of the 20 PPMC members are not signed up to
> the private list, it is a requirement that you do so).
>
> Thanks,
> Justin
>




AW: [DISCUSS] Apache IoTDB (Incubating) 0.8.0 RC3

2019-08-10 Thread Julian Feinauer
Hi,

One more from my side... We should not focus on the binaries in the Readme.
8 think it's better to prepare a nice download and getting started site where 
we explain.
There we can focus on binaries, that's fine.

And downdload site we need after all before sending out an announce (after IPMC 
vote finished successfully).

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: [DISCUSS] Apache IoTDB (Incubating) 0.8.0 RC3
Von: Justin Mclean
An: dev@iotdb.apache.org
Cc:

Hi,

> I carefully think again and again, I still think it could be better that if
> we can update the README.md file in the release version..

Releases don’t have to be perfect, they just need to be better than the 
previous release. As this is the first release then anything you release is 
going to be better than what you had previously.

If there is an issue with a previous release you can alway make a new one to 
fix any issue some time in the future.

It would be good to see more of the PPMC vote on this release. There are after 
all 20 of you! When you’re a TLP you’ll not have mentors and need to vote on 
your own releases.

(As an aside I can see that 6 of the 20 PPMC members are not signed up to the 
private list, it is a requirement that you do so).

Thanks,
Justin


AW: [DISCUSS] Apache IoTDB (Incubating) 0.8.0 RC3

2019-08-10 Thread Julian Feinauer
Hey, yes we will and we have to, currently we only have one +1 vote so we 
cannot close the vote successfully :)

It's always allowed to have a longer vote but it should not be shorter than 
72hrs in most cases.

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: [DISCUSS] Apache IoTDB (Incubating) 0.8.0 RC3
Von: Xiangdong Huang
An: dev@iotdb.apache.org
Cc:

Hi,

Indeed there are so few persons joining the vote... If possible, I suggest
to give one more day to other guys..

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Julian Feinauer  于2019年8月9日周五 下午8:37写道:

> Hi all,
>
> This is a short reminder that the vote is open and could close in a few
> hours.
> But, currently we only have ONE PPMC Vote.
>
> I think this is especially notable because the PPMC for iotdb has 20
> members.
>
> So please PPMCs vote for the release and help us get it out.
> As RM I would not feel confident to close the vote before we do not have a
> noticeable amount of votes from the PPMC (although technically we could
> with two more positive votes).
>
> Best
> Julian
>
> Von meinem Mobiltelefon gesendet
>
>
>  Ursprüngliche Nachricht 
> Betreff: Re: [DISCUSS] Apache IoTDB (Incubating) 0.8.0 RC3
> Von: Justin Mclean
> An: dev@iotdb.apache.org
> Cc:
>
> Hi,
>
> > I mean will we have another releasing version for 0.8.0 without the RC
> > suffix?
>
> Assuming teh vote changes no. You can change the artefact name without an
> affect on the hashes or signatures.
>
> Thanks,
> Justin
>


AW: [DISCUSS] Apache IoTDB (Incubating) 0.8.0 RC3

2019-08-09 Thread Julian Feinauer
Hi all,

This is a short reminder that the vote is open and could close in a few hours.
But, currently we only have ONE PPMC Vote.

I think this is especially notable because the PPMC for iotdb has 20 members.

So please PPMCs vote for the release and help us get it out.
As RM I would not feel confident to close the vote before we do not have a 
noticeable amount of votes from the PPMC (although technically we could with 
two more positive votes).

Best
Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: [DISCUSS] Apache IoTDB (Incubating) 0.8.0 RC3
Von: Justin Mclean
An: dev@iotdb.apache.org
Cc:

Hi,

> I mean will we have another releasing version for 0.8.0 without the RC
> suffix?

Assuming teh vote changes no. You can change the artefact name without an 
affect on the hashes or signatures.

Thanks,
Justin


Re: [DISCUSS] Apache IoTDB (Incubating) 0.8.0 RC3

2019-08-07 Thread Julian Feinauer
Hi,

I myself consider this "minor" so I suggest to keep that for the next release 
(we can always do a 0.8.1, if we feel like).
From my perspective, we fixed a lot of stuff and are "pretty mature" (with 
regards to how we started) but theres still a way to go.

But of course, its up to everybody to vote a -1 with explanation and then we 
will discuss and find a solution.

Julian

Am 07.08.19, 15:51 schrieb "Christofer Dutz" :

I was referring to the README in the last RC to be the one of the source 
distribution.
I was suggesting to create a README-binary with instructions on how to use 
the binary and to include that instead of the source one in the binary 
distribution.

By the way ... we could also move the NOTICE-binary and alike into a 
distribution/src/assembly/resources directory and there they won't confuse 
people.

Chris


    Am 07.08.19, 11:45 schrieb "Julian Feinauer" :

Hi Boris,

thanks fort he comment.
I think there is an important subtility in there.
As we as ASF only provide source releases, the README should still 
point to that instruction.

But on the homepage (where we'll have to place a download link) we can 
also write how to run the binaries.

For everything else, I agree.

Julian

Am 07.08.19, 11:36 schrieb "Boris Zhu" :

After this PR, https://github.com/apache/incubator-iotdb/pull/332, 
I think
we should rewrite some documents as Chris Dutz
<https://github.com/chrisdutz>suggests, especially readme.md and
quickstart. I remember quickstart requires users to compile source 
code
then use it instead of using binary directly. It's inconvenient for 
many
users. The documents still have little mistakes. I think the 
following
steps should be followed in order to avoid mistakes.

First, we should develop a uniform way of writing documents.

Second, someone opens an issue for writing a specific document and 
assign
it to someone(seem like I don't have the right to assign an issue 
in apache
Jira and there are still many issues not to be assigned).

third, someone reviews the documents.

Boris.



    
    On Tue, Aug 6, 2019 at 11:11 PM Julian Feinauer <
j.feina...@pragmaticminds.de> wrote:

> Hi,
>
> please keep all discussions around the RC here so that we have 
the Vote
> thread for VOTES only!
>
> Thanks!
> Julian
>








Re: [DISCUSS] Apache IoTDB (Incubating) 0.8.0 RC3

2019-08-07 Thread Julian Feinauer
Hi Boris,

thanks fort he comment.
I think there is an important subtility in there.
As we as ASF only provide source releases, the README should still point to 
that instruction.

But on the homepage (where we'll have to place a download link) we can also 
write how to run the binaries.

For everything else, I agree.

Julian

Am 07.08.19, 11:36 schrieb "Boris Zhu" :

After this PR, https://github.com/apache/incubator-iotdb/pull/332, I think
we should rewrite some documents as Chris Dutz
<https://github.com/chrisdutz>suggests, especially readme.md and
quickstart. I remember quickstart requires users to compile source code
then use it instead of using binary directly. It's inconvenient for many
users. The documents still have little mistakes. I think the following
steps should be followed in order to avoid mistakes.

First, we should develop a uniform way of writing documents.

Second, someone opens an issue for writing a specific document and assign
it to someone(seem like I don't have the right to assign an issue in apache
Jira and there are still many issues not to be assigned).

third, someone reviews the documents.

Boris.




On Tue, Aug 6, 2019 at 11:11 PM Julian Feinauer <
j.feina...@pragmaticminds.de> wrote:

> Hi,
>
> please keep all discussions around the RC here so that we have the Vote
> thread for VOTES only!
>
> Thanks!
> Julian
>




Re: [VOTE] Apache IoTDB (Incubating) 0.8.0 RC3

2019-08-07 Thread Julian Feinauer
Hi,

my vote is 
+1 (non-binding) PPMC Vote
but also
+1 (binding) IPMC Vote
(as I think the best practice is nowadays to also report IPMC Votes that where 
cast during PPMC Vote).

I checked:

- Downloaded staged artefacts
- Validated Hases and Signatures
- Build source bundle (mvn clean verify)
- Verified existence of README; RELEASE_NOTES, LICENSE and NOTICES
- [RM] Verified RELEADE_NOTES and README are the same as staged ones
- checked the contents of LICENSE, NOTICE, README, RELEASE_NOTES
- source bundle contains NO jars
- Checked no snapshot references
- UNPACKed the binary artefact and check the contents of LICENSE-binary and 
NOTICE-binary
- [Not necessary] Started Server, started Client, Client connects sucessfully 

One minor issue found:
One minor thing here: Hive in NOTICE is stated as 2008 - 2018... should it be 
2019 here?

Julian

Am 06.08.19, 16:56 schrieb "Julian Feinauer" :

Hi all,

thanks to cdutz for finding some major issues in RC2 and fixing them we are 
able to already provide RC3 now.

Important: All PMCs please note that you have to CHECK the release 
artifacts [1] (see below) before being allowed to vote “+1”, see [3,4].

Apache IoTDB (Incubating) 0.8.0 has been staged under [1] and it’s time to 
vote
on accepting it for release.  All Maven artifacts are available under [2].
If approved we will seek final release approval from the IPMC.
Voting will be open for 72hr.

A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.

Release tag: release/0.8.0
Hash for the release tag: 2f4da03b05d1c063eaaca622c68de86abe35de22

Per [3] "Before voting +1 [P]PMC members are required to download
the signed source code package, compile it as provided, and test
the resulting executable on their own platform, along with also
verifying that the package meets the requirements of the ASF policy
on releases."

You can achieve the above by following [4].

[ ]  +1 accept (indicate what you validated - e.g. performed the non-RM 
items in [4])
[ ]  -1 reject (explanation required)

[1] https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.8.0/rc3
[2] https://repository.apache.org/content/repositories/orgapacheiotdb-1003
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] 
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release





AW: Integrate Calcite and JDBC

2019-08-06 Thread Julian Feinauer
Hey,

I agree although I think long term we should move to calcite like nearly all 
apache projects did.
You can even have your special syntax there.

But in the meantime is fine to have two implementations.

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: Integrate Calcite and JDBC
Von: Xiangdong Huang
An: dev@iotdb.apache.org
Cc:

Hi,

I think it is a good idea.
Current JDBC and service-rpc module should be improved in my opinion..
For example, the SQL parser takes about 40% time cost for an "insert"
command.. (I remember that there is an issue mentioned that..).
Second, PreparedStatement is not implemented in current version (even in
the master branch).

Using Calcite is a kind of good choice, and for achieving that we need to
define how to map current SQL syntax to the standard SQL syntax.

By the way, I think it is also fine to keep maintaining the two JDBC and
SQL implementations (one for the current SQL and the other for the standard
SQL) for a while.
The implementation which has the best performance will be the final first
class citizen (Or, different users can use choose different implementation,
if someone prefer to the performance while others prefer the standard sql).


Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Julian Feinauer  于2019年8月6日周二 上午5:59写道:

> Hi all,
>
> there has been quite a bit of discussion this at the beginning but its
> become quiet about that.
> I think it would be great to move the JDBC Implementation to Calcite for
> multiple reasons.
>
> First, you get support for (nearly) everything in the SQL Standard.
> Second, you don’t have to maintain that.
> Third, we could even consider adding indices or dialects later on to
> improve the performance drastically.
>
> But the first step, for me, would be to revisit how JDBC is currently
> implemented and how the syntax maps SQL to the IoTDB data model.
> Then, I will, if my time allows it, happily help with the implementation.
>
> Julian
>


Re: Final fixes before RC3

2019-08-06 Thread Julian Feinauer
Hey,

yes, I had a cherry pick which introduced one or two deps on 0.9.0-SNAPSHOT 
instead of 0.8.0-SNAPSHOT which caused the issue : )

Julian

Am 06.08.19, 17:31 schrieb "Xiangdong Huang" :

Hi,

>  Required field 'timestampPrecision' was not present!

It is a new feature introduced by PR#285 [1]. The PR is merged into the
master, rather than 0.8..


[1] https://github.com/apache/incubator-iotdb/pull/285

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院
    
    
Julian Feinauer  于2019年8月6日周二 上午7:18写道:

> Sorry, was my own mistake, I had some issues somewhere else... everything
> is fine : )
>
> Am 06.08.19, 15:46 schrieb "Julian Feinauer" <
> j.feina...@pragmaticminds.de>:
>
> Hi all,
>
> after merging Chris PR (thank you Chris!) I just checked everything
> before preparing the next RC and I observed that I get an issue with the
> created binaries.
> I can start the server without Problems.
> But when I start the Client I get:
>
> 2019-08-06 15:43:32,498 [pool-1-IoTDB-JDBC-Client-thread-1] ERROR
> org.apache.thrift.server.TThreadPoolServer$WorkerProcess:295 - Thrift 
error
> occurred during processing of message.
> org.apache.thrift.protocol.TProtocolException: Required field
> 'timestampPrecision' was not present! Struct:
> ServerProperties(version:0.8.0,
> supportedTimeAggregationOperations:[max_time, min_time],
> timestampPrecision:null)
> at
> 
org.apache.iotdb.service.rpc.thrift.ServerProperties.validate(ServerProperties.java:482)
> at
> 
org.apache.iotdb.service.rpc.thrift.TSIService$getProperties_result.validate(TSIService.java:11262)
> at
> 
org.apache.iotdb.service.rpc.thrift.TSIService$getProperties_result$getProperties_resultStandardScheme.write(TSIService.java:11321)
> at
> 
org.apache.iotdb.service.rpc.thrift.TSIService$getProperties_result$getProperties_resultStandardScheme.write(TSIService.java:11288)
> at
> 
org.apache.iotdb.service.rpc.thrift.TSIService$getProperties_result.write(TSIService.java:11239)
> at
> org.apache.thrift.ProcessFunction.process(ProcessFunction.java:53)
> at
> org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
> at
> 
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286)
> at
> 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> 2019-08-06 15:43:32,499 [pool-1-IoTDB-JDBC-Client-thread-1] INFO
> org.apache.iotdb.db.service.TSServiceImpl:207 - IoTDB: receive close
> operation
> 2019-08-06 15:43:32,501 [pool-1-IoTDB-JDBC-Client-thread-1] INFO
> org.apache.iotdb.db.service.TSServiceImpl:182 - IoTDB: receive close 
session
> 2019-08-06 15:43:32,503 [pool-1-IoTDB-JDBC-Client-thread-1] WARN
> org.apache.thrift.transport.TIOStreamTransport:112 - Error closing output
> stream.
> java.net.SocketException: Socket closed
> at
> java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:116)
> at
> java.net.SocketOutputStream.write(SocketOutputStream.java:153)
> at
> java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
> at
> java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
> at
> java.io.FilterOutputStream.close(FilterOutputStream.java:158)
> at
> 
org.apache.thrift.transport.TIOStreamTransport.close(TIOStreamTransport.java:110)
> at
> org.apache.thrift.transport.TSocket.close(TSocket.java:235)
> at
> 
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:303)
> at
> 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
>
> has anybody an idea how this has happened and what to do to fix it?
>
> Thank you!
>
> Julian
>
> PS.: All tests do pass.
>
>
>




[DISCUSS] Apache IoTDB (Incubating) 0.8.0 RC3

2019-08-06 Thread Julian Feinauer
Hi,

please keep all discussions around the RC here so that we have the Vote thread 
for VOTES only!

Thanks!
Julian


[VOTE] Apache IoTDB (Incubating) 0.8.0 RC3

2019-08-06 Thread Julian Feinauer
Hi all,

thanks to cdutz for finding some major issues in RC2 and fixing them we are 
able to already provide RC3 now.

Important: All PMCs please note that you have to CHECK the release artifacts 
[1] (see below) before being allowed to vote “+1”, see [3,4].

Apache IoTDB (Incubating) 0.8.0 has been staged under [1] and it’s time to vote
on accepting it for release.  All Maven artifacts are available under [2].
If approved we will seek final release approval from the IPMC.
Voting will be open for 72hr.

A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.

Release tag: release/0.8.0
Hash for the release tag: 2f4da03b05d1c063eaaca622c68de86abe35de22

Per [3] "Before voting +1 [P]PMC members are required to download
the signed source code package, compile it as provided, and test
the resulting executable on their own platform, along with also
verifying that the package meets the requirements of the ASF policy
on releases."

You can achieve the above by following [4].

[ ]  +1 accept (indicate what you validated - e.g. performed the non-RM items 
in [4])
[ ]  -1 reject (explanation required)

[1] https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.8.0/rc3
[2] https://repository.apache.org/content/repositories/orgapacheiotdb-1003
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] 
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release



Re: Final fixes before RC3

2019-08-06 Thread Julian Feinauer
Sorry, was my own mistake, I had some issues somewhere else... everything is 
fine : )

Am 06.08.19, 15:46 schrieb "Julian Feinauer" :

Hi all,

after merging Chris PR (thank you Chris!) I just checked everything before 
preparing the next RC and I observed that I get an issue with the created 
binaries.
I can start the server without Problems.
But when I start the Client I get:

2019-08-06 15:43:32,498 [pool-1-IoTDB-JDBC-Client-thread-1] ERROR 
org.apache.thrift.server.TThreadPoolServer$WorkerProcess:295 - Thrift error 
occurred during processing of message.
org.apache.thrift.protocol.TProtocolException: Required field 
'timestampPrecision' was not present! Struct: ServerProperties(version:0.8.0, 
supportedTimeAggregationOperations:[max_time, min_time], 
timestampPrecision:null)
at 
org.apache.iotdb.service.rpc.thrift.ServerProperties.validate(ServerProperties.java:482)
at 
org.apache.iotdb.service.rpc.thrift.TSIService$getProperties_result.validate(TSIService.java:11262)
at 
org.apache.iotdb.service.rpc.thrift.TSIService$getProperties_result$getProperties_resultStandardScheme.write(TSIService.java:11321)
at 
org.apache.iotdb.service.rpc.thrift.TSIService$getProperties_result$getProperties_resultStandardScheme.write(TSIService.java:11288)
at 
org.apache.iotdb.service.rpc.thrift.TSIService$getProperties_result.write(TSIService.java:11239)
at 
org.apache.thrift.ProcessFunction.process(ProcessFunction.java:53)
at 
org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
at 
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
2019-08-06 15:43:32,499 [pool-1-IoTDB-JDBC-Client-thread-1] INFO  
org.apache.iotdb.db.service.TSServiceImpl:207 - IoTDB: receive close operation
2019-08-06 15:43:32,501 [pool-1-IoTDB-JDBC-Client-thread-1] INFO  
org.apache.iotdb.db.service.TSServiceImpl:182 - IoTDB: receive close session
2019-08-06 15:43:32,503 [pool-1-IoTDB-JDBC-Client-thread-1] WARN  
org.apache.thrift.transport.TIOStreamTransport:112 - Error closing output 
stream.
java.net.SocketException: Socket closed
at 
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:116)
at 
java.net.SocketOutputStream.write(SocketOutputStream.java:153)
at 
java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
at 
java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
at java.io.FilterOutputStream.close(FilterOutputStream.java:158)
at 
org.apache.thrift.transport.TIOStreamTransport.close(TIOStreamTransport.java:110)
at org.apache.thrift.transport.TSocket.close(TSocket.java:235)
at 
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:303)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

has anybody an idea how this has happened and what to do to fix it?

Thank you!

Julian

PS.: All tests do pass.




Final fixes before RC3

2019-08-06 Thread Julian Feinauer
Hi all,

after merging Chris PR (thank you Chris!) I just checked everything before 
preparing the next RC and I observed that I get an issue with the created 
binaries.
I can start the server without Problems.
But when I start the Client I get:

2019-08-06 15:43:32,498 [pool-1-IoTDB-JDBC-Client-thread-1] ERROR 
org.apache.thrift.server.TThreadPoolServer$WorkerProcess:295 - Thrift error 
occurred during processing of message.
org.apache.thrift.protocol.TProtocolException: Required field 
'timestampPrecision' was not present! Struct: ServerProperties(version:0.8.0, 
supportedTimeAggregationOperations:[max_time, min_time], 
timestampPrecision:null)
at 
org.apache.iotdb.service.rpc.thrift.ServerProperties.validate(ServerProperties.java:482)
at 
org.apache.iotdb.service.rpc.thrift.TSIService$getProperties_result.validate(TSIService.java:11262)
at 
org.apache.iotdb.service.rpc.thrift.TSIService$getProperties_result$getProperties_resultStandardScheme.write(TSIService.java:11321)
at 
org.apache.iotdb.service.rpc.thrift.TSIService$getProperties_result$getProperties_resultStandardScheme.write(TSIService.java:11288)
at 
org.apache.iotdb.service.rpc.thrift.TSIService$getProperties_result.write(TSIService.java:11239)
at 
org.apache.thrift.ProcessFunction.process(ProcessFunction.java:53)
at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39)
at 
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:286)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
2019-08-06 15:43:32,499 [pool-1-IoTDB-JDBC-Client-thread-1] INFO  
org.apache.iotdb.db.service.TSServiceImpl:207 - IoTDB: receive close operation
2019-08-06 15:43:32,501 [pool-1-IoTDB-JDBC-Client-thread-1] INFO  
org.apache.iotdb.db.service.TSServiceImpl:182 - IoTDB: receive close session
2019-08-06 15:43:32,503 [pool-1-IoTDB-JDBC-Client-thread-1] WARN  
org.apache.thrift.transport.TIOStreamTransport:112 - Error closing output 
stream.
java.net.SocketException: Socket closed
at 
java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:116)
at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
at 
java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:82)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:140)
at java.io.FilterOutputStream.close(FilterOutputStream.java:158)
at 
org.apache.thrift.transport.TIOStreamTransport.close(TIOStreamTransport.java:110)
at org.apache.thrift.transport.TSocket.close(TSocket.java:235)
at 
org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:303)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

has anybody an idea how this has happened and what to do to fix it?

Thank you!

Julian

PS.: All tests do pass.


Integrate Calcite and JDBC

2019-08-06 Thread Julian Feinauer
Hi all,

there has been quite a bit of discussion this at the beginning but its become 
quiet about that.
I think it would be great to move the JDBC Implementation to Calcite for 
multiple reasons.

First, you get support for (nearly) everything in the SQL Standard.
Second, you don’t have to maintain that.
Third, we could even consider adding indices or dialects later on to improve 
the performance drastically.

But the first step, for me, would be to revisit how JDBC is currently 
implemented and how the syntax maps SQL to the IoTDB data model.
Then, I will, if my time allows it, happily help with the implementation.

Julian


Re: Findings in the build

2019-08-06 Thread Julian Feinauer
Hi Chris,

thanks fort he changes.
I checked the PR and all artefact seem to be as they should be.
So are there any other issues to be addressed before spinning up the next round 
(RC3)?

Julian

Am 05.08.19, 14:46 schrieb "Christofer Dutz" :

Hi all,

I just submitted a PR: https://github.com/apache/incubator-iotdb/pull/332

So I invested a great portion of Sunday and most of today to clean up the 
build a bit. Here comes a summary to what I found and changed:

  *   Nothing is built outside the target directory anymore
 *   I moved the static parts of the client and server distributions to 
“src/assembly/resources” and added an assembly that builds the client and 
server inside the target directory (You need to update the documentation on 
this)
 *   The sever is now available at 
server/target/iotdb-server-0.9.0-SNAPSHOT
 *   The client is now available at 
client/target/iotdb-client-0.9.0-SNAPSHOT
 *   I updated the integration tests to work with these new locations
  *   I updated the distribution module (binary-distribution) to simply 
include and unpack the client and server assemblies, which greatly simplifies 
the assembly itself.
  *   In the integration-tests you use a process builder to get the current 
working directory … you can access this in the “user.dir” System property.
  *   There was a large mixture of artifacts with different versions in the 
classpath.
 *   I set all external dependencies to the same versions using a big 
dependencyManagement block in the master pom
 *   I removed the explicit version of every external dependency and 
moved it into the main dependencyManagement block in the root pom (except 
dependencies only used in the examples, for these I added a 
dependencyManagement block in the example pom). This way you instantly identify 
external dependencies.
 *   I added an enforcer rule to fail the build if two differing 
versions of one artifact are being used in the build (This should eliminate 
this problem from re-occuring)
 *   I replaced the usage of “${project.version}” with the real version 
(There is no need to manually update these versions and this way when looking 
at the pom you instantly know the version … keep in mind if an artifact is 
deployed to maven central, the user doesn’t have the code and therefore he 
always has to scroll up to the top in order to see which version is used)
  *   There were some imports related to Jdk 11 no longer providing some 
APIs, I moved those imports to a maven profile, which is activated based on the 
JDK version
  *   HDFSInputTest created a file in “spark/test/” … if the test failed, 
the rat plugin would complain the next time it’s run, I let it create the file 
in the “target” directory

However I did notice that there is quite a number of artifacts still in the 
classpath that have different maven coordinates, but very similar content:

  *   com.fasterxml.jackson.* and org.codehaus.jackson (1.9.13) (Not 
dangerous as they have different package names)
  *   javax.activation:activation (1.1.1) and 
javax.activation:javax.activation-api (1.2.0) (Probably not dangerous as the 
API versions are pretty similar, but the package names are equal)
  *   javax.servlet:javax.servlet-api (3.1.0) and javax.servlet:servlet-api 
(2.5) (Possibly dangerous as there is a difference in the major version, which 
usually implies incompatible changes)
  *   …
  *   I added an enforcer rule, that reports this type of problems, but 
commented it out as there is quite a bit of this throughout the project which 
would have to be cleaned up  first.

I checked the full build with all tests on Oracle-Java 8, Open-JDK 11, 
Oracle-JDK 12.

Chris




Re: [CANCELLED][VOTE] Apache IoTDB (Incubating) 0.8.0 RC2

2019-08-05 Thread Julian Feinauer
Hi Justin,

thanks for the reminder.
But, in this situation I consider the issue that major (and it is to have 
binaries in a source release) that I see this as a veto.
And as I know that Chris is already working on a fix I think its nicer for us 
to enter the stage with a reasonable clean release and sort out as many 
"initial problems" as possible.

But, agree, the next RC should make it... or the one after... or ... : )

Julian

Am 05.08.19, 11:24 schrieb "Justin Mclean" :

Hi,

> due to the binding -1 Vote of Chris and the major issues he raised (and I 
guess nobody will argue about) I hereby cancel the Vote for 0.8.0 RC2.

Just a reminder that vote can still pass with -1 votes, -1 are not vetos. 
There's been a couple votes I’ve voted -1 one that still passed.

> For all (P)PMCs:
> Don’t worry, this is not uncommon for a first Apache Release and will get 
better and better with every release you do.

I think I recall one that had 14 RCs, hopefully we’ll not reach that number.

Thanks,
Justin



[CANCELLED][VOTE] Apache IoTDB (Incubating) 0.8.0 RC2

2019-08-05 Thread Julian Feinauer
Hi all,

due to the binding -1 Vote of Chris and the major issues he raised (and I guess 
nobody will argue about) I hereby cancel the Vote for 0.8.0 RC2.

Chris already told me that he is preparing a PR where he fixes the issues he 
observed (thanks for that!) so we'll wait for that to create a third RC.

For all (P)PMCs:
Don’t worry, this is not uncommon for a first Apache Release and will get 
better and better with every release you do.

So, keep up the good work!
Julian

Am 04.08.19, 05:31 schrieb "Justin Mclean" :

Hi

Sorry I’m -1 (binding) on this release as there a large number of jars in 
the source release.

I checked:
- signature and hashes fine
- incubating in name
- DISCLAIMER exists
- LICENSE could do with some improvements (see below)
- all source file have ASF headers
- unexpected compiled code in the source release (lots of jars)
- can compile from source

BTW it's always a good idea to run rat manually on the artefacts as it 
would catch issues like this.

You may want to consider using the new DISCLAIMER-WIP [1]

While OK, this text in LICENSE would be more descriptive:
"The following class is modified from Maven Wrapper
./.mvn/wrapper/MavenWrapperDownloader.java”

It should mentions the license it is under, the original copyright owner 
and ideally the version it came from.

The file [2] is missing it's header, the original 3rd party header should 
be retained.

Licenses can change over time so it always best to include that information.

Some other minor issues that are not release blockers:
- NOTICE-binary has "Copyright 2008-2018 The Apache Software Foundation” 
this should be 2018-2019.
- NOTICE contains "Copyright 2019 and onwards” this is not correct as 
copyright has an expire date. Please replace with "Copyright 2019”
- NOTICE contains "Copyright 2008-2019” for Apache Hive. are these years 
correct?

I was able to sat up teh server but the client failed with this error:
Error: Could not find or load main class org.apache.iotdb.cli.client.Client

May just be my environment or my configuration but you may want to double 
check that works.

Thanks,
Justin

1. https://incubator.apache.org/policy/incubation.html#disclaimers
2. ./.mvn/wrapper/MavenWrapperDownloader.java



AW: [DISCUSS] Apache IoTDB (Incubating) 0.8.0 RC2

2019-08-03 Thread Julian Feinauer
Hi Chris,

When thinking about it, I definitely agree.
I just copied over the mail template from an other poling where it was created 
from an apache member which may not be named here :P

But +1.

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: [DISCUSS] Apache IoTDB (Incubating) 0.8.0 RC2
Von: Christofer Dutz
An: dev@iotdb.apache.org
Cc:

Hi …

I do have a proposal for future release-candidates:
I think the link usually posted as [2] should be [1] in the future.
The reason is that this IS THE RELEASE … the current Maven artifacts in [1] are 
convenience binaries distributed by the PPMC.
Also might it make people think, this is what they have to verify and not 
what’s currently in [2].

Will now start verifying the RC2 …

Chris


[VOTE] Apache IoTDB (Incubating) 0.8.0 RC2

2019-08-02 Thread Julian Feinauer
Hi all,

thanks to all reviewers of the RC1 and to everybody who helped to fix all 
issues we are able to vote again for the second release candidate.

Important: All PMCs please note that you have to CHECK the release artifacts 
[2] (see below) before being allowed to vote “+1”, see [3,4].

Apache IoTDB (Incubating) 0.8.0 has been staged under [2] and it’s time to vote
on accepting it for release.  All Maven artifacts are available under [1].
If approved we will seek final release approval from the IPMC.
Voting will be open for 72hr.

A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.

Release tag: release/0.8.0
Hash for the release tag: 7b242b02bf4f8ef0df298a49ea9a977b50c526d5

Per [3] "Before voting +1 [P]PMC members are required to download
the signed source code package, compile it as provided, and test
the resulting executable on their own platform, along with also
verifying that the package meets the requirements of the ASF policy
on releases."

You can achieve the above by following [4].

[ ]  +1 accept (indicate what you validated - e.g. performed the non-RM items 
in [4])
[ ]  -1 reject (explanation required)

[1] https://repository.apache.org/content/repositories/orgapacheiotdb-1002
[2] https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.8.0/rc2
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] 
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release



AW: Issues with the assembly

2019-08-01 Thread Julian Feinauer
Hi Chris,

Thank you already for jumping in!

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Issues with the assembly
Von: Christofer Dutz
An: dev@iotdb.apache.org
Cc:

Hi all,

so I spared some time between all of my pre-ApacheCon duties and had a look at 
the assembly issues.
We have to change something for the binary release to work.

The problem is that the assembly is executed immediately at the beginning of 
the build. While this doesn’t matter for Source releases (All the sources are 
already there),
For the binary release, the jars have not yet been built. If you run a “maven 
package” and then again with the release-profile, then it will find jars and 
pack them in, but this is not what we want.
During a release, the plugin checks out the tagged version into 
“target/checkout” therefore the assembly will stay empty in every attempt.

Having an even deeper look into the descriptor the main problem is that you are 
referencing files so in order to include them into the assembly.
This is considered bad practice and you should use moduleSets and reference the 
artifacts directly. Also is there a pretty new.

I’ve already cleaned up quite a bit and will continue tomorrow … as soon as 
that’s done I’ll submit a PR (Or send it to Julian).

Chris

PS: Perhaps some good reading points:
https://maven.apache.org/plugins/maven-assembly-plugin/examples/multimodule/module-binary-inclusion-simple.html






AW: [RESULT][VOTE] Apache IoTDB (Incubating) 0.8.0 RC1

2019-07-31 Thread Julian Feinauer
 check the contents of LICENSE-binary, NOTICE-binary, README.md,
RELEASE_NOTES.md
>   *   LICENSE-binary: The binary doesn’t contain any source files (…
therefore mentioning the Hive files can be removed
>  *   LICENSE-binary: The binary doesn’t contain the maven-wrapper
… therefore this mention can be removed

 Solved in PR #328.

>*   LICENSE-binary: The binary release doesn’t contain any binary
files (no jars etc.) therefore I don’t think we need to technically list
anything (But I guess it’s more an issue that there is no jar in there … )
>*   NOTICE-binary: Same year issue as with the Source NOTICE
> *   NOTICE-binary: As the binary distribution doesn’t seem to contain any
binary content, I can’t really verify this
>*   README.md: Can’t verify as the binary distribution doesn’t work
>*   RELEASE_NOTES.md: Same issues as in the source bundle

need to notice this issue when we upload to dist.apache.org.

Best,

---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Julian Feinauer  于2019年7月30日周二 下午3:29写道:

> Hi all,
>
> so, the Vote for Apache IoTDB (incubating) 0.8.0 RC1 closes.
>
> The vote results is:
> Binding votes: 5 +1, no 0, no -1. BUT one -1 for the binary artefacts.
> Non-Binding votes: 1 +1 vote.
>
> As RM I declare the Vote nonetheless as NOT PASSED and suggest to prepare
> a RC2.
> It is not unusual for an RC to be cancelled, in fact this is a regular
> process (therefore we have RCs before releases).
>
> I suggest to fix the “major” thing, which is the binary artefacts as
> reported by Chris and possibly some minor other things, as reported by
> Justin and Chris and then I can prepare a new RC on Thursday on Friday
> which should pass the Vote comfortably.
>
> I suggest to send PRs for the fixes to me directly so that I can merge
> them to the rel/0.8 branch.
>
> Thanks to all who contributed to the Vote and especially our Mentors for
> their engagement!
>
> Julian
>
>


[RESULT][VOTE] Apache IoTDB (Incubating) 0.8.0 RC1

2019-07-30 Thread Julian Feinauer
Hi all,

so, the Vote for Apache IoTDB (incubating) 0.8.0 RC1 closes.

The vote results is:
Binding votes: 5 +1, no 0, no -1. BUT one -1 for the binary artefacts.
Non-Binding votes: 1 +1 vote.

As RM I declare the Vote nonetheless as NOT PASSED and suggest to prepare a RC2.
It is not unusual for an RC to be cancelled, in fact this is a regular process 
(therefore we have RCs before releases).

I suggest to fix the “major” thing, which is the binary artefacts as reported 
by Chris and possibly some minor other things, as reported by Justin and Chris 
and then I can prepare a new RC on Thursday on Friday which should pass the 
Vote comfortably.

I suggest to send PRs for the fixes to me directly so that I can merge them to 
the rel/0.8 branch.

Thanks to all who contributed to the Vote and especially our Mentors for their 
engagement!

Julian



Re: [DISCUSS] Apache IoTDB (Incubating) 0.8.0 RC1

2019-07-29 Thread Julian Feinauer
Hi all,

I'm moving this discussion tot he DISCUSS Thread (answering to Kevins mail).
With Chris vote result I agree with Kevin (and Chris) and also suggest to 
Cancel the RC.

I suggest that we make a few necessary fixes to come up with a RC2 soon so that 
we get the release out of the door.
Most of the "minor" findings can be addressed with the next release (0.9 I 
guess) in the meantime.

Julian

Am 26.07.19, 16:24 schrieb "Julian Feinauer" :

Hi all,

just a short notice.
I started to do a release documentation (based on PLC4X) which is in my 
branch "tooling-for-release" under "docs/Documentation/Developers/release.adoc".
We should start to integrate it in the homepage when the release is over.

Julian
    
Am 26.07.19, 16:17 schrieb "Julian Feinauer" :

This is the discussion thread for the corresponding VOTE thread.

Please keep discussions in this thread to simplify the counting of 
votes.

If you have to vote -1 please mention a brief description on why and 
then take the details to this thread.

Julian






Re: [VOTE] Apache IoTDB (Incubating) 0.8.0 RC1

2019-07-29 Thread Julian Feinauer
Hi,

thanks Chris and Justin for your comments.
I also want to point to the checklist (which I had in my initial Vote Email) 
which I created in our Confluence: 
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release

Although its important to State that "correct" is only what ASF Policies say or 
the Incubator Rules.
The List above is more for convencience (I usually use a similar one for PLC4X).

Julian

Am 29.07.19, 11:21 schrieb "Justin Mclean" :

Hi,

Also when voting on release it's a good idea to list what you checked 
rather than saying +1.

There’s a checklist that can be found here [1] that you can use or the 
project could come up with it’s own.

Some project try to automate this, but I’d take case in doing so as it 
sometime doesn’t catch everything and sometimes misses serious issues or gives 
false positives.

Thanks,
Justin

1. 
https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist



AW: [VOTE] Apache IoTDB (Incubating) 0.8.0 RC1

2019-07-29 Thread Julian Feinauer
Short nitpick for you Chris: we do not do binary releases :)

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: [VOTE] Apache IoTDB (Incubating) 0.8.0 RC1
Von: Christofer Dutz
An: dev@iotdb.apache.org
Cc:

Hi Xiangdong,

I guess you misunderstand what we're voting on.

We're not voting on the repository, we're voting on the artifacts, that are 
staged for release.
In this case:
https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.8.0/rc1/apache-iotdb-0.8.0-incubating-source-release.zip

And if you download this archive and unpack it, it's almost empty.
A binary release should be a ready-usable version you intentionally don't have 
to build.

Chris




Am 29.07.19, 09:19 schrieb "Xiangdong Huang" :

Hi Chris,

I tried once again and find that `release/0.8.0` can generate a 17MB binary
file, too. The previous error is caused by "too many requests" reported by
"org.sonatype.ossindex".  However, the tag of release/0.8.0 is out-of-date
because there are many document issues fixed after that.

Now I am confused again about why you cannot get a binary file...

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Xiangdong Huang  于2019年7月29日周一 下午3:08写道:

> Hi Chris,
>
> > I inspected the downloaded zip archive and couldn't find the jars.
>
> Did you download the  zip file from [1]?  The codes come from the
> `release/0.8.0` branch, and I tried it can not generated a correct binary
> file...
>
> Actually the branch that Jialin tried on is rel/0.8, which can generate a
> 17 MB binary file, and many README.md issues have been fixed in that
> branch.
>
> I think `release/0.8.0` branch should be updated or re-forked from 
rel/0.8.
>
> [1] https://github.com/apache/incubator-iotdb/releases/tag/release%2F0.8.0
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> Christofer Dutz  于2019年7月29日周一 下午2:12写道:
>
>> Well I just did the check and the binary distribution staged for release
>> is less than 3 MB big and doesn’t contain a single jar.
>> So I'll leave my -1 for the binary.
>>
>> Chris
>>
>> Am 29.07.19, 07:59 schrieb "Christofer Dutz" > >:
>>
>> I inspected the downloaded zip archive and couldn't find the jars.
>>
>> Will double-check as soon as I'm in office.
>>
>> Chris
>>
>> Holen Sie sich Outlook für Android
>>
>> 
>> From: Jialin Qiao 
>> Sent: Monday, July 29, 2019 5:00:35 AM
>> To: dev@iotdb.apache.org 
>> Subject: Re: [VOTE] Apache IoTDB (Incubating) 0.8.0 RC1
>>
>> Hi Chris,
>>
>> I checked the binary distribution, and didn't find the problem.
>>
>> You can run "mvn clean package -Papache-release -DskipTests" in the
>> root folder and get an "apache-iotdb-0.8.0-SNAPSHOT-incubatin-bin.zip" in
>> the target under the root.
>>
>> The structure of this zip file is as follow and it works well (by
>> ./sbin/start-server.sh and ./sbin/start-client.sh):
>>
>> .
>> ├── DISCLAIMER
>> ├── LICENSE-binary
>> ├── NOTICE-binary
>> ├── README.md
>> ├── RELEASE_NOTES.md
>> ├── conf
>> │   ├── iotdb-engine.properties
>> │   ├── iotdb-env.bat
>> │   ├── iotdb-env.sh
>> │   ├── iotdb-sync-client.properties
>> │   ├── logback-tool.xml
>> │   ├── logback.xml
>> │   └── tsfile-format.properties
>> ├── docs
>> │   ├── Community-History
>> │   ├── Community-Powered\ By.md
>> │   ├── Community-Project\ Committers.md
>> │   ├── Development.md
>> │   ├── Documentation
>> │   │   ├── Frequently\ asked\ questions.md
>> │   │   ├── OtherMaterial-Examples.md
>> │   │   ├── OtherMaterial-Reference.md
>> │   │   ├── OtherMaterial-Sample\ Data.md
>> │   │   ├── OtherMaterial-Sample\ Data.txt
>> │   │   ├── QuickStart.md
>> │   │   └── UserGuide
>> │   │   ├── 0-Content.md
>> │   │   ├── 1-Overview
>> │   │   │   ├── 1-What\ is\ IoTDB.md
>> │   │   │   ├── 2-Architecture.md
>> │   │   │   ├── 3-Scenario.md
>> │   │   │   └── 4-Features.md
>> │   │   ├── 2-Concept\ Key\ Concepts\ and\ Terminology
>> │   │   │   ├── 1-Key\ Concepts\ and\ Terminology.md
>> │   │   │   ├── 2-Data\ Type.md
>> │   │   │   ├── 3-Encoding.md
>> │   │   │   └── 4-Compression.md
>> │   │   ├── 3-Operation\ Manual
>> │   │   │   

AW: Re: IoTDB vs InfluxDB Benchmark Report

2019-07-27 Thread Julian Feinauer
Hey mehedi,

That's excellent :)

I'm really looking forward to that.
One thing you should do is to sign an Icla: 
https://www.apache.org/dev/new-committers-guide.html#cla

Or here are some other useful resources: 
https://www.apache.org/dev/new-committers-guide.html#cla

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: Re: IoTDB vs InfluxDB Benchmark Report
Von: mehedi hasan
An: dev@iotdb.apache.org
Cc:

Hi Ziangdong,
Thanks for your reply. I am looking forward to it.
I will start contributing soon as an initial contributor.

best regards
mehedi

On Sat, Jul 27, 2019 at 4:49 AM Xiangdong Huang  wrote:

> Hi,
>
> Thanks for be interested in IoTDB.
>
> After finishing the first releasing version, I plan to  write some
> documents to introduce the detailed design of IoTDB to help more new
> contributors joining the project.
>
> I also invite other initial committers contributing the design documents
> because you know more than others...
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> mehedi hasan  于2019年7月26日周五 下午9:11写道:
>
> > Hi,
> > Its great to see that the iotdb performs way more better than the influx
> > db.
> > I am fairly new to iotdb. I am interested to know bit more.
> > How can i know a bit details about how tsfile writting, reading and
> > querying algorithm works?
> > I've read the basic documentation what is out there already, looking
> > forward to know bit more about it.
> >
> > Best Regards
> > mehedi
> >
> >
> >
> > On Thu, Jul 25, 2019 at 3:57 PM Xiangdong Huang 
> > wrote:
> >
> > > Hi,
> > >
> > > Many thanks for your report, and glad to see the better query
> performance
> > > of IoTDB.
> > >
> > > Actually, I think IoTDB's write performance can also be far better than
> > > InfluxDB. Just try to tune two parameters that you listed, and I have
> > > pointed out how to tune them on JIRA.
> > >
> > > Look forward to your new report.
> > >
> > > By the way, IoTDB v0.8 has at least 50% write performance improvement
> :p
> > >
> > > Best,
> > > ---
> > > Xiangdong Huang
> > > School of Software, Tsinghua University
> > >
> > >  黄向东
> > > 清华大学 软件学院
> > >
> > >
> > > chengong13...@sangfor.com.cn 
> > 于2019年7月25日周四
> > > 下午5:02写道:
> > >
> > > > I've uploaded the report on jira:
> > > > https://issues.apache.org/jira/browse/IOTDB-155. Please go to jira
> for
> > > > detail.
> > > >
> > > > --
> > > > chengong13...@sangfor.com.cn
> > > >
> > > >
> > > > *From:* Xiangdong Huang 
> > > > *Date:* 2019-07-25 13:49
> > > > *To:* dev 
> > > > *Subject:* Re: IoTDB vs InfluxDB Benchmark Report
> > > > Hi,
> > > >
> > > > Many thanks for the topic, but mailing list does not support the
> > > > attachment...
> > > >
> > > > How about upload it to IoTDB confluence or just open an JIRA issue to
> > > > discuss about that.
> > > >
> > > > Best,
> > > >
> > > > chengong13...@sangfor.com.cn  >于2019年7月25日
> > > > 周四上午11:49写道:
> > > >
> > > > > hello,
> > > > >
> > > > >  Here is the IoTDB vs InfluxDB benchmark test report, which
> > > contains
> > > > > the write, read, and compression performance test.
> > > > >  You can check the annex for detail.
> > > > >  Best wishes :-)
> > > > >
> > > > > --
> > > > > chengong13...@sangfor.com.cn
> > > > >
> > > > --
> > > > ---
> > > > Xiangdong Huang
> > > > School of Software, Tsinghua University
> > > >
> > > > 黄向东
> > > > 清华大学 软件学院
> > > >
> > > >
> > >
> >
>


AW: [VOTE] Apache IoTDB (Incubating) 0.8.0 RC1

2019-07-27 Thread Julian Feinauer
Hi Kevin,

That's to discuss.
As Justin voted +1, I think he himself judges those things as minor enough.

I think it's best to wait for other mentors vote (and possible todos) and 
decide then.

What do others think?

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: [VOTE] Apache IoTDB (Incubating) 0.8.0 RC1
Von: "Kevin A. McGrail"
An: dev@iotdb.apache.org,李天安
Cc:

So with the changes from Justin's post, I would expect to see RC1
abandoned, the vote closed and an RC2 rolled.  Thoughts?

Regards,
KAM

On 7/26/2019 11:23 PM, 李天安 wrote:
> Hi,
>
> +1 (binding)
>
>
> Best Regards,
> —
> Tianan Li
> School of Software, Tsinghua University
>
> 李天安
> 清华大学 软件学院
>
>> 在 2019年7月27日,上午11:18,Xiangdong Huang  写道:
>>
>> Hi,
>>
>> +1 (binding).
>>
>> Thanks for pointing out the issues @Justin. Is there anything that we need
>> to modify?
>>
>> Good work! @Jialin.
>>
>> Best,
>> ---
>> Xiangdong Huang
>> School of Software, Tsinghua University
>>
>> 黄向东
>> 清华大学 软件学院
>>
>>
>> Jialin Qiao  于2019年7月27日周六 上午11:16写道:
>>
>>> Hi,
>>>
>>> +1 (binding)
>>>
>>>
>>> I fixed the problems that Justin mentioned in the PR [1], which is already
>>> merged into rel/0.8 and cherry-picked to master. The followings are my
>>> modifications:
>>>
 - NOTICE may include a little too much text.  I not seen an export
>>> control placed in NOTICE before, and you only need to include the bit from
>>> Hive notice that are relevant [1]
>>>
>>> fixed, and the export control notice is removed.
>>>
 - All source files have ASF headers. However this file [4] incorrectly
>>> has an ASF header. It’s 3rd party software and should not use the ASF
>>> header.
>>>
>>> removed the license and ASF header
>>>
 In the README.md
 - Under "Installation from source code” it point the user to GitHub. The
>>> user should be pointed to the projects download page, we don’t want to
>>> encourage users to use unreleased software.
>>>
>>> I add the projects download url.
>>>
 - The text displayed under "If successful, you will see the the
>>> following text in the terminal:” is not correct
>>>
>>> fixed
>>>
 - The instruction for compiling are not correct “mvn XXX -pl iotdb-cli”
>>> and “mvn XXX -pl iotdb” don’t work.
>>>
>>> fixed
>>>
 - The script to start and stop the server have incorrect paths
>>> fixed
>>>
 When starting the server I get this error, but I assume that just my
>>> setup or environment. Can someone else confirm that once compiled the
>>> source release they can start the server?
 Error: Could not find or load main class
>>> org.apache.iotdb.db.service.IoTDB
>>>
>>> not reproduced, may be it is caused by the above incorrect path and
>>> commands. Now you can try again.
>>>
 For the binary convenience release:
 - The binary notice has way too much information in it. For instance you
>>> only need to include the bit from Hive notice that are relevant [1],
>>> logbook [2] has no notice file so there no need to include anything about
>>> it in the NOTICE file [3]. There no need to mention licensing information,
>>> that goes in LICENCE
>>>
>>> fixed
>>>
 - Most permissive licenses say the full text of the license needs to be
>>> included, that includes the copyright line for BSD and MIT licensed
>>> software, I’m not sure that have generic license test in license covers
>>> that.
>>>
>>> Actually, we have a "licenses" folder under the root which contains full
>>> text of the licenses.
>>>
>>> [1] https://github.com/apache/incubator-iotdb/pull/314
>>>
>>>
>>> Best,
>>> --
>>> Jialin Qiao
>>> School of Software, Tsinghua University
>>>
>>> 乔嘉林
>>> 清华大学 软件学院
>>>
 -原始邮件-
 发件人: "Justin Mclean" 
 发送时间: 2019-07-27 07:56:31 (星期六)
 收件人: dev@iotdb.apache.org
 抄送:
 主题: Re: [VOTE] Apache IoTDB (Incubating) 0.8.0 RC1

 Hi,

 +1 (binding)

 I checked:
 - incubating in artefact names
 - DISCLAIMER exists
 - LICENSE is good
 - NOTICE may include a little too much text.  I not seen an export
>>> control placed in NOTICE before, and you only need to include the bit from
>>> Hive notice that are relevant [1]
 - All source files have ASF headers. However this file [4] incorrectly
>>> has an ASF header. It’s 3rd party software and should not use the ASF
>>> header.
 - No unexpected binary files
 - Can compile from source

 One minor thing in license is this path
>>> "./mvn/wrapper/MavenWrapperDownloader.java” should be
>>> "./.mvn/wrapper/MavenWrapperDownloader.java"
 In the README.md
 - Under "Installation from source code” it point the user to GitHub. The
>>> user should be pointed to the projects download page, we don’t want to
>>> encourage users to use unreleased software.
 - The text displayed under "If successful, you will see the the
>>> following text in the terminal:” is not correct
 - The instruction for compiling are not 

Re: [DISCUSS] Apache IoTDB (Incubating) 0.8.0 RC1

2019-07-26 Thread Julian Feinauer
Hi all,

just a short notice.
I started to do a release documentation (based on PLC4X) which is in my branch 
"tooling-for-release" under "docs/Documentation/Developers/release.adoc".
We should start to integrate it in the homepage when the release is over.

Julian

Am 26.07.19, 16:17 schrieb "Julian Feinauer" :

This is the discussion thread for the corresponding VOTE thread.

Please keep discussions in this thread to simplify the counting of votes.

If you have to vote -1 please mention a brief description on why and then 
take the details to this thread.

Julian




Re: [VOTE] Apache IoTDB (Incubating) 0.8.0 RC1

2019-07-26 Thread Julian Feinauer
Hi,

+1 (non-binding, jfeinauer).

I did

- download staged artifacts. Check their signature and hashes.
-  [RM] verify the reported signature is for an "apache.org" address ("gpg: 
Good signature from ...")
- verify the existence of LICENSE, NOTICE, README, RELEASE_NOTES files in the 
extracted source bundle
- [RM] verify the staged source README, RELEASE_NOTE files correspond to those 
in the extracted source bundle
- check the contents of LICENSE, NOTICE, README, RELEASE_NOTES
- UNPACK the binary artefact and check the contents of LICENSE-binary and 
NOTICE-binary
- build from directions in README
- [RM] review target/rat.txt (though the build should fail if RAT constraints 
aren't met)
- Find and files containing binary content with this command: find . -type f 
-name 'rat.txt' -exec grep -l " B " {} \;
- Then review for B (binary) content in those files:   grep " B " target/rat.txt
- Search for SNAPSHOT references find . -type f -name 'pom.xml' -exec grep -| 
"SNAPSHOT" {} \;
- did a full `mvn clean install` on OS X 10.14.4

Julian

Am 26.07.19, 16:16 schrieb "Julian Feinauer" :

Hi all,

First, thanks to all of you for the support.
This first RC is the result of a long process and I want to thank all who 
participated in it.
Special thanks go to our Mentors Justin and Chris who did a lot of support 
to make this RC hopefully a success.

Apache IoTDB (Incubating) 0.8.0 has been staged under [2] and it’s time to 
vote
on accepting it for release.  All Maven artifacts are available under [1].
If approved we will seek final release approval from the IPMC.
Voting will be open for 72hr.

A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.

Release tag: release/0.8.0
Hash for the release tag: 040cbd175b92969cbabf5548fe3df1cac7c88011

Per [3] "Before voting +1 [P]PMC members are required to download
the signed source code package, compile it as provided, and test
the resulting executable on their own platform, along with also
verifying that the package meets the requirements of the ASF policy
on releases."

You can achieve the above by following [4].

[ ]  +1 accept (indicate what you validated - e.g. performed the non-RM 
items in [4])
[ ]  -1 reject (explanation required)

[1] https://repository.apache.org/content/repositories/orgapacheiotdb-1001
[2] https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.8.0/rc1
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] 
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release





[DISCUSS] Apache IoTDB (Incubating) 0.8.0 RC1

2019-07-26 Thread Julian Feinauer
This is the discussion thread for the corresponding VOTE thread.

Please keep discussions in this thread to simplify the counting of votes.

If you have to vote -1 please mention a brief description on why and then take 
the details to this thread.

Julian


[VOTE] Apache IoTDB (Incubating) 0.8.0 RC1

2019-07-26 Thread Julian Feinauer
Hi all,

First, thanks to all of you for the support.
This first RC is the result of a long process and I want to thank all who 
participated in it.
Special thanks go to our Mentors Justin and Chris who did a lot of support to 
make this RC hopefully a success.

Apache IoTDB (Incubating) 0.8.0 has been staged under [2] and it’s time to vote
on accepting it for release.  All Maven artifacts are available under [1].
If approved we will seek final release approval from the IPMC.
Voting will be open for 72hr.

A minimum of 3 binding +1 votes and more binding +1 than binding -1
are required to pass.

Release tag: release/0.8.0
Hash for the release tag: 040cbd175b92969cbabf5548fe3df1cac7c88011

Per [3] "Before voting +1 [P]PMC members are required to download
the signed source code package, compile it as provided, and test
the resulting executable on their own platform, along with also
verifying that the package meets the requirements of the ASF policy
on releases."

You can achieve the above by following [4].

[ ]  +1 accept (indicate what you validated - e.g. performed the non-RM items 
in [4])
[ ]  -1 reject (explanation required)

[1] https://repository.apache.org/content/repositories/orgapacheiotdb-1001
[2] https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.8.0/rc1
[3] https://www.apache.org/dev/release.html#approving-a-release
[4] 
https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release



Re: Next steps for release 0.8.0-rc1

2019-07-26 Thread Julian Feinauer
Hi all,

Someone (xiangdong I think) renamed the artifactId of the "root" to 
"incubating-iotdb-parent" to have the incubating in artefact name.
As Chris just send over a patch to include that via assembly plugin I suggest 
to change this back to "iotdb-parent" which is in accordance with what many 
other projects do.

I submitted a PR (with many help from Chris!) which does some other necessary 
final fixed and hope that everybody agrees: 
https://github.com/apache/incubator-iotdb/pull/310

Content is:
Removed "build" module and moved this to parent pom.
Renamed parent pom without incubating.
Added incubating artefact names in assembly plugin.
Added SHA512 for all artefacts.

As soon as the PR is merged I will finally check and prepare an RC this 
weekend, I think.

Best
Julian

Am 26.07.19, 10:45 schrieb "Christofer Dutz" :

HI all,

I sent Julian a patch with my changes. Got a lot to do today so I have to 
keep it simple.

Chris


Am 26.07.19, 10:05 schrieb "Jialin Qiao" :

Hi Chris,

Glad to see you back! Our PR [1] separates the license with 
license-binary, updates the artifact in pom and adds "incubating" as the prefix 
of the artefact name. You can check and work in this PR.

[1] https://github.com/apache/incubator-iotdb/pull/300

Best,
--
Jialin Qiao
School of Software, Tsinghua University

乔嘉林
清华大学 软件学院

> -原始邮件-
> 发件人: "Xiangdong Huang" 
> 发送时间: 2019-07-26 15:47:29 (星期五)
> 收件人: dev@iotdb.apache.org
> 抄送: 
> 主题: Re: Next steps for release 0.8.0-rc1
> 
> Hi Chris,
> 
> I think It could not be better if there is a PR. The PR makes it 
easier to
> let us know how to do the same thing in the future..
> 
> Best
> 
> Christofer Dutz 于2019年7月26日 周五下午3:39写道:
> 
> > Hi Justin,
> >
> > As I see it, it was producing a source-release without the 
"incubating" in
> > it ... I just whipped up a patch for that and one that also 
generated the
> > required sha512 hashes.
> > Can I just commit that to the release branch, or do we have to do 
the full
> > PR procedure?
> >
> > Chris
> >
> >
> > Am 26.07.19, 09:16 schrieb "Justin Mclean" 
:
> >
> > Hi,
> >
> > > I am sure I can help with all the issues you are having. 
Could you
> > please make a list that I can work off?
> >
> > I think everything been sort, but you could take a look at the 
product
> > artefact to see if you think it has been.
> >
> > Thanks,
> > Justin
> >
> > --
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
> 
>  黄向东
> 清华大学 软件学院






AW: Next steps for release 0.8.0-rc1

2019-07-26 Thread Julian Feinauer
Hi Chris,

There is already a pr in place from jialin and xiangdong.
Perhaps it would be good to check that.

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: Next steps for release 0.8.0-rc1
Von: Christofer Dutz
An: dev@iotdb.apache.org
Cc:

Hi Justin,

As I see it, it was producing a source-release without the "incubating" in it 
... I just whipped up a patch for that and one that also generated the required 
sha512 hashes.
Can I just commit that to the release branch, or do we have to do the full PR 
procedure?

Chris


Am 26.07.19, 09:16 schrieb "Justin Mclean" :

Hi,

> I am sure I can help with all the issues you are having. Could you please 
make a list that I can work off?

I think everything been sort, but you could take a look at the product 
artefact to see if you think it has been.

Thanks,
Justin



Re: Should remove so many readme.md in submodule?

2019-07-25 Thread Julian Feinauer
Hi Boris,

+1 from my side.
Ideally we have few but well documented files that are also accessible via the 
homepage (under /documents).

Julian

Am 25.07.19, 10:12 schrieb "Boris Zhu" :

there are so many readme.md which are out of date in many submodules. I
think these should be in the document.




Re: Next steps for release 0.8.0-rc1

2019-07-25 Thread Julian Feinauer
Hi Justin,

thanks for the input.
These are the things why I wanted a first release to sort all that out : )

I guess we wait until tomorrow with preparation of an RC as Chris can surely 
assist a bit with things like artefact names and all that stuff.

Julian

Am 25.07.19, 08:46 schrieb "Justin Mclean" :

Hi,

> Or, we provide a RC1 (which we do not expect to be the final release) but 
have then the community and the mentors check everything.

I can check it tomorrow (my time). But a quick quick shows a couple of 
issues:
- Missing incubating in name of artefact
- Jars in the source release
- Name seem wrong "IoTDB Root”?
- Docker file seems to using master?
- Wrong header on this file? /.mvn/wrapper/MavenWrapperDownloader.java
- It not immediately obvious of there is any 3rd party code in the source 
which make license and notice a lot simpler

Also being a first release, as long as there’s not significant issues, i’s 
likely to pass an IPMC vote.

Thanks,
Justin



Re: Next steps for release 0.8.0-rc1

2019-07-25 Thread Julian Feinauer
Hi all,

after everything is setup for the release, EXCEPT for some unclarity with 
regards to LICENSE, NOTICE and binary “supplementary files” I ask myself whats 
the best way to proceed.
Either we check our current material with the help of our mentors (like the PR 
https://github.com/apache/incubator-iotdb/pull/300).

Or, we provide a RC1 (which we do not expect to be the final release) but have 
then the community and the mentors check everything.
Then we can collect all necessary changes and fix them and come back with a RC2 
which will hopefully pass then.

Perhaps the second version is a bit better and clearer and eases things for our 
mentors as its just an RC as they know it and can do their regular checks.

What do others (and also our mentors) think?

Julian

Am 25.07.19, 08:20 schrieb "Julian Feinauer" :

Hi Justin,

from Chris email it should work with:

> You can test what happens during a release by doing a "mvn package -P 
release,apache-release".

Julian

Am 25.07.19, 08:18 schrieb "Justin Mclean" :

HI,

> short update on that... INFRA already set up the staging profile on 
nexus and I just did a quick dry-run and everything works.

So how can I locally produce a source release?

Thanks,
Justin





Re: Next steps for release 0.8.0-rc1

2019-07-25 Thread Julian Feinauer
Hi Justin,

from Chris email it should work with:

> You can test what happens during a release by doing a "mvn package -P 
> release,apache-release".

Julian

Am 25.07.19, 08:18 schrieb "Justin Mclean" :

HI,

> short update on that... INFRA already set up the staging profile on nexus 
and I just did a quick dry-run and everything works.

So how can I locally produce a source release?

Thanks,
Justin



Re: Next steps for release 0.8.0-rc1

2019-07-25 Thread Julian Feinauer
Hey all,

short update on that... INFRA already set up the staging profile on nexus and I 
just did a quick dry-run and everything works.
So we are absolutely ready to go for a RC1 as soon as LICENSE and NOTICE 
changes are sorted out (https://github.com/apache/incubator-iotdb/pull/300).

Julian

Am 24.07.19, 13:47 schrieb "Julian Feinauer" :

Hi Chris,

Thanks for the comment.
I already requested a profile at infra 
(https://issues.apache.org/jira/plugins/servlet/mobile#issue/INFRA-18788).

But will be good to have your support for the next steps.

Julian

PS: have a nice list day!

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: Next steps for release 0.8.0-rc1
Von: Christofer Dutz
An: dev@iotdb.apache.org
Cc:

Hi guys,

I'm actually writing this lying in a sun bed at the beach on creta ;-)

You can test what happens during a release by doing a "mvn package -P 
release,apache-release".

Then it should also build the source release artifacts.

The only thing we need to do is that nexus is prepared for the iotdb group 
ID. Without that performing the releases would be a challenge 

But feel free to build a test - release with the apache-release profile 
enabled and check the contents of the artifacts. If you already did the release 
prepare, you can even manually build the release.

I'll be traveling home tomorrow so I'll be more accessible to help from 
Friday on.


Chris

Holen Sie sich Outlook für Android<https://aka.ms/ghei36>

____
From: Julian Feinauer 
Sent: Wednesday, July 24, 2019 11:21:38 AM
To: dev@iotdb.apache.org 
Subject: AW: Next steps for release 0.8.0-rc1

Hey,

Indeed he made the build and i rely on the build setup we used in plc4x 
which he build the iotdb on as he told me.

And I'm totally against reinventing the wheel for each project so I think 
the way we used it in plc4x is fine as you only need those artifacts for a 
release and then staging needs to be done also.

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: Next steps for release 0.8.0-rc1
Von: Justin Mclean
An: dev@iotdb.apache.org
Cc:

Hi,

Or even better this [1] . My mvn internal knowledge is a little vague, but 
on most ASF projects you go mvn package and you end up with the source release 
in the target directory.

Anyway Chris is the person to speak to about this, he probably knows what 
needs to be done.

Thanks,
Justin

1. http://maven.apache.org/plugins/maven-assembly-plugin/




Re: Version 0.8.1?

2019-07-24 Thread Julian Feinauer
Hey,

I found some time and reverted the changes from the first trial in rel/0.8.
So we can simply merge it when the PR is agreed on : )

Julian

Am 24.07.19, 13:42 schrieb "Julian Feinauer" :

Hi xiangdong,

I we should simply revert the rel branch back to before release, this is 
https://github.com/apache/incubator-iotdb/commit/0936b2bd2b9b91bb124affc036fb69505dd4f300

Or you prepare a pr and I'll merge it later.

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: Version 0.8.1?
Von: Xiangdong Huang
An: dev@iotdb.apache.org
Cc:

Hi Julian,

I see.

I am trying to fix the problem of LICENSE and NOTICE.

So, do I need to submit the PR to release/0.8.0 and cherry-pick them to
rel/0.8 and master branches after the PR is accepted?

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


    Julian Feinauer  于2019年7月24日周三 下午5:12写道:

> Hi Xiangdong,
>
> There is one tagged commit (tag 'release/0.8.0) in the commit log with
> version 0.8.0. This commit is the code for rc1.
> The rel branch shows 0.8.1 as this would be the next bugfix release for
> 0.8.
>
> Does that clarify your question?
>
> Julian
>
> Von meinem Mobiltelefon gesendet
>
>
>  Ursprüngliche Nachricht 
> Betreff: Version 0.8.1?
> Von: Xiangdong Huang
> An: dev@iotdb.apache.org
> Cc:
>
> Hi,
>
> I notice that the version is changed to 0.8.1 now on rel/0.8 branch.. Do 
we
> start with 0.8.0 or 0.8.1?
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>




AW: Next steps for release 0.8.0-rc1

2019-07-24 Thread Julian Feinauer
Hi Chris,

Thanks for the comment.
I already requested a profile at infra 
(https://issues.apache.org/jira/plugins/servlet/mobile#issue/INFRA-18788).

But will be good to have your support for the next steps.

Julian

PS: have a nice list day!

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: Next steps for release 0.8.0-rc1
Von: Christofer Dutz
An: dev@iotdb.apache.org
Cc:

Hi guys,

I'm actually writing this lying in a sun bed at the beach on creta ;-)

You can test what happens during a release by doing a "mvn package -P 
release,apache-release".

Then it should also build the source release artifacts.

The only thing we need to do is that nexus is prepared for the iotdb group ID. 
Without that performing the releases would be a challenge 

But feel free to build a test - release with the apache-release profile enabled 
and check the contents of the artifacts. If you already did the release 
prepare, you can even manually build the release.

I'll be traveling home tomorrow so I'll be more accessible to help from Friday 
on.


Chris

Holen Sie sich Outlook für Android<https://aka.ms/ghei36>

________
From: Julian Feinauer 
Sent: Wednesday, July 24, 2019 11:21:38 AM
To: dev@iotdb.apache.org 
Subject: AW: Next steps for release 0.8.0-rc1

Hey,

Indeed he made the build and i rely on the build setup we used in plc4x which 
he build the iotdb on as he told me.

And I'm totally against reinventing the wheel for each project so I think the 
way we used it in plc4x is fine as you only need those artifacts for a release 
and then staging needs to be done also.

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: Next steps for release 0.8.0-rc1
Von: Justin Mclean
An: dev@iotdb.apache.org
Cc:

Hi,

Or even better this [1] . My mvn internal knowledge is a little vague, but on 
most ASF projects you go mvn package and you end up with the source release in 
the target directory.

Anyway Chris is the person to speak to about this, he probably knows what needs 
to be done.

Thanks,
Justin

1. http://maven.apache.org/plugins/maven-assembly-plugin/


AW: Version 0.8.1?

2019-07-24 Thread Julian Feinauer
Hi xiangdong,

I we should simply revert the rel branch back to before release, this is 
https://github.com/apache/incubator-iotdb/commit/0936b2bd2b9b91bb124affc036fb69505dd4f300

Or you prepare a pr and I'll merge it later.

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: Version 0.8.1?
Von: Xiangdong Huang
An: dev@iotdb.apache.org
Cc:

Hi Julian,

I see.

I am trying to fix the problem of LICENSE and NOTICE.

So, do I need to submit the PR to release/0.8.0 and cherry-pick them to
rel/0.8 and master branches after the PR is accepted?

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Julian Feinauer  于2019年7月24日周三 下午5:12写道:

> Hi Xiangdong,
>
> There is one tagged commit (tag 'release/0.8.0) in the commit log with
> version 0.8.0. This commit is the code for rc1.
> The rel branch shows 0.8.1 as this would be the next bugfix release for
> 0.8.
>
> Does that clarify your question?
>
> Julian
>
> Von meinem Mobiltelefon gesendet
>
>
>  Ursprüngliche Nachricht 
> Betreff: Version 0.8.1?
> Von: Xiangdong Huang
> An: dev@iotdb.apache.org
> Cc:
>
> Hi,
>
> I notice that the version is changed to 0.8.1 now on rel/0.8 branch.. Do we
> start with 0.8.0 or 0.8.1?
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>


AW: Version 0.8.1?

2019-07-24 Thread Julian Feinauer
Hi Xiangdong,

There is one tagged commit (tag 'release/0.8.0) in the commit log with version 
0.8.0. This commit is the code for rc1.
The rel branch shows 0.8.1 as this would be the next bugfix release for 0.8.

Does that clarify your question?

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Version 0.8.1?
Von: Xiangdong Huang
An: dev@iotdb.apache.org
Cc:

Hi,

I notice that the version is changed to 0.8.1 now on rel/0.8 branch.. Do we
start with 0.8.0 or 0.8.1?

Best,
---
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


AW: Next steps for release 0.8.0-rc1

2019-07-24 Thread Julian Feinauer
Hey,

Indeed he made the build and i rely on the build setup we used in plc4x which 
he build the iotdb on as he told me.

And I'm totally against reinventing the wheel for each project so I think the 
way we used it in plc4x is fine as you only need those artifacts for a release 
and then staging needs to be done also.

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: Next steps for release 0.8.0-rc1
Von: Justin Mclean
An: dev@iotdb.apache.org
Cc:

Hi,

Or even better this [1] . My mvn internal knowledge is a little vague, but on 
most ASF projects you go mvn package and you end up with the source release in 
the target directory.

Anyway Chris is the person to speak to about this, he probably knows what needs 
to be done.

Thanks,
Justin

1. http://maven.apache.org/plugins/maven-assembly-plugin/


AW: Next steps for release 0.8.0-rc1

2019-07-24 Thread Julian Feinauer
Hey Justin,

If I recall correctly it does it only in the release :perform phase which 
currently fails because we have no profile on nexus :)

So as soon as this is done we should have the correct source package.

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: Next steps for release 0.8.0-rc1
Von: Justin Mclean
An: dev@iotdb.apache.org
Cc:

Hi,

> I know and what I meant is that sources will be packaged as tarball by the 
> source release goal from the apache parent maven pom.

Which currently doesn’t seem to create a source package when you do a "mvn 
package”. Hence my confusion of what’s actually in the release or not.

Thanks,
Justin


AW: Next steps for release 0.8.0-rc1

2019-07-24 Thread Julian Feinauer
Hi Justin,

I know and what I meant is that sources will be packaged as tarball by the 
source release goal from the apache parent maven pom.

This indicates pretty clearly what will be inside and what not.

Hope that helps.

Julian

Von meinem Mobiltelefon gesendet


 Ursprüngliche Nachricht 
Betreff: Re: Next steps for release 0.8.0-rc1
Von: Justin Mclean
An: dev@iotdb.apache.org
Cc:

Hi,

> The source release will be a "regular" maven release of the Java project.

Maven is not an official release platform or where the ASF places official 
releases :-) That may come as a surprise to some people.

You need to create a source tar ball and place it in the distribution area 
(dist.apache.org) [1] and vote on the contents of that. Once the release has 
been approved by the IPMC it can be moved here [2] and the Apache mirror system 
will pick it up.

Thanks,
Justin

1. https://dist.apache.org/repos/dist/dev/incubator/
2.  https://dist.apache.org/repos/dist/release/incubator/


  1   2   3   >