CN104462421B - Multi-tenant extended method based on key-value database - Google Patents

Multi-tenant extended method based on key-value database Download PDF

Info

Publication number
CN104462421B
CN104462421B CN201410771826.8A CN201410771826A CN104462421B CN 104462421 B CN104462421 B CN 104462421B CN 201410771826 A CN201410771826 A CN 201410771826A CN 104462421 B CN104462421 B CN 104462421B
Authority
CN
China
Prior art keywords
tenant
business
entity
metadata
business entity
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201410771826.8A
Other languages
Chinese (zh)
Other versions
CN104462421A (en
Inventor
刘磊
周渊斐
郑艳伟
袁鼎
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Zhengzhou Xinrand Network Technology Co ltd
Institute of Acoustics CAS
Original Assignee
Institute of Acoustics CAS
Beijing Intellix Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Institute of Acoustics CAS, Beijing Intellix Technologies Co Ltd filed Critical Institute of Acoustics CAS
Priority to CN201410771826.8A priority Critical patent/CN104462421B/en
Publication of CN104462421A publication Critical patent/CN104462421A/en
Application granted granted Critical
Publication of CN104462421B publication Critical patent/CN104462421B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24Querying
    • G06F16/245Query processing
    • G06F16/2453Query optimisation
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/22Indexing; Data structures therefor; Storage structures
    • G06F16/2282Tablespace storage structures; Management thereof

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computational Linguistics (AREA)
  • Software Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The present embodiments relate to a kind of multi-tenant extended method based on key value database, the described method includes:Obtain initial service entity metadata;Customization stage, attribute of activating business on the initial service entity metadata define the service attribute Business Entity and display label, and generation meets the specific transactions entity metadata of multi-tenant demand;The example stage is generated, according to the specific transactions entity metadata, creates key value Key Value databases;The example operation phase, the Business Entity data of Key Value databases are inserted into using tenant identification as RowKey prefixes, the query context inquiry business solid data of RowKey is generated by the tenant identification, Business Entity data are taken out from the Key Value databases in the query context, interactive interface is generated according to the specific transactions entity metadata, so as to by the Business Entity data display.

Description

Multi-tenant extended method based on key-value database
Technical field
The present invention relates to computer realm more particularly to a kind of multi-tenant extended methods based on key-value database.
Background technology
The fast development of Internet technology causes traditional database to face huge challenge when tackling mass data, distributed Key-value Key-Value databases come into being, and Key-Value databases include the non-relational distributed data base increased income HBase, non-relational database Cassandra, the no SQL of the database of non-relational etc..The distribution of Key-Value databases Framework, mass data can be stored by having with respect to traditional Relational DataBase, and a table can have more than one hundred million rows;It is stored towards row, face The storage of nematic (race) and permission control, arrange (race) independent retrieval;Sparse storage for empty row, is not take up memory space, can It is very sparse table to be designed.
Multi-tenant technology is mainly used for multiple tenants and shares hardware resource, multiple public Application Instances of tenant. In the prior art, multi-tenant technology mainly includes following three kinds of schemes in terms of data storage:
1. each tenant possesses self contained data base
Mutually independent database is provided for different tenants, such data isolation is best, and due to that can be different The individually designed database structure of user helps to simplify the design of database structure, breaks down and recover also relatively easy.But Self contained data base is established for each tenant, for different tenants without really sharing hardware resource, acquisition cost and maintenance cost are high, General operator can not receive.
2. tenant's shared data bank, but possess independent storehouse table
All tenants share a database, but different tenants possess independent storehouse table.Provide certain data it Between isolation, but extend relatively cumbersome, be not easy to extend, cost is also higher, across tenant data statistics hardly possible.
3. tenant's shared data bank, shared data bank table
All tenant's shared data banks, shared library table, this method cost is minimum, sharing degree highest, allows the rent supported Family is also most, but since the business demand between different tenants differs, needs well-designed data for such case Storehouse.During using traditional Relational DataBase, when tenant need add custom field when, it is necessary in the database addition row, it is right For Mr. Yu tenant, the row of other tenants addition are useless row to the tenant, but need to exist in the database, but when rent , it is necessary to increase a large amount of row in the database, this results in extremely wasting there are substantial amounts of null value in database when amount amount is larger Space.
The content of the invention
An embodiment of the present invention provides a kind of multi-tenant extended methods based on key-value database, effectively reduce multi-tenant The operation cost and maintenance cost of database increase the autgmentability of multi-tenant database, reduce customization cost and the shortening of tenant Customize the cycle.
An embodiment of the present invention provides a kind of multi-tenant extended method based on key-value database, the described method includes:
Obtain initial service entity metadata;
Customization stage, attribute of activating business on the initial service entity metadata define industry to the service attribute Entity and display label, generation meet the specific transactions entity metadata of multi-tenant demand;
The example stage is generated, according to the specific transactions entity metadata, creates key-value Key-Value databases;
The example operation phase is inserted into the Business Entity of Key-Value databases using tenant identification as RowKey prefixes Data, by the tenant identification generate RowKey query context inquiry business solid data, in the query context from Business Entity data are taken out in the Key-Value databases, interactive interface is generated according to the specific transactions entity metadata, So as to by the Business Entity data display.
Preferably, the initial service entity metadata and the specific transactions entity metadata include at least:Business The table name of entity, the display label of Business Entity, the attribute column name of Business Entity, the data type of Business Entity, Business Entity Index column mark and Business Entity attribute display label.
Preferably, in the generation example stage, the method further includes:
All tenants share a Key-Value database, and the initial service entity metadata is corresponding to be classified as All tenants share.
Preferably, in the generation example stage, the method further includes:
It is described to activate business attribute for meeting the different business demand of the tenant, and at the same time generation and newly-increased industry The corresponding extension columns of business attribute, the extension columns are only visible to the tenant.
Preferably, the Business Entity number that Key-Value databases are inserted into using tenant identification as RowKey prefixes According to specifically further including:Using the tenant mark+Business Entity table name as the Business Entity data RowKey prefixes.
Preferably, the query context inquiry business solid data that RowKey is generated by the tenant identification specifically wraps It includes:The Key-Value databases are inquired about, according to the mark of the tenant and the table name setting inquiry model of the Business Entity It encloses, in the query context of the setting, inquiry is carried out according to querying condition set by user and obtains the Business Entity data.
Preferably, it is described to be specifically included according to specific transactions entity metadata generation interactive interface:
The specific transactions entity metadata of the tenant is obtained according to the mark of the tenant;
According to the index column information of the specific transactions entity metadata of the tenant and data type generation query term;
Display label and Business Entity data display inquiry knot in the specific transactions entity metadata of the tenant Fruit;
It is shown according to the display label of Business Entity of the specific transactions entity metadata of the tenant, the attribute of Business Entity The New any of the newly-built page of the data type of indicating label and Business Entity generation.
Multi-tenant extended method proposed by the present invention based on key-value database, can generate positive advantageous effect, tool Body is as follows:It supports the application for meeting tenant's individual demand by customizing generation, can be kept away for the similar business of operation flow Exempt from overlapping development;Using shared Key-Value databases realization is facilitated to extend, cut operating costs, with newly-increased tenant's Increase, with the growth of the userbase of tenant, the present invention is using tenant identification as the RowKey of all Business Entity data Prefix facilitates realization to extend, cuts operating costs.
Description of the drawings
Fig. 1 is the multi-tenant extended method flow chart based on key-value database that the embodiment of the present invention one provides;
Fig. 2 is the functional block diagram of the multi-tenant extended method provided by Embodiment 2 of the present invention based on key-value database.
Specific embodiment
To make the object, technical solutions and advantages of the present invention clearer, the present invention is embodied below in conjunction with the accompanying drawings Example is described in further detail.
Embodiment one
The extension of the multi-tenant based on key-value database that embodiment one that the present invention will be described in detail by taking Fig. 1 as an example below provides Method, Fig. 1 are the multi-tenant extended method flow chart provided in an embodiment of the present invention based on key-value database, of the invention real It can be operation supporting platform to apply subject of implementation in example.Fig. 2 show that the embodiment of the present invention proposes based on key-value database The functional block diagram of multi-tenant extended method.As shown in Fig. 2, the multi-tenant extension side proposed by the present invention based on key-value database In method, using the operation supporting platform of expansible definable multi-tenant, which uses distribution Key-Value data stocks Store up business information.With reference to shown in Fig. 1 and Fig. 2, this method comprises the following steps:
Step 101 obtains initial service entity metadata;
Initial service entity metadata includes at least:The table name of Business Entity, the display label of Business Entity, Business Entity Attribute column name, the data type of Business Entity, the index column of Business Entity mark and Business Entity attribute display label.
Step 102, customization stage, attribute of activating business on the initial service entity metadata, to the business category Property define Business Entity and display label, generation meets the specific transactions entity metadata of multi-tenant demand.
The initial service entity metadata and the specific transactions entity metadata include at least:The table of Business Entity Name, the attribute column name of the display label of Business Entity, Business Entity, the data type of Business Entity, the index column of Business Entity The attribute display label of mark and Business Entity.
Specifically, before operation supporting platform deployment, each module initial service entity member is formulated according to each modular service demand Data, and Key-Value data Kuku table is created according to initial service metadata, for example, wherein service metadata structure is main As shown in table 1:
1 service metadata structure table of table
It is as shown in table 2 according to template establishment database table CRM structures:
2 database table CRM structure tables of table
Step 103, generation example stage according to the specific transactions entity metadata, create key-value Key-Value numbers According to storehouse.
In the generation example stage, the method further includes:
All tenants share a Key-Value database, and the initial service entity metadata is corresponding to be classified as All tenants share.
Specifically, in the customization stage, tenant is on the basis of initial service entity metadata, according to domain knowledge to the first beginning of the school year Pragmatic voxel data is customized, and by changing initial column information, increases self-defined column information generation tenant's specific transactions entity Metadata.
Tenant 1 is certain educational institution, and according to business demand, the corresponding entity names of CRM are changed to " student ";Initial service The corresponding attribute tags of " USER_NAME " row are changed to " student name " in entity metadata, and " USER_ID " corresponds to attribute tags It is changed to " student number ";Increase attribute " grade " for Business Entity " student ", and define corresponding self-defined row, by customizing above, rent It is as shown in table 3 that family 1 generates self-defined Business Entity metadata:
The self-defined Business Entity metadata of 3 tenant 1 of table generation
Tenant 2 is certain corporate user, and according to business demand, the corresponding entity names of CRM are changed to " employee ";Initial service The corresponding attribute tags of " USER_NAME " row are changed to " employee name " in entity metadata, and " USER_ID " corresponds to attribute tags It is changed to " employee number ";Increase attribute " department " for Business Entity " employee ", and define corresponding self-defined row, by customizing above, It is as shown in table 4 that tenant 2 generates self-defined Business Entity metadata:
The self-defined Business Entity metadata of 4 tenant 2 of table generation
According to the self-defined Business Entity metadata that tenant 1 and tenant 2 generate, we can define several it is similar from Business Entity metadata is defined, equally we assume that tenant N is certain enterprise management level personnel, according to business demand, CRM is corresponded to Entity name be changed to " handle ";The corresponding attribute tags of " USER_NAME " row are changed to " pipe in initial service entity metadata Reason person ", " USER_ID " corresponding attribute tags are changed to " administrator number ";Increase attribute " department " for Business Entity " employee ", and it is fixed The corresponding self-defined row of justice, by customizing above, it is as shown in table 5 that tenant N generates self-defined Business Entity metadata:
The self-defined Business Entity metadata of 5 tenant N of table generations
In the generation example stage, the method further includes:
It is described to activate business attribute for meeting the different business demand of the tenant, and at the same time generation and newly-increased industry The corresponding extension columns of business attribute, the extension columns are only visible to the tenant.
Different tenants share same database table using generation example after the extension of identical initial service entity metadata, initially Business Entity metadata is corresponding to be classified as all tenants and shares;Meanwhile according to tenant generate specific transactions entity it is self-defined Attribute adds self-defined extension columns for tenant, and self-defined extension columns are only from the tenant.After certain tenant adds self-defined row, only There is the tenant in the row interpolation data, due to the sparse row storage characteristics of Key-Value databases, simultaneously there is no should by other tenants The data of the self-defined row of tenant, are also not take up any redundant space.1 Business Entity of tenant " student " at this time, 2 Business Entity of tenant The shared Key-Value database table CRM structures of " employee " and tenant N Business Entities " administrator " are extended to table 6 automatically:
Table 6Key-Value database table CRM structure extension tables
Step 104, example operation phase are inserted into Key-Value databases using tenant identification as RowKey prefixes Business Entity data generate the query context inquiry business solid data of RowKey by the tenant identification, in the inquiry In the range of from the Key-Value databases take out Business Entity data, according to the specific transactions entity metadata generate Interactive interface, so as to by the Business Entity data display.
The query context inquiry business solid data that RowKey is generated by the tenant identification specifically includes:Inquiry The Key-Value databases set query context, described according to the table name of the mark of the tenant and the Business Entity In the query context of setting, inquiry is carried out according to querying condition set by user and obtains the Business Entity data.
In the example operation phase, Key- is inserted into using tenant identification as the RowKey prefixes of all Business Entity data Value databases generate RowKey query contexts by the tenant identification and take out Business Entity number from Key-Value databases According to according to the specific transactions entity metadata generation interactive interface after customization.
It is described to be specifically included according to specific transactions entity metadata generation interactive interface:
The specific transactions entity metadata of the tenant is obtained according to the mark of the tenant;
According to the index column information of the specific transactions entity metadata of the tenant and data type generation query term;
Display label and Business Entity data display inquiry knot in the specific transactions entity metadata of the tenant Fruit;
It is shown according to the display label of Business Entity of the specific transactions entity metadata of the tenant, the attribute of Business Entity The New any of the newly-built page of the data type of indicating label and Business Entity generation.
The Business Entity data that Key-Value databases are inserted into using tenant identification as RowKey prefixes are specifically gone back Including:Using RowKey prefix of the table name as the Business Entity data of mark+Business Entity of the tenant.
Business Entity " student " metadata is obtained by tenant identification " Tenant001 ", it is real by the business of the metadata Body attribute display label and data type generation create or the content and its pattern of the modification page.Whole user information is filled in, number According to insertion Key-Value databases.When being inserted into data, using " tenant identification+storehouse table name " as data RowKey's Prefix, such as " Tenant001CRMStudent001 ".Similarly, represent that " Tenant002 " obtains Business Entity " member by tenant 2 Work " generates the newly-built or modification page afterwards, while is inserted into employee " Tenant002CRMEmployee001 ", and tenant N is similarly such as This.Data at this time in the table of CRM storehouses are as shown in table 7, and wherein BASE represents initial service metadata structure table, and CUSTOM, which is represented, to be expanded Exhibition industry business metadata structure table:
Table 7CRM storehouses table data
RowKey Row
Tenant001CRMStudent001 BASE:USER_ID:Student001
Tenant001CRMStudent001 BASE:USER_NAME:King is small by two
Tenant001CRMStudent001 BASE:USER_EMAIL:wangxe@stu.com
Tenant001CRMStudent001 CUSTOM:STUDENT_LEVEL:1
Tenant002CRMEmployee001 BASE:USER_ID:Employee001
Tenant002CRMEmployee001 BASE:USER_NAME:Li Du
Tenant002CRMEmployee001 BASE:USER_EMAIL:lid@company.com
Tenant002CRMEmployee001 CUSTOM:DEPARTMENT:Research and development
During into query page, identify " Tenant001 " using tenant 1 and obtain Business Entity " student " metadata, in member All index entry generation query pages are obtained in data, index entry display label includes " student name ", " mailbox ", " grade ". Query result shows self-defined Business Entity all properties, including " student number ", " student name ", " mailbox ", " grade ".Similarly, " Tenant002 " is identified using tenant 2 and obtains Business Entity " employee " metadata, obtains all index entry generations in the metadata Query page, index entry display label include " employee name ", " mailbox ", " department ".Query result shows that self-defined business is real Body all properties, including " employee number ", " employee name ", " mailbox ", " department ".When inquiring about certain tenant's Ku Biao data, according to Tenant identification and storehouse table name setting query context, carry out inquiry according to querying condition set by user in the range and obtain number According to, specifically, StartRow is set as using " tenant identification+storehouse table name ", StartRow plus one are set as EndRow, All data of the tenant in the table of storehouse are i.e. within this range, so that the inquiry velocity of tenant is only and the tenant number of oneself It is related according to measuring, and it is unrelated with other tenant data amounts.In this case, when inquiring about 1 Business Entity of tenant " student " data, setting StartRow is " Tenant001CRM ", and EndRow is " Tenant 001CRN ", and after setting range, inquiry 1 data of tenant only need Matching inquiry condition in the range, without scanning entire database table.
Specifically, in the example operation phase, when 1 business demand of tenant changes, " learned if desired for for Business Entity It is raw " increase attribute " specialty ", then only it need to increase the information of the attribute and self-defined row name in database template, it need not Do any additional customized exploitation or deployment.Need to be only distribution when operator tenant, which increases, causes server capacity inadequate Key-Value databases increase server, need not do additional Data Migration.
In conclusion the present invention proposes a kind of multi-tenant extended method based on key-value database, this method is customizing Stage activates business entity according to domain knowledge on the basis of initial metadata, and defines the display of Business Entity and its attribute Label, generation meet the certain metadata of tenant's different business demand;In the generation example stage, the business extended according to user is real Voxel data creates Key-Value databases for tenant;In the example operation phase, when tenant is to database Insert service data, Business datum RowKey is generated for prefix with " tenant identification+storehouse table name ", by the specific transactions entity member number for obtaining tenant According to generation interactive interface, query context is set from database taking-up business datum by RowKey and is shown.The present invention supports logical It crosses customization generation and meets the application of tenant's individual demand, it can be to avoid overlapping development, together for the similar business of operation flow The Key-Value databases that Shi Caiyong shares facilitate realization to extend, and cut operating costs.
Professional should further appreciate that, be described with reference to the embodiments described herein each exemplary Unit and algorithm steps can be realized with the combination of electronic hardware, computer software or the two, hard in order to clearly demonstrate The interchangeability of part and software generally describes each exemplary composition and step according to function in the above description. These functions are performed actually with hardware or software mode, specific application and design constraint depending on technical solution. Professional technician can realize described function to each specific application using distinct methods, but this realization It is not considered that the scope beyond the embodiment of the present invention.
The step of method or algorithm for being described with reference to the embodiments described herein, can use hardware, processor to perform The combination of software module or the two is implemented.Software module can be placed in random access memory (RAM), memory, read-only memory (ROM), electrically programmable ROM, electrically erasable ROM, register, hard disk, moveable magnetic disc, CD-ROM or technical field In any other form of storage medium well known to interior.
Above-described specific embodiment, to the embodiment of the present invention, technical solution and advantageous effect carried out into one Step is described in detail, it should be understood that the foregoing is merely the specific embodiments of the embodiment of the present invention, is not used to limit Determine the protection domain of the embodiment of the present invention, all any modifications within the spirit and principle of the embodiment of the present invention, made are equal Replace, improve etc., it should be included within the protection domain of the embodiment of the present invention.

Claims (2)

1. a kind of multi-tenant extended method based on key-value database, which is characterized in that the described method includes:
Obtain initial service entity metadata;
Customization stage, attribute of activating business on the initial service entity metadata define the service attribute business reality Body and display label, generation meet the specific transactions entity metadata of multi-tenant demand;
The example stage is generated, according to the specific transactions entity metadata, creates key-value Key-Value databases;
The example operation phase is inserted into the Business Entity data of Key-Value databases using tenant identification as RowKey prefixes, The query context inquiry business solid data of RowKey is generated by the tenant identification, from described in the query context Business Entity data are taken out in Key-Value databases, interactive interface is generated according to the specific transactions entity metadata, so as to By the Business Entity data display;
In the generation example stage, the method further includes:
All tenants share a Key-Value database, the initial service entity metadata is corresponding be classified as it is all Tenant shares;
In the generation example stage, the method further includes:
It is described to activate business attribute for meeting the different business demand of the tenant, and at the same time generation and newly-increased business category The corresponding extension columns of property, the extension columns are only visible to the tenant;
The query context inquiry business solid data that RowKey is generated by the tenant identification specifically includes:Described in inquiry Key-Value databases set query context, in the setting according to the table name of the mark of the tenant and the Business Entity Query context in, inquiry is carried out according to querying condition set by user and obtains the Business Entity data;
It is described to be specifically included according to specific transactions entity metadata generation interactive interface:
The specific transactions entity metadata of the tenant is obtained according to the mark of the tenant;
According to the index column information of the specific transactions entity metadata of the tenant and data type generation query term;
Display label and Business Entity data in the specific transactions entity metadata of the tenant show query result;
According to the display label of the Business Entity of the specific transactions entity metadata of the tenant, the attribute display mark of Business Entity The New any of the newly-built page of the data type of label and Business Entity generation;
The Business Entity data that Key-Value databases are inserted into using tenant identification as RowKey prefixes are specifically also wrapped It includes:Using RowKey prefix of the table name as the Business Entity data of mark+Business Entity of the tenant;
In the customization stage, tenant is on the basis of initial service entity metadata, according to domain knowledge to initial service entity member number According to being customized, by changing initial column information, increase self-defined column information generation tenant's specific transactions entity metadata.
2. the multi-tenant extended method according to claim 1 based on key-value database, which is characterized in that described initial Business Entity metadata and the specific transactions entity metadata include at least:The table name of Business Entity, Business Entity it is aobvious Indicating label, the attribute column name of Business Entity, the data type of Business Entity, the index column of Business Entity mark and Business Entity Attribute display label.
CN201410771826.8A 2014-12-12 2014-12-12 Multi-tenant extended method based on key-value database Active CN104462421B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201410771826.8A CN104462421B (en) 2014-12-12 2014-12-12 Multi-tenant extended method based on key-value database

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201410771826.8A CN104462421B (en) 2014-12-12 2014-12-12 Multi-tenant extended method based on key-value database

Publications (2)

Publication Number Publication Date
CN104462421A CN104462421A (en) 2015-03-25
CN104462421B true CN104462421B (en) 2018-06-05

Family

ID=52908456

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201410771826.8A Active CN104462421B (en) 2014-12-12 2014-12-12 Multi-tenant extended method based on key-value database

Country Status (1)

Country Link
CN (1) CN104462421B (en)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105824763B (en) * 2015-11-16 2019-05-17 广东亿迅科技有限公司 A kind of buffer service implementation method
CN105631019A (en) * 2015-12-29 2016-06-01 畅捷通信息技术股份有限公司 Metadata extension method and device
CN106202540A (en) * 2016-07-26 2016-12-07 浪潮通用软件有限公司 Database horizontal expansion method of large application system
CN106469224A (en) * 2016-09-26 2017-03-01 武汉工程大学 A kind of expansible data model for SaaS platform
US11500836B2 (en) * 2017-06-27 2022-11-15 Salesforce, Inc. Systems and methods of creation and deletion of tenants within a database
CN108446363B (en) * 2018-03-13 2021-05-25 北京奇安信科技有限公司 Data processing method and device of KV engine
CN111126876A (en) * 2019-12-31 2020-05-08 亚信科技(中国)有限公司 Method and device for realizing service configuration based on plug-in technology
CN112069210A (en) * 2020-08-21 2020-12-11 北京首汽智行科技有限公司 Saas platform multi-tenant data isolation method
CN112597169A (en) * 2020-12-30 2021-04-02 山东恒远智能科技有限公司 Method for realizing industrial software multi-tenant data isolation
CN112883300B (en) * 2021-02-02 2022-08-30 广州华多网络科技有限公司 Function label customizing method and device, equipment and medium thereof

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101777057A (en) * 2004-04-02 2010-07-14 易享信息技术(上海)有限公司 Methods and systems for storing customer fields for multiple tenants in multi-tenant database system
CN102200977A (en) * 2010-03-23 2011-09-28 国际商业机器公司 Method and system for extending database table under multi-tenant environment

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070255741A1 (en) * 2006-04-28 2007-11-01 Business Objects, S.A. Apparatus and method for merging metadata within a repository

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101777057A (en) * 2004-04-02 2010-07-14 易享信息技术(上海)有限公司 Methods and systems for storing customer fields for multiple tenants in multi-tenant database system
CN102200977A (en) * 2010-03-23 2011-09-28 国际商业机器公司 Method and system for extending database table under multi-tenant environment

Also Published As

Publication number Publication date
CN104462421A (en) 2015-03-25

Similar Documents

Publication Publication Date Title
CN104462421B (en) Multi-tenant extended method based on key-value database
US10747762B2 (en) Automatic generation of sub-queries
US6859805B1 (en) Method and apparatus for generating page-level security in a computer generated report
Gonzalez et al. Google fusion tables: data management, integration and collaboration in the cloud
US20170255709A1 (en) Atomic updating of graph database index structures
US10402386B2 (en) Method and apparatus for generating index for encrypted field in database
US10671671B2 (en) Supporting tuples in log-based representations of graph databases
US20170255708A1 (en) Index structures for graph databases
CN103729337B (en) report conversion method and device
Leydesdorff et al. Aggregated journal–journal citation relations in scopus and web of science matched and compared in terms of networks, maps, and interactive overlays
AU2015347304B2 (en) Testing insecure computing environments using random data sets generated from characterizations of real data sets
CN106909566A (en) A kind of Data Modeling Method and equipment
US6772156B1 (en) Method and apparatus for creating and displaying a table of content for a computer-generated report having page-level security
CN105117442B (en) A kind of big data querying method based on probability
US10445370B2 (en) Compound indexes for graph databases
CN108984598A (en) A kind of fusion method and system of relationship type geologic database and NoSQL
CN108319608A (en) The method, apparatus and system of access log storage inquiry
EP3095066A1 (en) Compartment-based data security
WO2017101643A1 (en) Method and device for image storage
JP2019520627A (en) Use of B-trees to store graph information in a database
US20090193004A1 (en) Apparatus and method for forming database tables from queries
US20180357328A1 (en) Functional equivalence of tuples and edges in graph databases
CN111126461A (en) Intelligent auditing method based on machine learning model explanation
Janecka et al. 3D cadastres best practices, chapter 4: 3D spatial DBMS for 3D cadastres
US20180349443A1 (en) Edge store compression in graph databases

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant
TR01 Transfer of patent right
TR01 Transfer of patent right

Effective date of registration: 20210813

Address after: 100190, No. 21 West Fourth Ring Road, Beijing, Haidian District

Patentee after: INSTITUTE OF ACOUSTICS, CHINESE ACADEMY OF SCIENCES

Address before: 100190 Institute of acoustics, Chinese Academy of Sciences, No. 21 West Fourth Ring Road, Haidian District, Beijing

Patentee before: INSTITUTE OF ACOUSTICS, CHINESE ACADEMY OF SCIENCES

Patentee before: BEIJING INTELLIX TECHNOLOGIES Co.,Ltd.

Effective date of registration: 20210813

Address after: Room 1601, 16th floor, East Tower, Ximei building, No. 6, Changchun Road, high tech Industrial Development Zone, Zhengzhou, Henan 450001

Patentee after: Zhengzhou xinrand Network Technology Co.,Ltd.

Address before: 100190, No. 21 West Fourth Ring Road, Beijing, Haidian District

Patentee before: INSTITUTE OF ACOUSTICS, CHINESE ACADEMY OF SCIENCES