Re: error when connect Doris via mysql
Hi wangtie. Running and compiling Doris JDK must be consistent. You can reference the compile doc[1] to change the JDK version while compiling. [1] https://doris.apache.org/master/zh-CN/installing/compilation.html#%E4%BD%BF%E7%94%A8-docker-%E5%BC%80%E5%8F%91%E9%95%9C%E5%83%8F%E7%BC%96%E8%AF%91-%E6%8E%A8%E8%8D%90 On Mon, Dec 13, 2021 at 4:17 PM 王 铁 wrote: > Hi > > I have compiled source code with using docker image, and I have started fe > progress on one server > > when I tried to connect use : ./mysql-client -h host -P port -uroot > > there is an error shown on screen : ERROR 2013 (HY000): Lost connection to > MySQL server at 'reading initial communication packet', system error: 0 > > and in the same time , there are some warn infomation which is printed in > fe.warn.log like this > > ERROR (doris-mysql-nio-pool-8|143) > [AcceptListener.lambda$handleEvent$1():86] connect processor exception > because > java.lang.NoSuchMethodError: > java.nio.ByteBuffer.limit(I)Ljava/nio/ByteBuffer; > at > org.apache.doris.mysql.MysqlChannel.sendOnePacket(MysqlChannel.java:259) > ~[palo-fe.jar:3.4.0] > at org.apache.doris.mysql.MysqlChannel.sendAndFlush(MysqlChannel.java:265) > ~[palo-fe.jar:3.4.0] > at org.apache.doris.mysql.MysqlProto.negotiate(MysqlProto.java:169) > ~[palo-fe.jar:3.4.0] > at > org.apache.doris.mysql.nio.AcceptListener.lambda$handleEvent$1(AcceptListener.java:63) > ~[palo-fe.jar:3.4.0] > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > [?:1.8.0_121] > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > [?:1.8.0_121] > at java.lang.Thread.run(Thread.java:745) [?:1.8.0_121] > > is this an issue or my mistake ? > > thank you guys. >
Re: Re: [Discuss] Invite external collaborators with the triage role on GitHub
I'd like to join. id: qidaye Jianliang Qi On Fri, Feb 11, 2022 at 1:14 PM 陈明雨 wrote: > > Can collaborators label the PRs ?I think yes. > > > > -- > > 此致！Best Regards > 陈明雨 Mingyu Chen > > Email: > chenmin...@apache.org > > > > > > 在 2022-02-11 13:06:13，"ling miao" 写道： > >Can collaborators label the PRs ? > > > > > >Ling Miao > > > >41108453 <41108...@qq.com.invalid> 于2022年2月11日周五 12:59写道： > > > >> id:hf200012 > >> > >> > >> very good > >> > >> > >> > >> > >> > >> > >> > >> > >> -- 原始邮件 -- > >> 发件人: > >> "dev" > >> < > >> morning...@163.com>; > >> 发送时间: 2022年2月11日(星期五) 中午12:12 > >> 收件人: "doris-dev" >> > >> 主题: [Discuss] Invite external collaborators with the triage role on > >> GitHub > >> > >> > >> > >> Hi all: > >> > >> > >> I just find that we can assign external collaborators with the triage > role > >> on GitHub[1] > >> The external collaborators can assign, edit, close the issues and PRs, > but > >> without write access to the repo. > >> > >> > >> I think we can invite some people to participate in the community > building > >> as collaborators to provide some non-code collaboration, but also a good > >> reflection of everyone's contribution. > >> > >> > >> Welcome to discuss, if any of you wish to be collaborators, please leave > >> your github id. > >> > >> > >> [1] > >> > https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-AssigningexternalcollaboratorswiththetriageroleonGitHub > >> > >> > >> > >> > >> -- > >> > >> 此致！Best Regards > >> 陈明雨 Mingyu Chen > >> > >> Email: > >> chenmin...@apache.org >
Re: [VOTE] Graduate Apache Doris (Incubating) as a TLP
+1 On Fri, Apr 8, 2022 at 8:13 PM Dayue Gao wrote: > +1 for graduation > > Best Regards > Dayue Gao > > 陈明雨 于2022年4月7日周四 10:57写道： > > > Hi all, > > > > > > > > > > Apache Doris (Incubating) has been in development for over 3 years since > > it entered the Apache incubator in September 2018. > > > > During our time in the Incubator, we have learned a lot about open source > > software governance and the Apache Foundation's philosophy on managing, > > maintaining, and developing open source community. > > > > > > > > > > After a discussion[1][2] with the community, we'd like to get your vote > on > > graduating Doris as an Apache Top Level Project. > > > > > > > > > > The following is a brief overview of the progress of the Doris project > and > > community since entering the incubator. > > > > 1. Community > > > > - 9 new PPMC members were added, from five different companies, > > bringing the total number of PPMC members to 22. > > > > - 20 new Committers were added (including the new PPMC members), > > bringing the total number of Committers to 33. > > > > - The number of Contributors is now 289 and growing. > > > > - The dev@doris mailing list currently has 289 subscribers, and all > > major project discussions are happening in the dev@doris. > > > > 2. Project > > > > - 7 releases by 6 release managers. All compliance issues have been > > resolved. > > > > - Doris official website[3] is compliant with Apache Foundation > > requirements[4]. > > > > - Project maturity model can be found in [5]. > > > > - We have also created a pre-graduation Check List[6] following the > > Apache official website guidelines and are currently moving forward. > > > > > > > > > > The proposed resolution: > > > > > > > > > > > Establish the Apache Doris Project > > > > > > > > > > WHEREAS, the Board of Directors deems it to be in the best interests of > > > > the Foundation and consistent with the Foundation's purpose to establish > > > > a Project Management Committee charged with the creation and maintenance > > > > of open-source software, for distribution at no charge to the public, > > > > related to a MPP-based interactive SQL data warehousing for reporting > > > > and analysis. > > > > > > > > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee > > > > (PMC), to be known as the "Apache Doris Project", be and hereby is > > > > established pursuant to Bylaws of the Foundation; and be it further > > > > > > > > > > RESOLVED, that the Apache Doris Project be and hereby is responsible for > > > > the creation and maintenance of software related to a MPP-based > > > > interactive SQL data warehousing for reporting and analysis; and be it > > > > further > > > > > > > > > > RESOLVED, that the office of "Vice President, Apache Doris" be and > > > > hereby is created, the person holding such office to serve at the > > > > direction of the Board of Directors as the chair of the Apache Doris > > > > Project, and to have primary responsibility for management of the > > > > projects within the scope of responsibility of the Apache Doris Project; > > > > and be it further > > > > > > > > > > RESOLVED, that the persons listed immediately below be and hereby are > > > > appointed to serve as the initial members of the Apache Doris Project: > > > > > > > > > > * Bin Ling > > > > * Bo Wang > > > > * Chaoyong Li > > > > * Chun Zhao > > > > * Conghui Cai > > > > * Dayue Gao > > > > * De Li > > > > * Hangyuan Liu > > > > * Hao Chen > > > > * HaoPeng Li > > > > * Jiafeng Zhang > > > > * Kaisen Kang > > > > * Ling Miao > > > > * Ming Wen > > > > * Mingyu Chen > > > > * Ruyue Ma > > > > * Shao Feng Shi > > > > * Sijie Guo > > > > * Willem Ning Jiang > > > > * Zheng Shao > > > > * Zhengguo Yang > > > > * Zuo Wei > > > > > > > > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mingyu Chen be appointed to > > > > the office of Vice President, Apache Doris, to serve in accordance with > > > > and subject to the direction of the Board of Directors and the Bylaws of > > > > the Foundation until death, resignation, retirement, removal or > > > > disqualification, or until a successor is appointed; and be it further > > > > > > > > > > RESOLVED, that the Apache Doris Project be and hereby is tasked with the > > > > migration and rationalization of the Apache Incubator Doris podling; and > > > > be it further > > > > > > > > > > RESOLVED, that all responsibilities pertaining to the Apache Incubator > > > > Doris podling encumbered upon the Apache Incubator PMC are hereafter > > > > discharged. > > > > > > > > > > > > > > > > > If this vote is passed, we will start a graduation discussion at > > general@incubator > > > > > > > > > > Please vote on graduating Apache Doris (incubating) as a Top Level > Project. > > > > The vot
Re: Add more rules to checkstyle.xml in fe
Is there a way to check the imports order? Now we can only manually remind the order by reviewers. Jianliang Qi On Thu, Apr 14, 2022 at 5:02 PM ling miao wrote: > It is best to check the code style at compile time. > > Ling Miao > > morrysnow 于2022年4月14日周四 16:37写道： > > > Hi, devs, > > > > Currently, we only have two rules in checkstyle.xml in fe. These are all > > about import. So, the code style in fe is very casual. > > I want to add more rules to checkstyle.xml in fe to Improve code > > readability, and adjust all fe code to satisfy new code style step by > step. > > What do you think about it? If this is a good idea. I will research which > > rules apply to our code and put together a list. > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@doris.apache.org > > For additional commands, e-mail: dev-h...@doris.apache.org > > > > >
Re: Add more rules to checkstyle.xml in fe
> I have add it in PR https://github.com/apache/incubator-doris/pull/8987 Good job! On Thu, Apr 14, 2022 at 5:12 PM vin jake wrote: > I have add it in PR https://github.com/apache/incubator-doris/pull/8987 > > On Thu, Apr 14, 2022 at 4:37 PM morrysnow wrote: > > > Hi, devs, > > > > Currently, we only have two rules in checkstyle.xml in fe. These are all > > about import. So, the code style in fe is very casual. > > I want to add more rules to checkstyle.xml in fe to Improve code > > readability, and adjust all fe code to satisfy new code style step by > step. > > What do you think about it? If this is a good idea. I will research which > > rules apply to our code and put together a list. > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@doris.apache.org > > For additional commands, e-mail: dev-h...@doris.apache.org > > > > >
Re: New official website released online
Looking forward to seeing the new website. Jianliang Qi On Wed, Jun 15, 2022 at 6:38 PM 41108453 <41108...@qq.com.invalid> wrote: > Dear All， > > > > > > > > We previously discussed the new version of the official website design [1]. > > We have also completed the design of the new official website[2]. > > > > > Now that the design and development of the new Apache Doris website has > been completed, > > we will release it at 12 o'clock tonight, during which there may be access > interruptions. > > Although we have conducted some tests and verifications on this before, > there may be problems during the online process. > > Once If there is a short-term irreparable problem, we will return to the > previous official website. > > > > > > > > Thread: > > 1. https://lists.apache.org/thread/2r62fb11cwobfz5b6jc7m8j3nhrf3hsf > > 2. > https://cwiki.apache.org/confluence/display/DORIS/DSIP-011%3A+New+Official+website > > > > > > > > 此致！Best Regards > > jiafeng.Zhang/张家锋 > > Email:jiafengzh...@apache.org > > > > > > > zhangfen_41108453 > zhangfen_41108...@qq.com
Re: [Discuss] Change Doris binary name
+1 Jianliang Qi On Thu, Jun 23, 2022 at 12:19 AM Zhou Minghong wrote: > +1 > > > > 回复的原邮件 > | 发件人 | 41108453<41108...@qq.com.INVALID> | > | 日期 | 2022年06月22日 23:54 | > | 收件人 | dev | > | 抄送至 | | > | 主题 | Re: [Discuss] Change Doris binary name | > +1 > > > > > > -- Original -- > From: 陈明雨 Date: Wed,Jun 22,2022 11:19 AM > To: doris-dev Subject: Re: [Discuss] Change Doris binary name > > > > Hi all, > Currently, the binary of Doris is named as `palo_be` and `palo-fe.jar`. > And Palo is the former name of Doris, and now is the commercial product > name in Baidu[1], powered by Apach Doris. > So I think it's time to change the default binary name to `doris_be` and > `doris-fe.jar`. > > > BTW, we need to consider the forward compatibility because some supervisor > daemon service use `palo_be` as the process name > to monitor its aliveness. So my suggestion is: > 1. Rename the default binary name to `doris_be`. > 2. Add a soft link "ln -s palo_be doris_be" > > > And the soft link will be removed in next (maybe 1.2 or later) release. > > > [1] https://github.com/baidu/palo > > > > -- > > 此致！Best Regards > 陈明雨 Mingyu Chen > > Email: > morning...@apache.org
Re: Re:[Discuss]Modify Dockerfile default JDK version
+1 Jianliang Qi On Wed, Jun 22, 2022 at 11:53 PM 41108453 <41108...@qq.com.invalid> wrote: > +1 > > > > > > -- Original -- > From: 陈明雨 Date: Wed,Jun 22,2022 11:36 PM > To: dev Subject: Re: Re:[Discuss]Modify Dockerfile default JDK version > > > > Agreed! > > > > > > > -- > > 此致！Best Regards > 陈明雨 Mingyu Chen > > Email: > morning...@apache.org > > > > > > At 2022-06-22 17:47:52, "苏奕嘉" <591244...@qq.com.INVALID> wrote: > >Hi all, > >In the past practice process, I found that whether it is a developer > or a community user, the JDK version is still mostly 1.8.0. In our Docker > compiled image, the default JDK-11 version is adopted. Not paying attention > to the JDK version problem often leads to taking time to compile, but > getting a binary file with an incorrect JDK version, so I want to change > the default JDK version of Doris's Docker compiled image to JDK-1.8.0. > > > > > > > > > > > > > >-- > > > >此致！Best Regards > >苏奕嘉 Yijia Su > > > >Email: > >suyi...@selectdb.com
Re: [Discuss][Random Distribution Aggregate Table Query] Make consistent query result on Aggregate Keys table for both hash distribution and random distribution.
solution 2, +1 It is better to make it easier for users to use. Jianliang Qi On Tue, Jun 28, 2022 at 2:36 PM Zhou Minghong wrote: > I support solution 2. > > > We add a new shuffle type, so we have to expand our agg code to support > the new cases. > > > > > > > > > > > > > > > > > > At 2022-06-26 21:49:19, "蔡聪辉" wrote: > > > > > > > >Hi, all devs. Now Doris has supported random distribution for Duplicate > Keys table and Aggregate Keys table without replace(replace_if_not_null) > type column to solve data skew problem. > > > >But now, It brings some problem when we do some speical queris on > aggregate table with random distribution. > > > >For example, if we have a aggreate table like following: > > > > > > > > > >Table agg_table > > > > > > > > > >ColumnNameType Aggregate Type > > > >k1char(5) > > > >v1 intmax > > > > > > > > > >Origin Data Source, which include 5 rows : > > > > >a 1 > > > >a 2 > > > >b 3 > > > >b 4 > > > >b 5 > > > > > > > > > >In hash distribution, the Doris can ensure that diffrent rows with same > aggregate keys always in the same tablet(replica), > > > > > > > > > >so that the result for select * from agg_table is same with select * from > (select k1, max(v1) from agg_table); > > > > > > > > > >but for the random distribution, aggregate keys table with diffrent rows > with same aggregate keys may be in the difffrent tablet(replica), > > > > > > > > > >which may result in different reuslt from hash distribution. > > > > > > > > > >But what is the real root cause? This is because Doris leave out the > aggregate function and group by statement if needed when do select column > operation from aggregate table, > > > >and do aggregate function with group by operation only in the Doris > storage layer. > > > > > > > > > >In the current design, count(1) and select just value column without > aggregate funcion or group by stament for aggregate table now is diffrent > from query reuslt on rollup which base on duiplicate table. > > > > > > > > > >For example, if we have duplcate table > > > >Table dup_table > > > >ColumnName Type > > > >k1char(5) > > > >v1 int > > > > > > > > > >the the rollup is > > > > Rollup rollup_table > > > >ColumnNameType Aggregate Type > > > >k1char(5) > > > >v1 intmax > > > > > > > > > >if we exectue query like "select * from dup_table " or "select count(1) > from dup_table", we won't hit the rollup even if query rollup will cost > less, this because select * or select count(1) > > > >not really match the v1 column with aggregate function like min. > > > > > > > > > >So. to make query result on random distribution consistent with hash > distribution for aggregate table, here are two main solutions. > > > >1. forbid directly select * from aggregate table, forbid select count(1) > directly from aggregate table, and give the right sql to remind user that > they should use aggregate function on value column or write group by > statement explicitly. > > > >2. keep the origin design, and we rewrite sql when user execute some > special queries on aggregate table. > > > > > >These two solutions have their own advantages and disadvantages. You are > welcome to give your opinions, feel free to discuss. > > >
Re: MySQL client queries whether there is a limit of 65535 records for export?
Hi, Doris defaults to adding `limit 65535 `to `order by` clause, if you want to order by more data you can manually write an `order by` with a larger number. Jianliang Qi On Mon, Jul 4, 2022 at 5:07 PM zhan...@eastcom-sw.com < zhan...@eastcom-sw.com> wrote: > >Hi, is there a parameter that limits the maximum number of records > 65535 through MySQL client query export? > >The total number of records in a table is 14552989, but whether it is > to query the full amount through tools or select * from table into outfile > "file:////result_", >The maximum results are only 65535. > >The data table is the aggregate model, 16buckets, and it is normal to > export the unique model. > > count(`count`)| > --+ > 14552989| > > FileNumber|TotalRows|FileSize|URL > | > > --+-++-+ > 1|65535| > 4472974|file:////result_6d366b7e25744ae0-89ff707424449356_| > > > > > 姓名 ：张泽钦 > 公司 ：杭州东方通信软件技术有限公司 广东项目部 > 地址 ：广州市天河区珠江新城海安路13号越秀财富世纪广场A1栋1802 > 邮编 ：510627 > 手机 ：13414145631 > Email：zhan...@eastcom-sw.com >
Re: [Discuss][DSIP] Use Docker support external tables scenarios test
Great idea! This will facilitate external table function testing. Looking forward to it. Jianliang Qi On Wed, Jul 6, 2022 at 9:19 AM stalary wrote: > Hi all, > Currently we support a variety of external tables, but ut can only mock > a lot of times. In order to be able to test for real scenarios, I wanted to > use Docker to solve the problem of third party dependencies. My initial > thoughts are as follows. > 1. Create docker-compose.yaml files for the third party dependencies you > want to test. > 2. Implement annotations for ut, supporting the specification of > docker-compose.yaml. > 3. Start the Docker service before starting ut. > > > Reference implementation > a. > https://github.com/apache/dolphinscheduler/blob/dev/dolphinscheduler-e2e/dolphinscheduler-e2e-case/src/test/java/org/apache/dolphinscheduler/e2e/cases/ClickhouseDataSourceE2ETest.java > b. > https://github.com/apache/skywalking-java/blob/main/test/plugin/scenarios/activemq-scenario/configuration.yml > > > Stalary > Email: stal...@163.com
Re: [Discuss] Optimize the official website
Looking forward to it. On Thu, Jul 14, 2022 at 9:54 PM luzhijing <543881...@qq.com.invalid> wrote: > The Doris official website had been redesigned and updated last month. > During a month of use, many users had reported the following issues: > - Homepage is too slow and animation effect is redundant. > - Bad search experience. > - The homepage blog cannot be automatically switched with the launch > of a new blog. > - 404 Error when switching document version. > - …… > > > So I would like to optimize the official website on the basis of the > previous version. I will redesign the homepage to make it more concise and > improve the problems of bad experience. -- Best regards. Jianliang Qi Email: jianlian...@apache.org
