Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release Note 1.1.1 #11121

Open
yiguolei opened this issue Jul 22, 2022 · 5 comments
Open

Release Note 1.1.1 #11121

yiguolei opened this issue Jul 22, 2022 · 5 comments

Comments

@yiguolei
Copy link
Contributor

yiguolei commented Jul 22, 2022

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 vectorized engine in 1.1. So that we add back this feature in 1.1.1.

2. Simple Memtracker for Vectorized Engine.

There is no memtracker in BE for vectorized engine in 1.1, so that the memory is out of control and cause OOM. In 1.1.1, a simple memtracker is added to BE and could control the memory and cancel the query when memory exceeded.

Improvements

1. Cache decompressed data in page cache.

Some data is compressed using bitshuffle and it costs a lot of time to decompress it during query. In 1.1.1, doris will decompress the data that encoded by bitshuffle to accelerate query and we find it could reduce 30% latency for some query in ssb-flat.

Bug Fix

1. Fix the problem that could not do rolling upgrade from 1.0.(Serious)

This issue was introduced in version 1.1 and may cause BE core when upgrade BE but not upgrade FE.

If you encounter this problem, you can try to fix it with #10833.

2. Fix the problem that some query not fall back to non-vectorized engine, and BE will core.

Currently, vectorized engine could not deal with all sql queries and some queries (like left outer join) will use non-vectorized engine to run. But there are some cases not covered in 1.1. And it will cause be crash.

3. Compaction not work correctly and cause -235 Error.

One rowset multi segments in uniq key compaction, segments rows will be merged in generic_iterator but merged_rows not increased. Compaction will failed in check_correctness, and make a tablet with too much versions which lead to -235 load error.

4. Some segment fault cases during query.

#10961 #10954 #10962

Behavior Changes

None.

Thanks

Thanks to everyone who has contributed to this release:
@jacktengg
@mrhhsg
@xinyiZzz
@yixiutt
@starocean999
@morrySnow
@morningman
@HappenLee

@yiguolei yiguolei changed the title [Enhancement] Release Note 1.1.1 Jul 22, 2022
@kkfnui
Copy link
Contributor

kkfnui commented Jul 22, 2022

Has the version include #11033 ?

@kpfly
Copy link

kpfly commented Jul 22, 2022

Has the version include #11033 ?

Yes

@kpfly
Copy link

kpfly commented Jul 25, 2022

Maybe #11033 should be added in release note. @yiguolei

@yiguolei yiguolei pinned this issue Jul 30, 2022
@Zu3zz
Copy link

Zu3zz commented Aug 9, 2022

Which pkg should i choose doris in v1.1.1 between java version 8 and version 11?
In Doris v1.1.0, It is separate into two different package

@yiguolei
Copy link
Contributor Author

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 vectorized engine in 1.1. So that we add back this feature in 1.1.1.

2. Simple Memtracker for Vectorized Engine.

There is no memtracker in BE for vectorized engine in 1.1, so that the memory is out of control and cause OOM. In 1.1.1, a simple memtracker is added to BE and could control the memory and cancel the query when memory exceeded.

Improvements

1. Cache decompressed data in page cache.

Some data is compressed using bitshuffle and it costs a lot of time to decompress it during query. In 1.1.1, doris will decompress the data that encoded by bitshuffle to accelerate query and we find it could reduce 30% latency for some query in ssb-flat.

Bug Fix

1. Fix the problem that could not do rolling upgrade from 1.0.(Serious)

This issue was introduced in version 1.1 and may cause BE core when upgrade BE but not upgrade FE.

If you encounter this problem, you can try to fix it with #10833.

2. Fix the problem that some query not fall back to non-vectorized engine, and BE will core.

Currently, vectorized engine could not deal with all sql queries and some queries (like left outer join) will use non-vectorized engine to run. But there are some cases not covered in 1.1. And it will cause be crash.

3. Compaction not work correctly and cause -235 Error.

One rowset multi segments in uniq key compaction, segments rows will be merged in generic_iterator but merged_rows not increased. Compaction will failed in check_correctness, and make a tablet with too much versions which lead to -235 load error.

4. Some segment fault cases during query.

#10961 #10954 #10962

JDK 8.

@morningman morningman unpinned this issue Sep 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants