After append new items,  the release notes would be like this after
update:

New Features

- Support scaling for ShardingSphere (alpha version)
- Move etcd registry center from experiment repo to apache repo
- Upgrade to Java 8

Enhancement

- Optimization for Sharing Parser with ANTLR Visitor improving the parsing
performance of long SQL by 100%~1000%
- Use multiple threads to load metadata for different data sources
- Support `allow.range.query.with.inline.sharding` option
- The docker of Sharding-Proxy supports loading external lib packages
- Support integration with Spring using @ShardingTransactionType
- Enhance ShardingDataSource to compatiable with Seata in micro-sevice
distribution transaction

Refactor

- Migrate LeafKeyGenerator and remove distributedLock

Bug Fixes

- Fix an exception caused by using a CHAR/VARCHAR type column as a order by
item
- Refine `DataTypeName` syntax rules of all database dialects
- Fix an exception caused by executing `BEGIN` using prepared statement of
MySQL C API
- Fix the problem that `ALTER TABLE` fails to execute when the field type
of the table contains Integer/Double/BigDecimal
- Fix the problem of the stop index dislocation of segment with alias
- Fixed the problem that overwriting SQL `SELECT * FROM tbl WHERE
encrypt_col = ? AND (sharding_key = ? OR sharding_key = ?)` when using
sharding + encrypt would throw StringIndexOutOfBoundsException
- Fixed the problem of incorrect decoding after AES encoding when using
Sharding-Proxy in Spring Boot
- Fix a long-time problem of adding schema dynamically in Sharding-UI

--

Zhang Yonglun
Apache ShardingSphere


KimmKing <[email protected]> 于2020年4月3日周五 上午9:16写道:

> Hello, jun,
> PR#5050 fix a long-time bug for adding schema dynamically in sharing-ui.
> It's nessesary to include tag 4.1.0 and added to release-note.
>
> At 2020-04-02 13:02:28, "赵俊" <[email protected]> wrote:
> >Hi, community
> >
> >In master branch, since PR#4945 have changed the KeyGenerator API.
> >So we plan to create 4.1.0-release branch based on 43d3426 commit,
> >PRs after 43d3426  we will change it to 5.0.0 milestone.
> >
> >If you have any question please feel free to let me know.
> >
> >------------------
> >Zhao Jun (cherrylzhao)
> >Apache ShardingSphere & ServiceComb
> >
> >
> >> On Mar 17, 2020, at 1:15 PM, sushixiang <[email protected]> wrote:
> >>
> >> Sounds great.
> >>
> >>
> >> And I want to know 'Upgrade to Java 8' has already be finished yet? If
> not, I want to join.
> >>
> >>
> >>
> >>
> >> ------------------&nbsp;Original&nbsp;------------------
> >> From:&nbsp;"Zhang Yonglun"<[email protected]&gt;;
> >> Date:&nbsp;Tue, Mar 17, 2020 12:30 PM
> >> To:&nbsp;"dev"<[email protected]&gt;;
> >>
> >> Subject:&nbsp;[DISCUSS] 4.1.0 release plan
> >>
> >>
> >>
> >> Hi ShardingSphere community,
> >>
> >> I'm preparing a new release of ShardingSphere 4.x. The new release
> include
> >> a couple significant updates, so the version will be 4.1.0.
> >>
> >> The target tag is
> >> https://github.com/apache/incubator-shardingsphere/tree/dev-5.x which
> >> include many bug fixes, enhancement and refactor.
> >>
> >> All updatas can be found in
> >>
> https://github.com/apache/incubator-shardingsphere/issues?q=is%3Aissue+milestone%3A5.0.0+
> >> .
> >>
> >> After reviewing those issues, the major items in our next release note
> >> would be:
> >>
> >> - Support scaling for shardingsphere
> >> - Optimization for Sharing Parser with ANTLR Visitor for MySQL
> >> - Parsing SubQuery
> >> - Upgrade to Java 8
> >> - Redesign class domain of parser module
> >> - Create database protocol module
> >> - Create new module for shardingsphere-sql-parse-binder
> >> - Refactor orchestration center interface
> >> - Improve integrate SQL parser test engine
> >> - Decouple UI and ShardingSphere
> >>
> >> Note: This release note is just a draft, anyone would add on to it.
> >>
> >> Currently, we are being preparing our next release, i appreciate it if
> you
> >> could pick up more items for next release note, or give your suggestions
> >> about this release.
> >>
> >> Welcome to our release discussion.
> >> --
> >>
> >> Zhang Yonglun
> >> Apache ShardingSphere
> >
>

Reply via email to