Skip to content
Permalink
Browse files
updated menu, homepage, faq and sql_reference
  • Loading branch information
lide committed Oct 12, 2018
1 parent 902e746 commit a86fc5857b19f9ce3ca1e128d56fa83abbce768b
Showing 32 changed files with 969 additions and 4,061 deletions.
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
@@ -4,17 +4,13 @@ render.tags=false
render.sitemap=true
template.homepage.file=homepage.gsp
template.simplepage.file=simplepage.gsp
template.retired.file=retired.gsp
template.archive.file=archive.gsp
template.tag.file=tags.gsp
template.sitemap.file=sitemap.gsp
template.post.file=post.gsp
template.page.file=page.gsp
template.feed.file=feed.gsp
template.guide.file=guide.gsp
template.proposalGuide.file=guide.gsp
template.pmcGuide.file=guide.gsp
template.policy.file=policy.gsp
render.index=false
index.file=index.html
content.folder=pages
@@ -0,0 +1,114 @@
//Licensed under the Apache License, Version 2.0 (the "License");
//you may not use this file except in compliance with the License.
//You may obtain a copy of the License at
//
//http://www.apache.org/licenses/LICENSE-2.0
//
//Unless required by applicable law or agreed to in writing, software
//distributed under the License is distributed on an "AS IS" BASIS,
//WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
//See the License for the specific language governing permissions and
//limitations under the License.
= Apache Doris Community
Apache Doris Community
2018-09-29
:jbake-type: simplepage
:jbake-status: published
:idprefix:
:toc:
:imagesdir: ../images/

Most discussion about Doris happens over email and GitHub.

= 1. Doris Community

**WiKi** link:https://github.com/apache/incubator-doris/wiki[Wiki On Github]

**Development mailing list** dev#doris.apache.org for discussion about project development link:mailto:dev-subscribe@doris.incubator.apache.org[(Click here to subscribe this email list)]

**Issues** link:https://github.com/apache/incubator-doris/issues[GitHub Doris Issues and Pull Requests]

**Meetups Doris** meetups for different meetup groups around the world.

= 2. Contributing
Doris is a community-led project and we are delighted to receive contributions of anything from minor fixes to big new features.

== 2.1 What to work on

If you have an itch to scratch, then by all means do that! Fixing bugs you run into, or adding features you need, are both immensely helpful.

If you're looking for some starter projects, we maintain a list of issues suitable for new developers.

There are plenty of ways to help outside writing Doris code. Code review of pull requests (even if you are not a committer), feature suggestions, reporting bugs, documentation and usability feedback all matter immensely.

== 2.2 Getting your changes accepted

Patches to Doris are done through GitHub pull requests.

In general please follow the contributing guidelines when sending in pull requests. This will help review proceed as quickly as possible.

For code contributions, we require that you agree to a Contributor License Agreement (CLA) before we can accept your code.

= 3. Mentors

