Should we add the fix of Issue#4182[1] into 4.0.1?
[1] https://github.com/apache/incubator-shardingsphere/issues/4182 -- Yi Yang(Sion) Apache ShardingSphere At 2020-02-09 15:44:05, "zhaojun" <[email protected]> wrote: >Hi, ShardingSphere community, > >I’d like to be the release manager of 4.0.1 version. >We have done some bug fixes and performance optimization in past month based >on 4.0.0. >If there is no other requirement, I think we can start to release 4.0.1 >recently. > > >## Bug fixes > >3975 oracle insert SQL could not work in encrypt mode >3997 proxy for PostgreSQL decode parameters error in all types except String >4022 none sharding strategy could not config in spring-boot >4052 plain column could not get from resultSet in sharding-encrypt mode >4173 wasNull field was wrong in GroupByStreamMergeResult > > >## Enhancement > >3956 using guava cache to improve parsing performance >4004 optimize COM_STM_EXECUTE of MySQL to support sysbench >4054 optimize antlr performance using two-stage parsing strategy >4205 add class filter constructor to restrict the illegal class from YAML > >Thanks to these contributors for their code commits. > - tuohai666, xiyelife, SteNicholas, KomachiSion, beckhampu, plazmdk > >Any other task missing here? Please feel free to let me know. > >------------------ >Zhao Jun (cherrylzhao) >Apache ShardingSphere & ServiceComb
