[VOTE] Apache IoTDB 0.8.1 (incubating) RC1
Hi all, First, thanks to all of you for the support. This is my first time to be as a RM of Apache project and I want to thank all guys. It's because all of you are so patient to answer my question that I can do this release. Special thanks go to our Mentors, our committers, and a lot of documents from PLC4X, Apache, Spark, etc.. Apache IoTDB (incubating) 0.8.1 is a bug-fix version from 0.8.0. You can get its mainly changes from [5]. Apache IoTDB (Incubating) 0.8.1 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.1 Hash for the release tag: b664e8778d1221c4eb92205411e58c392214b3ab Per [3] "Before voting +1 PMC/PPMC 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-1004 [2] https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.8.1/rc1 [3] https://www.apache.org/dev/release.html#approving-a-release [4] https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release [5] https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.8.1/rc1/README.md Best, -- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院
Re: Different types of measurements that have same name in one storage group should be supported.
Hi, 1 for this. Each time series should be independent because we create them separately in IoTDB. This is due to the design of TsFile, maybe we should redesign the TsFile structure. Best, -- Jialin Qiao School of Software, Tsinghua University 乔嘉林 清华大学 软件学院 > -原始邮件- > 发件人: "Yuan Tian (Jira)" > 发送时间: 2019-09-27 20:32:00 (星期五) > 收件人: dev@iotdb.apache.org > 抄送: > 主题: [jira] [Created] (IOTDB-245) Different types of measurements that have > same name in one storage group should be supported. > > Yuan Tian created IOTDB-245: > --- > > Summary: Different types of measurements that have same name in > one storage group should be supported. > Key: IOTDB-245 > URL: https://issues.apache.org/jira/browse/IOTDB-245 > Project: Apache IoTDB > Issue Type: Improvement > Reporter: Yuan Tian > > > If we have two devices named d1 and d2, and both of them have a sensor named > s1, d1.s1 and d2.s1 must have the same type in current version. So if you > really have d1.s1 which has float type and d2.s1 which has int32 type, you > have to separate them into two different storage groups which is unreasonable. > > So we want to remove the restriction about measurements' type of same name in > one storage group. > > > > -- > This message was sent by Atlassian Jira > (v8.3.4#803005)
Re: Release of 0.8.1
Hi, > gpg: data source: http://pgp.mit.edu:11371 Did you try hkps://keys.openpgp.org that seems to be the preferred key server these days. Thanks,. Justin
Re: Release of 0.8.1
Hi, > And looking at the page, it says "Pre-release" on that page for the given RC … Yep because I changed it to say that :-) Thanks, Justin
Re: Release of 0.8.1
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 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" < >>
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 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" < >> jus...@classsoftware.com>: >> > >> > 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
Re: Release of 0.8.1
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) > > 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: Possible "problem" with the website
Hi, Hm.. I quickly search some sentences using Google. Indeed, if the contents are loaded by JS (actually the contents are at the github repo/docs/*.md), then they will not be indexed. Any Suggestions? @Zesong @Yi Xu? By the way, I think the website of PLC4x is good, except a minor issue: on page [1], if I scroll down the page, then the horizontal table of content will cover some contents ... especially for the first chapter (Preparing your system for being able to release)... [1] https://plc4x.apache.org/developers/release.html Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Christofer Dutz 于2019年9月27日周五 下午9:41写道： > Hi all, > > today we were discussing things in the PLC4X project especially because > our website looks so crappy. > Julian mentioned the IoTDB website being nice and built with Vue … so I > thought: Isn’t Vue one of these “compile to JS” technologies? > So I checked and indeed it is. > > So the next thing I checked is that usually Google doesn’t index such > sites and indeed I took some sentences of the website and searched for them > and these couldn’t be found. > > I thing not having the projects website found by google could be quite a > problem. > > Chris >
Re: Release of 0.8.1
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
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 > >
Possible "problem" with the website
Hi all, today we were discussing things in the PLC4X project especially because our website looks so crappy. Julian mentioned the IoTDB website being nice and built with Vue … so I thought: Isn’t Vue one of these “compile to JS” technologies? So I checked and indeed it is. So the next thing I checked is that usually Google doesn’t index such sites and indeed I took some sentences of the website and searched for them and these couldn’t be found. I thing not having the projects website found by google could be quite a problem. Chris
[jira] [Created] (IOTDB-245) Different types of measurements that have same name in one storage group should be supported.
Yuan Tian created IOTDB-245: --- Summary: Different types of measurements that have same name in one storage group should be supported. Key: IOTDB-245 URL: https://issues.apache.org/jira/browse/IOTDB-245 Project: Apache IoTDB Issue Type: Improvement Reporter: Yuan Tian If we have two devices named d1 and d2, and both of them have a sensor named s1, d1.s1 and d2.s1 must have the same type in current version. So if you really have d1.s1 which has float type and d2.s1 which has int32 type, you have to separate them into two different storage groups which is unreasonable. So we want to remove the restriction about measurements' type of same name in one storage group. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: Release of 0.8.1
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
And looking at the page, it says "Pre-release" on that page for the given RC ... Chris Am 27.09.19, 11:13 schrieb "Justin Mclean" : Hi, OK this is not ideal: https://github.com/apache/incubator-iotdb/releases/tag/release%2F0.8.1 Because we haven't voted on the release yet, you can only release artefacts once you have voted on them. I’ve marked it as “pre-release” to hopefully stop any confusion that it has actually been released. Thanks, Justin
Re: Release of 0.8.1
Definitely not. This is a problem with Github ... manually doing everything the release plugin does, just to avoid a problem with an external Non ASF mirror is definitely not anything I would be willing to do. The release plugin is built to make correct releases (That’s what it was created for). We could try to use this: http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html#remoteTagging To disable the tagging. But if that doesn't work, no idea. Chris 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
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
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. Chris Am 27.09.19, 11:13 schrieb "Justin Mclean" : Hi, OK this is not ideal: https://github.com/apache/incubator-iotdb/releases/tag/release%2F0.8.1 Because we haven't voted on the release yet, you can only release artefacts once you have voted on them. I’ve marked it as “pre-release” to hopefully stop any confusion that it has actually been released. Thanks, Justin
Re: Release of 0.8.1
Hi, OK this is not ideal: https://github.com/apache/incubator-iotdb/releases/tag/release%2F0.8.1 Because we haven't voted on the release yet, you can only release artefacts once you have voted on them. I’ve marked it as “pre-release” to hopefully stop any confusion that it has actually been released. Thanks, Justin
Re: Release of 0.8.1
Hi,
Well well, I know why I can not find the files from repository.apache.org,
because I did not login on the website..
The document of PLC4x has pointed out that:
> After the build it is important to log in to Nexus at
https://repository.apache.org/, select Staging Repositories and find the
repository with the name: orgapacheplc4x-{somenumber}.
Sorry to make trouble to the mail list...
Best,
---
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Xiangdong Huang 于2019年9月27日周五 下午4:23写道：
> Hi,
>
> Something to correct:
>
> If I check the rel/0.8 branch in gitbox repo [1], I can find the
> commitlogs that maven release plugin generated.
>
> [1]
> https://gitbox.apache.org/repos/asf?p=incubator-iotdb.git;a=shortlog;h=refs/heads/rel/0.8
>
>
> But still do not know why repository.apache.org and
> dist.apache.org/repos/dist/dev/incubator/iotdb/ have no new files..
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
> 黄向东
> 清华大学 软件学院
>
>
> Xiangdong Huang 于2019年9月27日周五 下午4:12写道：
>
>> Hi Chris,
>>
>> Actually now I still meet some issues..
>>
>> > "git remote set-url
>> https://gitbox.apache.org/repos/asf/incubator-iotdb.git;
>>
>> do you mean: git remote set-url --push origin
>> https://gitbox.apache.org/repos/asf/incubator-iotdb.git ?
>> (But I think `mvn release:prepare` command choose the git url according
>> SCM in pom.xml rather than .git files..)
>>
>> I have not try it, but just now I tried to change the scm in the pom as:
>>
>>
>> scm:git:ssh://
>> g...@github.com/apache/incubator-iotdb.git
>> scm:git:ssh://
>> g...@github.com/apache/incubator-iotdb.git
>> ssh://g...@github.com:apache/incubator-iotdb.git
>> rel/0.8
>>
>>
>> It works for pushing commits (two commitlogs: [maven-release-plugin]
>> prepare release release/0.8.1 and [maven-release-plugin] prepare for next
>> development iteration)
>> and create a tag (release-0.8.1) on the remote successfully.
>>
>> However, when I check gitbox repo (
>> https://gitbox.apache.org/repos/asf?p=incubator-iotdb.git;a=shortlog),
>> there is no commits
>>
>>
>> Then I choose to omit it to try the next step: $mvn release:perform
>> -DreleaseProfiles=apache-release
>>
>> Well, it tooks me about 46 mins to upload jars, asc, zip, pom files to
>> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/iotdb/iotdb-distribution/0.8.1/
>>
>>
>> However, after that, when I check https://repository.apache.org and
>> https://dist.apache.org/repos/dist/dev/incubator/iotdb/, I can not find
>> any new files... :(
>>
>> Hm... so, now I do not know which step is incorrect.
>>
>> The result of running `mvn release:perform` is:
>>
>> [INFO]
>> [INFO] Apache IoTDB (incubating) Project Parent POM 0.8.2-SNAPSHOT
>> SUCCESS [46:44 min]
>> [INFO] TsFile . SKIPPED
>> [INFO] Service-rpc SKIPPED
>> [INFO] IoTDB Jdbc . SKIPPED
>> [INFO] IoTDB Client ... SKIPPED
>> [INFO] IoTDB Server ... SKIPPED
>> [INFO] IoTDB Examples . SKIPPED
>> [INFO] IoTDB-Kafka Examples ... SKIPPED
>> [INFO] IoTDB-RocketMQ Examples SKIPPED
>> [INFO] IoTDB Grafana .. SKIPPED
>> [INFO] IoTDB Spark-TsFile . SKIPPED
>> [INFO] IoTDB Distribution 0.8.2-SNAPSHOT .. SKIPPED
>> [INFO]
>>
>> [INFO] BUILD SUCCESS
>> [INFO]
>>
>> [INFO] Total time: 46:45 min
>> [INFO] Finished at: 2019-09-27T15:34:53+08:00
>> [INFO]
>>
>>
>> Best,
>> ---
>> Xiangdong Huang
>> School of Software, Tsinghua University
>>
>> 黄向东
>> 清华大学 软件学院
>>
>>
>> Christofer Dutz 于2019年9月27日周五 下午3:33写道：
>>
>>> Hi Xiangdong,
>>>
>>> this happens when the release plugin tries to commit and push the
>>> changes it does during the release.
>>> It changes the versions to the release versions and commits that and
>>> then changes them to the next development version and then commits a second
>>> time.
>>> There seem to be issues with the credentials for pushing the changes. I
>>> usually use the gitbox repo which works fine with username+password or when
>>> using github I use the ssh key authentication.
>>> I guess you're using github with 2FA and that could be a problem.
>>>
>>> Try the following command:
>>>
>>> "git remote set-url
>>> https://gitbox.apache.org/repos/asf/incubator-iotdb.git;
>>>
>>> And then re-try. But first you should probably undo the changes
Re: [jira] [Created] (IOTDB-244) wrong duplicated columns query result
Hi,
I would choose the latter. Reducing unnecessary network traffic sounds more
attractive to me, besides, this may save a lot memory when the fetch size is
quite large.
| |
Tian Jiang
|
|
jt2594...@163.com
|
签名由网易邮箱大师定制
On 9/27/2019 16:22，Lei Rui wrote：
Hi，
I find the bug and the cause is that there is divergence between the server and
the client in treating queries with duplicated columns.
For example, I query "select s0,s0,s0,s1 from root.vehicle.d0",
The server returns the result with duplicated fields as queried.
[root.vehicle.d0.s0, root.vehicle.d0.s0, root.vehicle.d0.s0, root.vehicle.d0.s1]
However, the client assumes that the returned result has been deduplicated,
[root.vehicle.d0.s0, root.vehicle.d0.s1]
thus using a structure called `columnInfoMap` in the `IoTDBQueryResultSet`.
Before fixing this bug, we should decide who handles the duplication?
The server returns a complete result and the client just need to take,
or the server returns deduplicated result and the client do additional map task?
Lei Rui
On 9/27/2019 16:09，Lei Rui (Jira) wrote：
Lei Rui created IOTDB-244:
-
Summary: wrong duplicated columns query result
Key: IOTDB-244
URL: https://issues.apache.org/jira/browse/IOTDB-244
Project: Apache IoTDB
Issue Type: Bug
Reporter: Lei Rui
I use the following sql to insert data,
{code:java}
SET STORAGE GROUP TO root.vehicle.d0
SET STORAGE GROUP TO root.vehicle.d1
CREATE TIMESERIES root.vehicle.d0.s0 WITH DATATYPE=INT32, ENCODING=RLE
CREATE TIMESERIES root.vehicle.d0.s1 WITH DATATYPE=INT64, ENCODING=RLE
CREATE TIMESERIES root.vehicle.d0.s2 WITH DATATYPE=FLOAT, ENCODING=RLE
CREATE TIMESERIES root.vehicle.d0.s3 WITH DATATYPE=TEXT, ENCODING=PLAIN
CREATE TIMESERIES root.vehicle.d0.s4 WITH DATATYPE=BOOLEAN, ENCODING=PLAIN
CREATE TIMESERIES root.vehicle.d1.s0 WITH DATATYPE=INT32, ENCODING=RLEinsert
into root.vehicle.d0(timestamp,s0) values(1,101)
insert into root.vehicle.d0(timestamp,s0) values(2,198)
insert into root.vehicle.d0(timestamp,s0) values(100,99)
insert into root.vehicle.d0(timestamp,s0) values(101,99)
insert into root.vehicle.d0(timestamp,s0) values(102,80)
insert into root.vehicle.d0(timestamp,s0) values(103,99)
insert into root.vehicle.d0(timestamp,s0) values(104,90)
insert into root.vehicle.d0(timestamp,s0) values(105,99)
insert into root.vehicle.d0(timestamp,s0) values(106,99)
insert into root.vehicle.d0(timestamp,s0) values(2,1)
insert into root.vehicle.d0(timestamp,s0) values(50,1)
insert into root.vehicle.d0(timestamp,s0) values(1000,2)insert into
root.vehicle.d0(timestamp,s1) values(1,1101)
insert into root.vehicle.d0(timestamp,s1) values(2,198)
insert into root.vehicle.d0(timestamp,s1) values(100,199)
insert into root.vehicle.d0(timestamp,s1) values(101,199)
insert into root.vehicle.d0(timestamp,s1) values(102,180)
insert into root.vehicle.d0(timestamp,s1) values(103,199)
insert into root.vehicle.d0(timestamp,s1) values(104,190)
insert into root.vehicle.d0(timestamp,s1) values(105,199)
insert into root.vehicle.d0(timestamp,s1) values(2,4)
insert into root.vehicle.d0(timestamp,s1) values(50,5)
insert into root.vehicle.d0(timestamp,s1) values(1000,5)insert into
root.vehicle.d0(timestamp,s2) values(1000,5)
insert into root.vehicle.d0(timestamp,s2) values(2,2.22)
insert into root.vehicle.d0(timestamp,s2) values(3,3.33)
insert into root.vehicle.d0(timestamp,s2) values(4,4.44)
insert into root.vehicle.d0(timestamp,s2) values(102,10.00)
insert into root.vehicle.d0(timestamp,s2) values(105,11.11)
insert into root.vehicle.d0(timestamp,s2) values(1000,1000.11)insert into
root.vehicle.d0(timestamp,s3) values(60,'a')
insert into root.vehicle.d0(timestamp,s3) values(70,'b')
insert into root.vehicle.d0(timestamp,s3) values(80,'c')
insert into root.vehicle.d0(timestamp,s3) values(101,'d')
insert into root.vehicle.d0(timestamp,s3) values(102,'f')insert into
root.vehicle.d1(timestamp,s0) values(1,999)
insert into root.vehicle.d1(timestamp,s0) values(1000,888)insert into
root.vehicle.d0(timestamp,s1) values(2000-01-01T08:00:00+08:00, 100)
insert into root.vehicle.d0(timestamp,s3) values(2000-01-01T08:00:00+08:00,
'good')insert into root.vehicle.d0(timestamp,s4) values(100, false)
insert into root.vehicle.d0(timestamp,s4) values(100, true)
{code}
and then I query as follows:
{code:java}
IoTDB> select s0,s0,s0,s1 from root.vehicle.d0
+---+--+--+--+--+
|
Time|root.vehicle.d0.s0|root.vehicle.d0.s0|root.vehicle.d0.s0|root.vehicle.d0.s1|
+---+--+--+--+--+
| 1970-01-01T08:00:00.001+08:00| 101| 101|
101| 101|
| 1970-01-01T08:00:00.002+08:00| 1| 1|
1| 1|
|
Re: Release of 0.8.1
Hi, Something to correct: If I check the rel/0.8 branch in gitbox repo [1], I can find the commitlogs that maven release plugin generated. [1] https://gitbox.apache.org/repos/asf?p=incubator-iotdb.git;a=shortlog;h=refs/heads/rel/0.8 But still do not know why repository.apache.org and dist.apache.org/repos/dist/dev/incubator/iotdb/ have no new files.. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Xiangdong Huang 于2019年9月27日周五 下午4:12写道： > Hi Chris, > > Actually now I still meet some issues.. > > > "git remote set-url > https://gitbox.apache.org/repos/asf/incubator-iotdb.git; > > do you mean: git remote set-url --push origin > https://gitbox.apache.org/repos/asf/incubator-iotdb.git ? > (But I think `mvn release:prepare` command choose the git url according > SCM in pom.xml rather than .git files..) > > I have not try it, but just now I tried to change the scm in the pom as: > > > scm:git:ssh:// > g...@github.com/apache/incubator-iotdb.git > scm:git:ssh:// > g...@github.com/apache/incubator-iotdb.git > ssh://g...@github.com:apache/incubator-iotdb.git > rel/0.8 > > > It works for pushing commits (two commitlogs: [maven-release-plugin] > prepare release release/0.8.1 and [maven-release-plugin] prepare for next > development iteration) > and create a tag (release-0.8.1) on the remote successfully. > > However, when I check gitbox repo ( > https://gitbox.apache.org/repos/asf?p=incubator-iotdb.git;a=shortlog), > there is no commits > > > Then I choose to omit it to try the next step: $mvn release:perform > -DreleaseProfiles=apache-release > > Well, it tooks me about 46 mins to upload jars, asc, zip, pom files to > https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/iotdb/iotdb-distribution/0.8.1/ > > > However, after that, when I check https://repository.apache.org and > https://dist.apache.org/repos/dist/dev/incubator/iotdb/, I can not find > any new files... :( > > Hm... so, now I do not know which step is incorrect. > > The result of running `mvn release:perform` is: > > [INFO] > [INFO] Apache IoTDB (incubating) Project Parent POM 0.8.2-SNAPSHOT SUCCESS > [46:44 min] > [INFO] TsFile . SKIPPED > [INFO] Service-rpc SKIPPED > [INFO] IoTDB Jdbc . SKIPPED > [INFO] IoTDB Client ... SKIPPED > [INFO] IoTDB Server ... SKIPPED > [INFO] IoTDB Examples . SKIPPED > [INFO] IoTDB-Kafka Examples ... SKIPPED > [INFO] IoTDB-RocketMQ Examples SKIPPED > [INFO] IoTDB Grafana .. SKIPPED > [INFO] IoTDB Spark-TsFile . SKIPPED > [INFO] IoTDB Distribution 0.8.2-SNAPSHOT .. SKIPPED > [INFO] > > [INFO] BUILD SUCCESS > [INFO] > > [INFO] Total time: 46:45 min > [INFO] Finished at: 2019-09-27T15:34:53+08:00 > [INFO] > > > Best, > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > Christofer Dutz 于2019年9月27日周五 下午3:33写道： > >> Hi Xiangdong, >> >> this happens when the release plugin tries to commit and push the changes >> it does during the release. >> It changes the versions to the release versions and commits that and then >> changes them to the next development version and then commits a second time. >> There seem to be issues with the credentials for pushing the changes. I >> usually use the gitbox repo which works fine with username+password or when >> using github I use the ssh key authentication. >> I guess you're using github with 2FA and that could be a problem. >> >> Try the following command: >> >> "git remote set-url >> https://gitbox.apache.org/repos/asf/incubator-iotdb.git; >> >> And then re-try. But first you should probably undo the changes from your >> first attempt (Hopefully with you having no uncommitted changes) >> >> >> Chris >> >> Am 27.09.19, 08:04 schrieb "Xiangdong Huang" : >> >> Hi, >> >> @Justin, many thanks! I have already upload the updated KEYS there. >> >> Now I want to try maven plugin `mvn release:prepare` to automatically >> finish some work, like create a tag on github.. >> However, it fails because: >> >> [ERROR] Failed to execute goal >> org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare >> (default-cli) >> on project iotdb-parent: Unable to tag SCM >> [ERROR] Provider message: >> [ERROR] The git-push command failed. >> [ERROR] Command output: >>
Re: [jira] [Created] (IOTDB-244) wrong duplicated columns query result
Hi，
I find the bug and the cause is that there is divergence between the server and
the client in treating queries with duplicated columns.
For example, I query "select s0,s0,s0,s1 from root.vehicle.d0",
The server returns the result with duplicated fields as queried.
[root.vehicle.d0.s0, root.vehicle.d0.s0, root.vehicle.d0.s0, root.vehicle.d0.s1]
However, the client assumes that the returned result has been deduplicated,
[root.vehicle.d0.s0, root.vehicle.d0.s1]
thus using a structure called `columnInfoMap` in the `IoTDBQueryResultSet`.
Before fixing this bug, we should decide who handles the duplication?
The server returns a complete result and the client just need to take,
or the server returns deduplicated result and the client do additional map task?
Lei Rui
On 9/27/2019 16:09，Lei Rui (Jira) wrote：
Lei Rui created IOTDB-244:
-
Summary: wrong duplicated columns query result
Key: IOTDB-244
URL: https://issues.apache.org/jira/browse/IOTDB-244
Project: Apache IoTDB
Issue Type: Bug
Reporter: Lei Rui
I use the following sql to insert data,
{code:java}
SET STORAGE GROUP TO root.vehicle.d0
SET STORAGE GROUP TO root.vehicle.d1
CREATE TIMESERIES root.vehicle.d0.s0 WITH DATATYPE=INT32, ENCODING=RLE
CREATE TIMESERIES root.vehicle.d0.s1 WITH DATATYPE=INT64, ENCODING=RLE
CREATE TIMESERIES root.vehicle.d0.s2 WITH DATATYPE=FLOAT, ENCODING=RLE
CREATE TIMESERIES root.vehicle.d0.s3 WITH DATATYPE=TEXT, ENCODING=PLAIN
CREATE TIMESERIES root.vehicle.d0.s4 WITH DATATYPE=BOOLEAN, ENCODING=PLAIN
CREATE TIMESERIES root.vehicle.d1.s0 WITH DATATYPE=INT32, ENCODING=RLEinsert
into root.vehicle.d0(timestamp,s0) values(1,101)
insert into root.vehicle.d0(timestamp,s0) values(2,198)
insert into root.vehicle.d0(timestamp,s0) values(100,99)
insert into root.vehicle.d0(timestamp,s0) values(101,99)
insert into root.vehicle.d0(timestamp,s0) values(102,80)
insert into root.vehicle.d0(timestamp,s0) values(103,99)
insert into root.vehicle.d0(timestamp,s0) values(104,90)
insert into root.vehicle.d0(timestamp,s0) values(105,99)
insert into root.vehicle.d0(timestamp,s0) values(106,99)
insert into root.vehicle.d0(timestamp,s0) values(2,1)
insert into root.vehicle.d0(timestamp,s0) values(50,1)
insert into root.vehicle.d0(timestamp,s0) values(1000,2)insert into
root.vehicle.d0(timestamp,s1) values(1,1101)
insert into root.vehicle.d0(timestamp,s1) values(2,198)
insert into root.vehicle.d0(timestamp,s1) values(100,199)
insert into root.vehicle.d0(timestamp,s1) values(101,199)
insert into root.vehicle.d0(timestamp,s1) values(102,180)
insert into root.vehicle.d0(timestamp,s1) values(103,199)
insert into root.vehicle.d0(timestamp,s1) values(104,190)
insert into root.vehicle.d0(timestamp,s1) values(105,199)
insert into root.vehicle.d0(timestamp,s1) values(2,4)
insert into root.vehicle.d0(timestamp,s1) values(50,5)
insert into root.vehicle.d0(timestamp,s1) values(1000,5)insert into
root.vehicle.d0(timestamp,s2) values(1000,5)
insert into root.vehicle.d0(timestamp,s2) values(2,2.22)
insert into root.vehicle.d0(timestamp,s2) values(3,3.33)
insert into root.vehicle.d0(timestamp,s2) values(4,4.44)
insert into root.vehicle.d0(timestamp,s2) values(102,10.00)
insert into root.vehicle.d0(timestamp,s2) values(105,11.11)
insert into root.vehicle.d0(timestamp,s2) values(1000,1000.11)insert into
root.vehicle.d0(timestamp,s3) values(60,'a')
insert into root.vehicle.d0(timestamp,s3) values(70,'b')
insert into root.vehicle.d0(timestamp,s3) values(80,'c')
insert into root.vehicle.d0(timestamp,s3) values(101,'d')
insert into root.vehicle.d0(timestamp,s3) values(102,'f')insert into
root.vehicle.d1(timestamp,s0) values(1,999)
insert into root.vehicle.d1(timestamp,s0) values(1000,888)insert into
root.vehicle.d0(timestamp,s1) values(2000-01-01T08:00:00+08:00, 100)
insert into root.vehicle.d0(timestamp,s3) values(2000-01-01T08:00:00+08:00,
'good')insert into root.vehicle.d0(timestamp,s4) values(100, false)
insert into root.vehicle.d0(timestamp,s4) values(100, true)
{code}
and then I query as follows:
{code:java}
IoTDB> select s0,s0,s0,s1 from root.vehicle.d0
+---+--+--+--+--+
|
Time|root.vehicle.d0.s0|root.vehicle.d0.s0|root.vehicle.d0.s0|root.vehicle.d0.s1|
+---+--+--+--+--+
| 1970-01-01T08:00:00.001+08:00| 101| 101|
101| 101|
| 1970-01-01T08:00:00.002+08:00| 1| 1|
1| 1|
| 1970-01-01T08:00:00.050+08:00| 1| 1|
1| 1|
| 1970-01-01T08:00:00.100+08:00|99|99|
99|99|
|
Re: Release of 0.8.1
Hi Chris, Actually now I still meet some issues.. > "git remote set-url https://gitbox.apache.org/repos/asf/incubator-iotdb.git; do you mean: git remote set-url --push origin https://gitbox.apache.org/repos/asf/incubator-iotdb.git ? (But I think `mvn release:prepare` command choose the git url according SCM in pom.xml rather than .git files..) I have not try it, but just now I tried to change the scm in the pom as: scm:git:ssh://g...@github.com/apache/incubator-iotdb.git scm:git:ssh:// g...@github.com/apache/incubator-iotdb.git ssh://g...@github.com:apache/incubator-iotdb.git rel/0.8 It works for pushing commits (two commitlogs: [maven-release-plugin] prepare release release/0.8.1 and [maven-release-plugin] prepare for next development iteration) and create a tag (release-0.8.1) on the remote successfully. However, when I check gitbox repo ( https://gitbox.apache.org/repos/asf?p=incubator-iotdb.git;a=shortlog), there is no commits Then I choose to omit it to try the next step: $mvn release:perform -DreleaseProfiles=apache-release Well, it tooks me about 46 mins to upload jars, asc, zip, pom files to https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/iotdb/iotdb-distribution/0.8.1/ However, after that, when I check https://repository.apache.org and https://dist.apache.org/repos/dist/dev/incubator/iotdb/, I can not find any new files... :( Hm... so, now I do not know which step is incorrect. The result of running `mvn release:perform` is: [INFO] [INFO] Apache IoTDB (incubating) Project Parent POM 0.8.2-SNAPSHOT SUCCESS [46:44 min] [INFO] TsFile . SKIPPED [INFO] Service-rpc SKIPPED [INFO] IoTDB Jdbc . SKIPPED [INFO] IoTDB Client ... SKIPPED [INFO] IoTDB Server ... SKIPPED [INFO] IoTDB Examples . SKIPPED [INFO] IoTDB-Kafka Examples ... SKIPPED [INFO] IoTDB-RocketMQ Examples SKIPPED [INFO] IoTDB Grafana .. SKIPPED [INFO] IoTDB Spark-TsFile . SKIPPED [INFO] IoTDB Distribution 0.8.2-SNAPSHOT .. SKIPPED [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 46:45 min [INFO] Finished at: 2019-09-27T15:34:53+08:00 [INFO] Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Christofer Dutz 于2019年9月27日周五 下午3:33写道： > Hi Xiangdong, > > this happens when the release plugin tries to commit and push the changes > it does during the release. > It changes the versions to the release versions and commits that and then > changes them to the next development version and then commits a second time. > There seem to be issues with the credentials for pushing the changes. I > usually use the gitbox repo which works fine with username+password or when > using github I use the ssh key authentication. > I guess you're using github with 2FA and that could be a problem. > > Try the following command: > > "git remote set-url > https://gitbox.apache.org/repos/asf/incubator-iotdb.git; > > And then re-try. But first you should probably undo the changes from your > first attempt (Hopefully with you having no uncommitted changes) > > > Chris > > Am 27.09.19, 08:04 schrieb "Xiangdong Huang" : > > Hi, > > @Justin, many thanks! I have already upload the updated KEYS there. > > Now I want to try maven plugin `mvn release:prepare` to automatically > finish some work, like create a tag on github.. > However, it fails because: > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare > (default-cli) > on project iotdb-parent: Unable to tag SCM > [ERROR] Provider message: > [ERROR] The git-push command failed. > [ERROR] Command output: > [ERROR] remote: Permission to apache/incubator-iotdb.git denied to > jixuan1989. (Ah, this is my github account.) > [ERROR] fatal: unable to access ' > https://github.com/apache/incubator-iotdb.git/': The requested URL > returned > error: 403 > > I have set the SSH and GPG key on my Github's account settings. > > Best, > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > Justin Mclean 于2019年9月27日周五 下午12:09写道： > > > HI, > > > > > 1. Do I need to change the version from 0.8.1-SNAPSHOT to 0.8.1-RC1 > > > (RC2,..., RCn) first, and then 0.8.1 second? > > >
[jira] [Created] (IOTDB-244) wrong duplicated columns query result
Lei Rui created IOTDB-244:
-
Summary: wrong duplicated columns query result
Key: IOTDB-244
URL: https://issues.apache.org/jira/browse/IOTDB-244
Project: Apache IoTDB
Issue Type: Bug
Reporter: Lei Rui
I use the following sql to insert data,
{code:java}
SET STORAGE GROUP TO root.vehicle.d0
SET STORAGE GROUP TO root.vehicle.d1
CREATE TIMESERIES root.vehicle.d0.s0 WITH DATATYPE=INT32, ENCODING=RLE
CREATE TIMESERIES root.vehicle.d0.s1 WITH DATATYPE=INT64, ENCODING=RLE
CREATE TIMESERIES root.vehicle.d0.s2 WITH DATATYPE=FLOAT, ENCODING=RLE
CREATE TIMESERIES root.vehicle.d0.s3 WITH DATATYPE=TEXT, ENCODING=PLAIN
CREATE TIMESERIES root.vehicle.d0.s4 WITH DATATYPE=BOOLEAN, ENCODING=PLAIN
CREATE TIMESERIES root.vehicle.d1.s0 WITH DATATYPE=INT32, ENCODING=RLEinsert
into root.vehicle.d0(timestamp,s0) values(1,101)
insert into root.vehicle.d0(timestamp,s0) values(2,198)
insert into root.vehicle.d0(timestamp,s0) values(100,99)
insert into root.vehicle.d0(timestamp,s0) values(101,99)
insert into root.vehicle.d0(timestamp,s0) values(102,80)
insert into root.vehicle.d0(timestamp,s0) values(103,99)
insert into root.vehicle.d0(timestamp,s0) values(104,90)
insert into root.vehicle.d0(timestamp,s0) values(105,99)
insert into root.vehicle.d0(timestamp,s0) values(106,99)
insert into root.vehicle.d0(timestamp,s0) values(2,1)
insert into root.vehicle.d0(timestamp,s0) values(50,1)
insert into root.vehicle.d0(timestamp,s0) values(1000,2)insert into
root.vehicle.d0(timestamp,s1) values(1,1101)
insert into root.vehicle.d0(timestamp,s1) values(2,198)
insert into root.vehicle.d0(timestamp,s1) values(100,199)
insert into root.vehicle.d0(timestamp,s1) values(101,199)
insert into root.vehicle.d0(timestamp,s1) values(102,180)
insert into root.vehicle.d0(timestamp,s1) values(103,199)
insert into root.vehicle.d0(timestamp,s1) values(104,190)
insert into root.vehicle.d0(timestamp,s1) values(105,199)
insert into root.vehicle.d0(timestamp,s1) values(2,4)
insert into root.vehicle.d0(timestamp,s1) values(50,5)
insert into root.vehicle.d0(timestamp,s1) values(1000,5)insert into
root.vehicle.d0(timestamp,s2) values(1000,5)
insert into root.vehicle.d0(timestamp,s2) values(2,2.22)
insert into root.vehicle.d0(timestamp,s2) values(3,3.33)
insert into root.vehicle.d0(timestamp,s2) values(4,4.44)
insert into root.vehicle.d0(timestamp,s2) values(102,10.00)
insert into root.vehicle.d0(timestamp,s2) values(105,11.11)
insert into root.vehicle.d0(timestamp,s2) values(1000,1000.11)insert into
root.vehicle.d0(timestamp,s3) values(60,'a')
insert into root.vehicle.d0(timestamp,s3) values(70,'b')
insert into root.vehicle.d0(timestamp,s3) values(80,'c')
insert into root.vehicle.d0(timestamp,s3) values(101,'d')
insert into root.vehicle.d0(timestamp,s3) values(102,'f')insert into
root.vehicle.d1(timestamp,s0) values(1,999)
insert into root.vehicle.d1(timestamp,s0) values(1000,888)insert into
root.vehicle.d0(timestamp,s1) values(2000-01-01T08:00:00+08:00, 100)
insert into root.vehicle.d0(timestamp,s3) values(2000-01-01T08:00:00+08:00,
'good')insert into root.vehicle.d0(timestamp,s4) values(100, false)
insert into root.vehicle.d0(timestamp,s4) values(100, true)
{code}
and then I query as follows:
{code:java}
IoTDB> select s0,s0,s0,s1 from root.vehicle.d0
+---+--+--+--+--+
|
Time|root.vehicle.d0.s0|root.vehicle.d0.s0|root.vehicle.d0.s0|root.vehicle.d0.s1|
+---+--+--+--+--+
| 1970-01-01T08:00:00.001+08:00| 101| 101|
101| 101|
| 1970-01-01T08:00:00.002+08:00| 1| 1|
1| 1|
| 1970-01-01T08:00:00.050+08:00| 1| 1|
1| 1|
| 1970-01-01T08:00:00.100+08:00|99|99|
99|99|
| 1970-01-01T08:00:00.101+08:00|99|99|
99|99|
| 1970-01-01T08:00:00.102+08:00|80|80|
80|80|
| 1970-01-01T08:00:00.103+08:00|99|99|
99|99|
| 1970-01-01T08:00:00.104+08:00|90|90|
90|90|
| 1970-01-01T08:00:00.105+08:00|99|99|
99|99|
| 1970-01-01T08:00:00.106+08:00|99|99|
99|99|
| 1970-01-01T08:00:01.000+08:00| 2| 2|
Re: Release of 0.8.1
Hi Xiangdong, this happens when the release plugin tries to commit and push the changes it does during the release. It changes the versions to the release versions and commits that and then changes them to the next development version and then commits a second time. There seem to be issues with the credentials for pushing the changes. I usually use the gitbox repo which works fine with username+password or when using github I use the ssh key authentication. I guess you're using github with 2FA and that could be a problem. Try the following command: "git remote set-url https://gitbox.apache.org/repos/asf/incubator-iotdb.git; And then re-try. But first you should probably undo the changes from your first attempt (Hopefully with you having no uncommitted changes) Chris Am 27.09.19, 08:04 schrieb "Xiangdong Huang" : Hi, @Justin, many thanks! I have already upload the updated KEYS there. Now I want to try maven plugin `mvn release:prepare` to automatically finish some work, like create a tag on github.. However, it fails because: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare (default-cli) on project iotdb-parent: Unable to tag SCM [ERROR] Provider message: [ERROR] The git-push command failed. [ERROR] Command output: [ERROR] remote: Permission to apache/incubator-iotdb.git denied to jixuan1989. (Ah, this is my github account.) [ERROR] fatal: unable to access ' https://github.com/apache/incubator-iotdb.git/': The requested URL returned error: 403 I have set the SSH and GPG key on my Github's account settings. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Justin Mclean 于2019年9月27日周五 下午12:09写道： > HI, > > > 1. Do I need to change the version from 0.8.1-SNAPSHOT to 0.8.1-RC1 > > (RC2,..., RCn) first, and then 0.8.1 second? > > I would just change it to 0.8.1 and name the files / vote emails RC1, RC2 > etc as needed. > > > 2. @Julian, Would you share the commands that you used when releasing > 0.8.0 > > with me? It is very helpful for me. :D. > > Mavin is not an official release area and can be done after the official > source release is voted on. > > You just need to put the official source release here [1]. You would also > need to update the KEYS file there. > > Thanks, > Justin > > 1. https://dist.apache.org/repos/dist/dev/incubator/iotdb/
Re: Release of 0.8.1
Hi all, But the maven release tools are what actually produce the artifacts that we are going to vote on. So yes you would do the maven release: This will stage the maven artifacts and produce a source distribution with pgp signatures and hashes in the root target folder. These files you will have to manually commit to the official release svn repo and start a vote on that. Chris Am 27.09.19, 06:09 schrieb "Justin Mclean" : HI, > 1. Do I need to change the version from 0.8.1-SNAPSHOT to 0.8.1-RC1 > (RC2,..., RCn) first, and then 0.8.1 second? I would just change it to 0.8.1 and name the files / vote emails RC1, RC2 etc as needed. > 2. @Julian, Would you share the commands that you used when releasing 0.8.0 > with me? It is very helpful for me. :D. Mavin is not an official release area and can be done after the official source release is voted on. You just need to put the official source release here [1]. You would also need to update the KEYS file there. Thanks, Justin 1. https://dist.apache.org/repos/dist/dev/incubator/iotdb/
Re: Release of 0.8.1
The naming is usually handled automatically by the release plugin (Except in
non pom.xml files like documentation and RELEASE_NOTES)
So if you have references to the current SNAPSHOT version in your
RELEASE_NOTES, I would remove the SNAPSHOT manually before running mvn
release:prepare.
(Just stumbled into that yesterday and had to re-do my RC)
Chris
Am 27.09.19, 05:51 schrieb "Xiangdong Huang" :
Hi,
Ask for help about some questions.
1. Do I need to change the version from 0.8.1-SNAPSHOT to 0.8.1-RC1
(RC2,..., RCn) first, and then 0.8.1 second?
2. @Julian, Would you share the commands that you used when releasing 0.8.0
with me? It is very helpful for me. :D.
(commands like what PLC4X release document said, `mvn release:branch -P
with-cpp,with-dotnet,with-java,with-proxies,with-python,with-sandbox
-DbranchName=rel/{minor-version} -DautoVersionSubmodules=true`)
Best,
---
Xiangdong Huang
School of Software, Tsinghua University
黄向东
清华大学 软件学院
Xiangdong Huang 于2019年9月27日周五 上午1:19写道：
> Hi,
>
> well, after a lot of cherry-pick operations, the following bug-fix prs
> are involved.
>
> - [IOTDB-172] bug in updating startTime and endTime in TsFileResource
>
> - Abnormal publishing of sequence and unsequence data folders in
> DirectoryManager
>
> - fix a bug in TimeRange's intersects function
>
> - [IOTDB-202] fix tsfile example data type
>
> - [IOTDB-195] Bug about 'serializedSize' in ChunkGroupMetaData.java (for
> Chinese string)
>
> - [IOTDB-242] fix mvn integration-test failed because the files in the
> target folder changes
>
> The first two bugs are critical while others are minors.
>
>
> 4 PRs that Jialin mentioned are not included:
>
> * bug in tsfile batch write interface
> * https://github.com/apache/incubator-iotdb/pull/344
> * https://github.com/apache/incubator-iotdb/pull/385
>
> * bug of docs (maven version)
> * https://github.com/apache/incubator-iotdb/pull/364
>
> * bug of the serialized size of String
> * https://github.com/apache/incubator-iotdb/pull/377
>
> * Bug about 'serializedSize' in ChunkGroupMetaData.java
> * https://github.com/apache/incubator-iotdb/pull/396/files
>
> The first one is a bug-fix which is not affected in 0.8;
> The 2-4 can not be included because they do not only modify source codes
> that 0.8 has, but also some files that only appears in 0.9.
> Meanwhile, because these PR only has 1~2 commits and mixed the two parts
> of modifications, just a cherry-pick operation is not enough...
> If we really want to fix that, I have to read how these PRs solve the
> problem and then put some codes into the rel/0.8 branch...
>
> Bug 2 is an error in documents, and Bug 3 and 4 will affect users if they
> use Chinese to describe a device or a measurement.
>
>
>
>
> Best,
> ---
> Xiangdong Huang
> School of Software, Tsinghua University
>
> 黄向东
> 清华大学 软件学院
>
>
> Jialin Qiao 于2019年9月26日周四 下午1:03写道：
>
>> 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
>> > > *
Re: Release of 0.8.1
Hi, I solved it by changing the SCM from https protocol to ssh protocol. (Howver I feel curious how Julian solved it for the last release..) I will submit a PR later. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Xiangdong Huang 于2019年9月27日周五 下午2:03写道： > Hi, > > @Justin, many thanks! I have already upload the updated KEYS there. > > Now I want to try maven plugin `mvn release:prepare` to automatically > finish some work, like create a tag on github.. > However, it fails because: > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare (default-cli) > on project iotdb-parent: Unable to tag SCM > [ERROR] Provider message: > [ERROR] The git-push command failed. > [ERROR] Command output: > [ERROR] remote: Permission to apache/incubator-iotdb.git denied to > jixuan1989. (Ah, this is my github account.) > [ERROR] fatal: unable to access ' > https://github.com/apache/incubator-iotdb.git/': The requested URL > returned error: 403 > > I have set the SSH and GPG key on my Github's account settings. > > Best, > --- > Xiangdong Huang > School of Software, Tsinghua University > > 黄向东 > 清华大学 软件学院 > > > Justin Mclean 于2019年9月27日周五 下午12:09写道： > >> HI, >> >> > 1. Do I need to change the version from 0.8.1-SNAPSHOT to 0.8.1-RC1 >> > (RC2,..., RCn) first, and then 0.8.1 second? >> >> I would just change it to 0.8.1 and name the files / vote emails RC1, RC2 >> etc as needed. >> >> > 2. @Julian, Would you share the commands that you used when releasing >> 0.8.0 >> > with me? It is very helpful for me. :D. >> >> Mavin is not an official release area and can be done after the official >> source release is voted on. >> >> You just need to put the official source release here [1]. You would also >> need to update the KEYS file there. >> >> Thanks, >> Justin >> >> 1. https://dist.apache.org/repos/dist/dev/incubator/iotdb/ > >
Re: Release of 0.8.1
Hi, @Justin, many thanks! I have already upload the updated KEYS there. Now I want to try maven plugin `mvn release:prepare` to automatically finish some work, like create a tag on github.. However, it fails because: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.3:prepare (default-cli) on project iotdb-parent: Unable to tag SCM [ERROR] Provider message: [ERROR] The git-push command failed. [ERROR] Command output: [ERROR] remote: Permission to apache/incubator-iotdb.git denied to jixuan1989. (Ah, this is my github account.) [ERROR] fatal: unable to access ' https://github.com/apache/incubator-iotdb.git/': The requested URL returned error: 403 I have set the SSH and GPG key on my Github's account settings. Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Justin Mclean 于2019年9月27日周五 下午12:09写道： > HI, > > > 1. Do I need to change the version from 0.8.1-SNAPSHOT to 0.8.1-RC1 > > (RC2,..., RCn) first, and then 0.8.1 second? > > I would just change it to 0.8.1 and name the files / vote emails RC1, RC2 > etc as needed. > > > 2. @Julian, Would you share the commands that you used when releasing > 0.8.0 > > with me? It is very helpful for me. :D. > > Mavin is not an official release area and can be done after the official > source release is voted on. > > You just need to put the official source release here [1]. You would also > need to update the KEYS file there. > > Thanks, > Justin > > 1. https://dist.apache.org/repos/dist/dev/incubator/iotdb/