* David Fisher (wave@apache#org)
* Luke Han (lukehan@apache#org)
* Willem Ning Jiang (ningjiang@apache#org)

= 4. PPMC

* Ruyue Ma (https://github.com/maruyue, maruyue@apache#org)

* Chun Zhao (https://github.com/imay, zhaoc@apache#org)

* Mingyu Chen (https://github.com/morningman, morningman@apache#org)

* De Li (https://github.com/lide-reed, lide@apache#org)

* Bin Lin (https://github.com/lingbin, lingbin@apache#org)

* Hao Chen (https://github.com/chenhao7253886, chenhao@apache#org)

* Chaoyong Li (https://github.com/cyongli, lichaoyong@apache#org)

* Sijie Guo (sijie@apache#org)

* Zheng Shao (zshao@apache#org)


= 5. Committers
Committers are collectively responsible for Doris's technical management. This involves setting the direction of the project, contributing code, and reviewing code contributed by others.

You don't need to be a committer to contribute- pull requests are welcome from anyone.

All committers are members of the PPMC.

== 5.1 Becoming a committer

If you'd like to become a committer, that's great! Please contact one of the existing committers for a walk through the process. Basically, what we're looking for is an interest in ongoing contributions to Doris.

= 6. General committer guidelines

If you are an official Doris committer then congratulations! You are part of a fantastic group of people. Here are some guidelines to follow to help ensure the Doris project continues to grow and improve:

You can merge your own pull request if it fits the rest of the criteria. A common thing to see is "+1 after travis" from other committers.

A pull request should have at least one +1 from a committer who is not the author, on the "code/textual" level of review.

Pull requests which have just one +1 from a committer couldn't be merged earlier than after 3 working days since PR submission.

A pull request with just one +1 could be merged only by (or in coordination with) the committer who provided the review. Because the reviewer may think that the PR is complex or risky enough that needs another pair of eyes to look at it. If this is the case, the first reviewer should indicate this in the PR approval message.

If a pull request has two or more +1's from committers who are not the author, it could be merged immediately and by any committer. But still, enough time since the PR submission should pass to give folks a reasonable chance to indicate a desire to comment on the pull request. AKA: don't merge a pull request that was submitted Friday evening until at least 1~2 regular work days have passed. Use good judgement here.

= 7. Governance
The PMC (Project Management Committee) is responsible for the administrative aspects of the Doris project. The responsibilities of the PMC include:

* Approving releases

* Nominating new committers

* Maintaining the project's shared resources, including the github account, mailing lists, websites, social media channels, etc.

* Maintaining guidelines for the project

@@ -0,0 +1,66 @@
//Licensed under the Apache License, Version 2.0 (the "License");
//you may not use this file except in compliance with the License.
//You may obtain a copy of the License at
//
//http://www.apache.org/licenses/LICENSE-2.0
//
//Unless required by applicable law or agreed to in writing, software
//distributed under the License is distributed on an "AS IS" BASIS,
//WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
//See the License for the specific language governing permissions and
//limitations under the License.
= Apache Doris Downloads
Apache Doris Downloads
2018-09-29
:jbake-type: simplepage
:jbake-status: published
:idprefix:
:toc:
:imagesdir: ../images/

= Stable release
The current Doris stable release is 0.8.2. This version is recommended for production use.

* link:https://github.com/apache/incubator-doris/releases/download/v0.8.2/palo-0.8.2-release-20180824.tar.gz[palo-0.8.2-release-20180824.tar.gz] 184 MB

* link:https://github.com/apache/incubator-doris/archive/v0.8.2.zip[Source code (zip)]

* link:https://github.com/apache/incubator-doris/archive/v0.8.2.tar.gz[Source code (tar.gz)]

== Change Log

1. Performance improvement
* Support vectorized execution engine.
* Support aggregation operator parallelization.
* Optimized storage engine for more efficient data fetching.

2. Table-level privileges support
* User can grant fine-grained privileges on specified tables to specified user from specified host.

3. Backup and restore
* User can backup snapshot of data to HDFS and restore snapshot to other Palo cluster.

4. Broker supports HDFS HA and Hadoop kerberos authentication.

5. Using [BRPC](https://github.com/brpc/brpc) instead of the old RPC framework.

6. A lot of bugs fixed.

7. Other changes:

* Rewrite http server in Backend using Libevent to replace Mongoose.
* Remove mysql code to avoid copyright problem.
* More metrics to expose internal situation of Palo system.
* Same Frontend can be removed and added again without the changing port.
* Change the format of Frontend's audit log for parsing it more conveniently.

== Compatibility

**This release version DOES NOT support rolling upgrade, and CAN NOT rollback after upgrade. So it is HIGHLY RECOMMENDED to backup your data and meta data before upgrading to this release version. Or upgrade it in your test/pre-online Palo cluster to make sufficient test.**

|Item|Content|
|---|---|
|Forward Compatibility | 0.8.1, 0.8.0 |
|Rolling Upgrade | No |
|Rollback | No |

@@ -1,11 +1,24 @@
title=Apache Doris FAQs
date=2018-09-28
type=simplepage
status=published
imagesdir=/images/
~~~~~~
# 建表
//Licensed under the Apache License, Version 2.0 (the "License");
//you may not use this file except in compliance with the License.
//You may obtain a copy of the License at
//
//http://www.apache.org/licenses/LICENSE-2.0
//
//Unless required by applicable law or agreed to in writing, software
//distributed under the License is distributed on an "AS IS" BASIS,
//WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
//See the License for the specific language governing permissions and
//limitations under the License.
= Apache Doris FAQs
Apache Doris FAQs
2018-09-29
:jbake-type: simplepage
:jbake-status: published
:idprefix:
:toc:
:imagesdir: ../images/

= 1. 建表

**Q:建表报错:Float or double can't be used as a key, use decimal instead**

@@ -47,7 +60,7 @@ A:没有

A:Palo只支持utf8编码,对gbk不支持

# 表的属性和信息查看
= 2. 表的属性和信息查看

**Q:如何看一个表占了多少物理存储?**

@@ -69,7 +82,7 @@ A:desc table_name all;

A:show partitions from table_name;

# 修改表
= 3. 修改表

**Q:palo可以对已有的表增加列吗?**

@@ -151,7 +164,7 @@ A:delete执行之后目前是会影响性能,建议少发delete

A:是的

# 导入
= 4. 导入

**Q:show load能按照一些条件查询么,能部分匹配么**

@@ -261,7 +274,7 @@ A:在columns参数中指定表和数据中列的对应关系,并且在需要

A:超过7天的历史数据会被清空

# 查询
= 5. 查询

**Q:查询报错:memory limit exceeded**

@@ -307,7 +320,7 @@ A:由create view时的as select决定的,具体可以通过执行explain selec

A:可以通过palo查询mysql库,palo本身不存储mysql的数据,也不能使用palo往mysql中导入数据

# 其它
= 6. 其它

**Q:报错:Sql parsing error, check your sql.**

This file was deleted.

0 comments on commit a86fc58

Please sign in to comment.