| CPC G06F 16/24542 (2019.01) [G06F 16/221 (2019.01); G06F 16/2379 (2019.01); G06F 16/258 (2019.01)] | 20 Claims |

|
1. A method of implementing row-oriented data storage by a column-oriented storage database, comprising:
receiving a data reading and writing request by a first database, wherein the first database stores data in a column-oriented storage format, the data reading and writing request is configured to request for reading/writing data from/into a row storage table, the first database comprises a front-end node and a back-end node, the front-end node is configured to receive the data reading and writing request, and the back-end node is configured to store data;
generating, by the front-end node, a physical execution plan based on the data reading and writing request, wherein the physical execution plan comprises physical operators;
reading/writing data from/into a second database by the back-end node based on the physical execution plan, wherein the first database calls data from the second database, and the second database stores data in a row-oriented storage format;
wherein the method further comprises:
determining a request type of the data reading and writing request; and
determining a reading and writing path for the front-end node and the back-end node to read/write data from/into the second database based on the request type of the data reading and writing request, wherein the determining a reading and writing path for the front-end node and the back-end node to read/write data from/into the second database based on the request type of the data reading and writing request comprises:
determining, when the data reading and writing request is a first request type, that the front-end node and the back-end node read/write data from/into the second database via a first reading and writing path, and
determining, when the data reading and writing request is a second request type, that the front-end node and the back-end node read/write data from/into the second database via a second reading and writing path, wherein the first reading and writing path is shorter than the second reading and writing path.
|