yiguolei

Results 14 issues of yiguolei

FOLLY_OPENSSL_PREREQ is not defined if ssl is boringssl. ![image](https://user-images.githubusercontent.com/9208457/145970400-97f70562-f156-4f32-8078-1db8b3127d30.png) But it is used in SSLContext.h. So that I think FOLLY could not work with boringssl, Am I right?

## Release Note 1.1.1 ### Upgrade Notes None ### Features #### 1. Support ODBC Sink in Vectorized Engine. This feature is enabled in non-vectorized engine but it is missed in...

# Proposed changes This issue is introduced by https://github.com/apache/doris/pull/8096, the operator priority is wrong , so that in some cases, there will be many scanners. ## Problem summary Describe your...

area/vectorization
reviewed
dev/1.1.3

## Release Note 1.1.2 [v1.1.1 Release Note](https://github.com/apache/doris/issues/11121) ### Upgrade Notes In this release, Doris Team has fixed more than 170 issues or performance improvement since 1.1.1. This release is a...

release notes

### Search before asking - [X] I had searched in the [issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no similar issues. ### Description There are some method in doris that may throw exception but...

doris-future

# Proposed changes NewLoadStreamMgr already has pipe and other info. Do not need save the pipe into fragment state. and FragmentState should be more clear. But this pr will change...

area/planner

# Proposed changes 1. remove duplicate type definition in function context 2. remove unused method in function context 3. not need stale state in vexpr context because vexpr is stateless...

area/sql/function
area/vectorization

## Proposed changes Currently, we could not get real cancel reason because the status is very mess. In this PR I do following: 1. add new method in status.java, like...

meta-change

后端用C++ 实现的,所以已经有proto 定义的IDL 对象了; 但是客户端是java,想用jprotobuf来做客户端,但是提示客户端传递的对象必须使用@Protobuf 标注。 如果能都用proto 来定义对象,那么前后端就统一了。

## Proposed changes Issue Number: close #xxx ## Further comments If this is a relatively large or complex change, kick off the discussion at [[email protected]](mailto:[email protected]) by explaining why you chose...