CN104462421A - Multi-tenant expanding method based on Key-Value database - Google Patents
Multi-tenant expanding method based on Key-Value database Download PDFInfo
- Publication number
- CN104462421A CN104462421A CN201410771826.8A CN201410771826A CN104462421A CN 104462421 A CN104462421 A CN 104462421A CN 201410771826 A CN201410771826 A CN 201410771826A CN 104462421 A CN104462421 A CN 104462421A
- Authority
- CN
- China
- Prior art keywords
- tenant
- business entity
- key
- entity
- business
- 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.)
- Granted
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2453—Query optimisation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
Abstract
An embodiment of the invention relates to a multi-tenant expanding method based on Key-Value database. The method includes acquiring initial business entity metadata; a customizing phase, an instance generating phase and an instance operating phase, wherein the customizing phase is expanding business attributes based on the initial business entity metadata, and defining business entities and displaying labels of the business attributes to generate specific business entity metadata meeting multi-tenant requirements; the instance generating phase is establishing a Key-Value database according to the specific business entity metadata; the instance operating phase is inserting tenant identifications as RowKey prefixes to the business entity data of Key-Value database, generating a query scope of RowKey to query business entity data through the tenant identifications, extracting the business entity data from the Key-Value database in the query scope and generating an interactive interface according to the specific business entity metadata, so as to display the business entity data.
Description
Technical field
The present invention relates to computer realm, particularly relate to a kind of many tenants extended method based on key-Value Data storehouse.
Background technology
The fast development of Internet technology makes traditional database face huge challenge when tackling mass data, distributed key-value Key-Value database arises at the historic moment, Key-Value database comprise increase income non-relational distributed data base HBase, non-relational database Cassandra, non-relational the no SQL of database etc.The distributed architecture of Key-Value database, relative traditional Relational DataBase has and can store mass data, and a table can have more than one hundred million row; Store towards row, towards storage and the control of authority of row (race), the independent retrieval of row (race); Sparse storage, for the row of sky, does not take storage space, and that table can be designed is very sparse.
Many tenants technology is mainly used in multiple tenant and shares hardware resource, the public Application Instance of multiple tenant.In prior art, many tenants technology mainly comprises following three kinds of schemes in data storage:
1. each tenant has self contained data base
For different tenant provides separate database, such data isolation is best, and owing to can be the independent design data library structure of different user, contributes to the design of reduced data library structure, breaks down and recovers also relatively simple.But set up self contained data base for each tenant, different tenant not really share hardware resource, acquisition cost and maintenance cost high, general operator cannot accept.
2. tenant's shared data bank, but have independent storehouse table
All tenants share a database, but different tenant has independently storehouse table.Provide isolation between certain data, the trouble relatively but expansion is got up, be not easy to expansion, cost is also higher, difficult across tenant data statistics.
3. tenant's shared data bank, shared data bank table
All tenant's shared data banks, shared library table, this method cost is minimum, and sharing degree is the highest, allows the tenant supported also maximum, but differs due to the business demand between different tenant, therefore needs well-designed database for this situation.When adopting traditional Relational DataBase, when tenant needs to add custom field, need to add row in a database, for certain tenant, the row that other tenants add are useless row to this tenant, but need to exist in a database, but when tenant's quantity is larger, need to increase a large amount of row in a database, this just causes there is a large amount of null values in database, very wasting space.
Summary of the invention
Embodiments provide a kind of many tenants extended method based on key-Value Data storehouse, effectively reduce operation cost and the maintenance cost of multi-tenant database, increase the extendability of multi-tenant database, reduce the customization cost of tenant and shorten the customization cycle.
Embodiments provide a kind of many tenants extended method based on key-Value Data storehouse, described method comprises:
Obtain initial service entity metadata;
In the customization stage, attribute that described initial service entity metadata is activated business, to described service attribute definition Business Entity and display label, generates the specific transactions entity metadata meeting many tenants demand;
Generate the example stage, according to described specific transactions entity metadata, create key-value Key-Value database;
The example operation phase, the Business Entity data of Key-Value database are inserted into using tenant identification as RowKey prefix, the query context inquiry business solid data of RowKey is generated by described tenant identification, from described Key-Value database, Business Entity data are taken out in described query context, interactive interface is generated, so that by described Business Entity data display according to described specific transactions entity metadata.
Preferably, described initial service entity metadata and described specific transactions entity metadata all at least comprise: the index column mark of the attribute column name of the table name of Business Entity, the display label of Business Entity, Business Entity, the data type of Business Entity, Business Entity and the attribute display label of Business Entity.
Preferably, in the described generation example stage, described method also comprises:
All tenants share a described Key-Value database, and what described initial service entity metadata was corresponding be classified as, and all tenants share.
Preferably, in the described generation example stage, described method also comprises:
Described attribute of activating business for meeting the different business demand of described tenant, and generates the extension columns corresponding with newly-increased service attribute simultaneously, and described extension columns is only visible to described tenant.
Preferably, the described Business Entity data being inserted into Key-Value database using tenant identification as RowKey prefix specifically also comprise: adopt the table name of the mark of described tenant+described Business Entity as the RowKey prefix of described Business Entity data.
Preferably, the described query context inquiry business solid data by described tenant identification generation RowKey specifically comprises: inquire about described Key-Value database, according to the mark of described tenant and the table name setting query context of described Business Entity, in the query context of described setting, carry out inquiry according to the querying condition of user's setting and obtain described Business Entity data.
Preferably, describedly generate interactive interface according to described specific transactions entity metadata and specifically comprise:
The specific transactions entity metadata of described tenant is obtained according to the mark of described tenant;
According to index column information and the data type generated query item of the specific transactions entity metadata of described tenant;
According to the display label in the specific transactions entity metadata of described tenant and Business Entity data display Query Result;
The New any of the newly-built page is generated according to the data type of the display label of the Business Entity of the specific transactions entity metadata of described tenant, the attribute display label of Business Entity and Business Entity.
The many tenants extended method based on key-Value Data storehouse that the present invention proposes, can produce positive beneficial effect, specific as follows: support to generate by customization the application meeting tenant's individual demand, the business similar for operation flow can avoid overlapping development; Adopt the Key-Value database shared conveniently to realize expansion, cut operating costs, along with the growth of newly-increased tenant, along with tenant userbase growth, the RowKey prefix of the present invention using tenant identification as all Business Entity data, conveniently realizes expansion, cuts operating costs.
Accompanying drawing explanation
The many tenants extended method process flow diagram based on key-Value Data storehouse that Fig. 1 provides for the embodiment of the present invention one;
The theory diagram of the many tenants extended method based on key-Value Data storehouse that Fig. 2 provides for the embodiment of the present invention two.
Embodiment
For making the object, technical solutions and advantages of the present invention clearly, below in conjunction with accompanying drawing, the specific embodiment of the invention is described in further detail.
Embodiment one
Below for the many tenants extended method based on key-Value Data storehouse that Fig. 1 detailed description embodiment of the present invention one provides, the many tenants extended method process flow diagram based on key-Value Data storehouse that Fig. 1 provides for the embodiment of the present invention, subject of implementation can be operation supporting platform in embodiments of the present invention.Fig. 2 shows the theory diagram of the many tenants extended method based on key-Value Data storehouse that the embodiment of the present invention proposes.As shown in Figure 2, in the many tenants extended method based on key-Value Data storehouse that the present invention proposes, adopt the operation supporting platform of the definable many tenants of easily extensible, this platform adopts distributed Key-Value database purchase business information.Shown in composition graphs 1 and Fig. 2, the method comprises the steps:
Step 101, acquisition initial service entity metadata;
Initial service entity metadata at least comprises: the index column mark of the attribute column name of the table name of Business Entity, the display label of Business Entity, Business Entity, the data type of Business Entity, Business Entity and the attribute display label of Business Entity.
Step 102, customization stage, attribute that described initial service entity metadata is activated business, to described service attribute definition Business Entity and display label, generates the specific transactions entity metadata meeting many tenants demand.
Described initial service entity metadata and described specific transactions entity metadata all at least comprise: the index column mark of the attribute column name of the table name of Business Entity, the display label of Business Entity, Business Entity, the data type of Business Entity, Business Entity and the attribute display label of Business Entity.
Particularly, operation supporting platform formulates each module initial service entity metadata according to each modular service demand before disposing, and creates Key-Value data Kuku table according to initial service metadata, and such as, wherein service metadata structure is mainly as shown in table 1:
Table 1 service metadata structural table
As shown in table 2 according to template establishment database table CRM structure:
Table 2 database table CRM structural table
Step 103, generation example stage, according to described specific transactions entity metadata, create key-value Key-Value database.
In the described generation example stage, described method also comprises:
All tenants share a described Key-Value database, and what described initial service entity metadata was corresponding be classified as, and all tenants share.
Particularly, in the customization stage, tenant, on initial service entity metadata basis, customizes initial service entity metadata according to domain knowledge, by amendment initial column information, increases self-defined column information and generates tenant's specific transactions entity metadata.
Tenant 1 is certain educational institution, according to business demand, entity title corresponding for CRM is changed into " student "; Attribute tags in initial service entity metadata corresponding to " USER_NAME " row changes into " student name ", and " USER_ID " corresponding attribute tags changes into " student number "; For Business Entity " student " increases attribute " grade ", and define corresponding self-defined row, by above customization, it is as shown in table 3 that tenant 1 generates self-defined Business Entity metadata:
The self-defined Business Entity metadata that table 3 tenant 1 generates
Tenant 2 is certain corporate user, according to business demand, entity title corresponding for CRM is changed into " employee "; Attribute tags in initial service entity metadata corresponding to " USER_NAME " row changes into " employee name ", and " USER_ID " corresponding attribute tags changes into " employee number "; For Business Entity " employee " increases attribute " department ", and define corresponding self-defined row, by above customization, it is as shown in table 4 that tenant 2 generates self-defined Business Entity metadata:
The self-defined Business Entity metadata that table 4 tenant 2 generates
According to the self-defined Business Entity metadata that tenant 1 and tenant 2 generate, we can define several similar self-defined Business Entity metadata, we suppose that tenant N is certain enterprise management level personnel equally, according to business demand, entity title corresponding for CRM are changed into " manager "; Attribute tags in initial service entity metadata corresponding to " USER_NAME " row changes into " keeper ", and " USER_ID " corresponding attribute tags changes into " keeper number "; For Business Entity " employee " increases attribute " department ", and define corresponding self-defined row, by above customization, it is as shown in table 5 that tenant N generates self-defined Business Entity metadata:
The self-defined Business Entity metadata that table 5 tenant N generates
In the described generation example stage, described method also comprises:
Described attribute of activating business for meeting the different business demand of described tenant, and generates the extension columns corresponding with newly-increased service attribute simultaneously, and described extension columns is only visible to described tenant.
Different tenant generates example after adopting identical initial service entity metadata to expand and shares same database table, and what initial service entity metadata was corresponding be classified as all tenants shares; Meanwhile, the Custom Attributes of specific transactions entity generated according to tenant is self-defined extension columns for tenant adds, and self-defined extension columns is from this tenant.After certain tenant adds self-defined row, only have this tenant to add data at these row, due to the sparse row storage characteristics of Key-Value database, there are not the data of the self-defined row of this tenant in other tenants, does not take any redundant space yet.Now tenant 1 Business Entity " student ", tenant 2 Business Entity " employee " the Key-Value database table CRM structure automatic expansion shared with tenant N Business Entity " keeper " becomes table 6:
Table 6Key-Value database table CRM structure extension table
Step 104, example operation phase, the Business Entity data of Key-Value database are inserted into using tenant identification as RowKey prefix, the query context inquiry business solid data of RowKey is generated by described tenant identification, from described Key-Value database, Business Entity data are taken out in described query context, interactive interface is generated, so that by described Business Entity data display according to described specific transactions entity metadata.
The described query context inquiry business solid data by described tenant identification generation RowKey specifically comprises: inquire about described Key-Value database, according to the mark of described tenant and the table name setting query context of described Business Entity, in the query context of described setting, carry out inquiry according to the querying condition of user's setting and obtain described Business Entity data.
In the example operation phase, Key-Value database is inserted using tenant identification as the RowKey prefix of all Business Entity data, generate RowKey query context by described tenant identification and take out Business Entity data from Key-Value database, generate interactive interface according to the described specific transactions entity metadata after customization.
Describedly generate interactive interface according to described specific transactions entity metadata and specifically comprise:
The specific transactions entity metadata of described tenant is obtained according to the mark of described tenant;
According to index column information and the data type generated query item of the specific transactions entity metadata of described tenant;
According to the display label in the specific transactions entity metadata of described tenant and Business Entity data display Query Result;
The New any of the newly-built page is generated according to the data type of the display label of the Business Entity of the specific transactions entity metadata of described tenant, the attribute display label of Business Entity and Business Entity.
The described Business Entity data being inserted into Key-Value database using tenant identification as RowKey prefix specifically also comprise: adopt the table name of the mark of described tenant+described Business Entity as the RowKey prefix of described Business Entity data.
Obtain Business Entity " student " metadata by tenant identification " Tenant001 ", generated content and the pattern thereof of the newly-built or amendment page by the Business Entity attribute display label of this metadata and data type.Fill in whole user information, data insert Key-Value database.During data inserting, adopt " tenant identification+storehouse table name claims " as the prefix of this data RowKey, as " Tenant001CRMStudent001 ".In like manner, represent that " Tenant002 " obtains Business Entity " employee " and generate the newly-built or amendment page afterwards by tenant 2, insert employee " Tenant002CRMEmployee001 ", tenant N is like this too simultaneously.Data now in the table of CRM storehouse are as shown in table 7, and wherein BASE represents initial service metadata structure table, and CUSTOM represents metadata structure table of activating business:
Table 7CRM storehouse table data
| RowKey | Row |
| Tenant001CRMStudent001 | BASE:USER_ID:Student001 |
| Tenant001CRMStudent001 | BASE:USER_NAME: a king young waiter in a wineshop or an inn |
| 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 |
When entering query page, utilize tenant 1 to identify " Tenant001 " and obtain Business Entity " student " metadata, obtain all index entry generated query pages in the metadata, index entry display label comprises " student name ", " mailbox ", " grade ".Query Result shows self-defined Business Entity all properties, comprises " student number ", " student name ", " mailbox ", " grade ".In like manner, utilize tenant 2 to identify " Tenant002 " and obtain Business Entity " employee " metadata, obtain all index entry generated query pages in the metadata, index entry display label comprises " employee name ", " mailbox ", " department ".Query Result shows self-defined Business Entity all properties, comprises " employee number ", " employee name ", " mailbox ", " department ".When inquiring about certain tenant Ku Biao data, claim to set query context according to tenant identification and storehouse table name, within the scope of this, carry out inquiry according to the querying condition of user's setting obtain data, specifically, adopt " tenant identification+storehouse table name claims " to be set as StartRow, StartRow is added one and is set as EndRow, all data of this tenant in the table of storehouse are namely within the scope of this, make the inquiry velocity of tenant only relevant with the data volume of this tenant oneself like this, and have nothing to do with other tenant data amounts.In this case, during inquiry tenant 1 Business Entity " student " data, set StartRow as " Tenant001CRM ", EndRow is " Tenant 001CRN ", after setting range, inquiry tenant 1 data only need within the scope of this matching inquiry condition, and do not need to scan whole database table.
Particularly, in the example operation phase, when tenant 1 business demand changes, as needs for Business Entity " student " increases attribute " specialty ", then only need increase the information of this attribute and self-defined row name in database template, not need do the exploitation of any additional customized or dispose.When operator tenant increase causes server capacity inadequate, being only required to be distributed Key-Value database increases server, does not need to do extra Data Migration.
In sum, the present invention proposes a kind of many tenants extended method based on key-Value Data storehouse, the method is in the customization stage, to activate business entity according to domain knowledge in initial metadata basis, and define the display label of Business Entity and attribute thereof, generate the certain metadata meeting tenant's different business demand; In the generation example stage, according to the Business Entity metadata of user's expansion, for tenant creates Key-Value database; In the example operation phase, when tenant is to database Insert service data, with " tenant identification+storehouse table name claims " for prefix generates business datum RowKey, generate interactive interface by the specific transactions entity metadata obtaining tenant, set query context by RowKey and take out business datum showing from database.Support of the present invention generates the application meeting tenant's individual demand by customization, the business similar for operation flow can avoid overlapping development, adopts shared Key-Value database conveniently to realize expansion simultaneously, cuts operating costs.
Professional should recognize further, in conjunction with unit and the algorithm steps of each example of embodiment disclosed herein description, can realize with electronic hardware, computer software or the combination of the two, in order to the interchangeability of hardware and software is clearly described, generally describe composition and the step of each example in the above description according to function.These functions perform with hardware or software mode actually, depend on application-specific and the design constraint of technical scheme.Professional and technical personnel can use distinct methods to realize described function to each specifically should being used for, but this realization should not think the scope exceeding the embodiment of the present invention.
The software module that the method described in conjunction with embodiment disclosed herein or the step of algorithm can use hardware, processor to perform, or the combination of the two is implemented.Software module can be placed in the storage medium of other form any known in random access memory (RAM), internal memory, ROM (read-only memory) (ROM), electrically programmable ROM, electrically erasable ROM, register, hard disk, moveable magnetic disc, CD-ROM or technical field.
Above-described embodiment; to the embodiment of the present invention, technical scheme and beneficial effect further describe; be understood that; the foregoing is only the embodiment of the embodiment of the present invention; be not intended to limit the present invention the protection domain of embodiment; within all spirit in the embodiment of the present invention and principle, any amendment made, equivalent replacement, improvement etc., within the protection domain that all should be included in the embodiment of the present invention.
Claims (7)
1. based on many tenants extended method in key-Value Data storehouse, it is characterized in that, described method comprises:
Obtain initial service entity metadata;
In the customization stage, attribute that described initial service entity metadata is activated business, to described service attribute definition Business Entity and display label, generates the specific transactions entity metadata meeting many tenants demand;
Generate the example stage, according to described specific transactions entity metadata, create key-value Key-Value database;
The example operation phase, the Business Entity data of Key-Value database are inserted into using tenant identification as RowKey prefix, the query context inquiry business solid data of RowKey is generated by described tenant identification, from described Key-Value database, Business Entity data are taken out in described query context, interactive interface is generated, so that by described Business Entity data display according to described specific transactions entity metadata.
2. the many tenants extended method based on key-Value Data storehouse according to claim 1, it is characterized in that, described initial service entity metadata and described specific transactions entity metadata all at least comprise: the index column mark of the attribute column name of the table name of Business Entity, the display label of Business Entity, Business Entity, the data type of Business Entity, Business Entity and the attribute display label of Business Entity.
3. the many tenants extended method based on key-Value Data storehouse according to claim 1, is characterized in that, in the described generation example stage, described method also comprises:
All tenants share a described Key-Value database, and what described initial service entity metadata was corresponding be classified as, and all tenants share.
4. the many tenants extended method based on key-Value Data storehouse according to claim 3, is characterized in that, in the described generation example stage, described method also comprises:
Described attribute of activating business for meeting the different business demand of described tenant, and generates the extension columns corresponding with newly-increased service attribute simultaneously, and described extension columns is only visible to described tenant.
5. the many tenants extended method based on key-Value Data storehouse according to claim 1, it is characterized in that, the described Business Entity data being inserted into Key-Value database using tenant identification as RowKey prefix specifically also comprise: adopt the table name of the mark of described tenant+described Business Entity as the RowKey prefix of described Business Entity data.
6. the many tenants extended method based on key-Value Data storehouse according to claim 1, it is characterized in that, the described query context inquiry business solid data by described tenant identification generation RowKey specifically comprises: inquire about described Key-Value database, according to the mark of described tenant and the table name setting query context of described Business Entity, in the query context of described setting, carry out inquiry according to the querying condition of user's setting and obtain described Business Entity data.
7. the many tenants extended method based on key-Value Data storehouse according to claim 6, is characterized in that, describedly generates interactive interface according to described specific transactions entity metadata and specifically comprises:
The specific transactions entity metadata of described tenant is obtained according to the mark of described tenant;
According to index column information and the data type generated query item of the specific transactions entity metadata of described tenant;
According to the display label in the specific transactions entity metadata of described tenant and Business Entity data display Query Result;
The New any of the newly-built page is generated according to the data type of the display label of the Business Entity of the specific transactions entity metadata of described tenant, the attribute display label of Business Entity and Business Entity.
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 true CN104462421A (en) | 2015-03-25 |
| CN104462421B 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) |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105631019A (en) * | 2015-12-29 | 2016-06-01 | 畅捷通信息技术股份有限公司 | Metadata extension method and device |
| CN105824763A (en) * | 2015-11-16 | 2016-08-03 | 广东亿迅科技有限公司 | Caching service realization method |
| CN106202540A (en) * | 2016-07-26 | 2016-12-07 | 浪潮通用软件有限公司 | The data base of a kind of large-scale application system can method extending transversely |
| CN106469224A (en) * | 2016-09-26 | 2017-03-01 | 武汉工程大学 | A kind of expansible data model for SaaS platform |
| CN108446363A (en) * | 2018-03-13 | 2018-08-24 | 北京奇安信科技有限公司 | A kind of data processing method and device of KV engines |
| CN110799961A (en) * | 2017-06-27 | 2020-02-14 | 易享信息技术有限公司 | System and method for creating and deleting tenants in database |
| 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 |
| CN112883300A (en) * | 2021-02-02 | 2021-06-01 | 广州华多网络科技有限公司 | Function label customizing method and device, equipment and medium thereof |
Citations (3)
| 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 |
| 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 |
-
2014
- 2014-12-12 CN CN201410771826.8A patent/CN104462421B/en active Active
Patent Citations (3)
| 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 |
| US20070255741A1 (en) * | 2006-04-28 | 2007-11-01 | Business Objects, S.A. | Apparatus and method for merging metadata within a repository |
| CN102200977A (en) * | 2010-03-23 | 2011-09-28 | 国际商业机器公司 | Method and system for extending database table under multi-tenant environment |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105824763B (en) * | 2015-11-16 | 2019-05-17 | 广东亿迅科技有限公司 | A kind of buffer service implementation method |
| CN105824763A (en) * | 2015-11-16 | 2016-08-03 | 广东亿迅科技有限公司 | Caching service realization method |
| CN105631019A (en) * | 2015-12-29 | 2016-06-01 | 畅捷通信息技术股份有限公司 | Metadata extension method and device |
| CN106202540A (en) * | 2016-07-26 | 2016-12-07 | 浪潮通用软件有限公司 | The data base of a kind of large-scale application system can method extending transversely |
| CN106469224A (en) * | 2016-09-26 | 2017-03-01 | 武汉工程大学 | A kind of expansible data model for SaaS platform |
| CN110799961A (en) * | 2017-06-27 | 2020-02-14 | 易享信息技术有限公司 | System and method for creating and deleting tenants in database |
| CN110799961B (en) * | 2017-06-27 | 2023-12-26 | 硕动力公司 | System and method for creating and deleting tenants in database |
| CN108446363A (en) * | 2018-03-13 | 2018-08-24 | 北京奇安信科技有限公司 | A kind of data processing method and device of KV engines |
| 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 |
| CN112883300A (en) * | 2021-02-02 | 2021-06-01 | 广州华多网络科技有限公司 | Function label customizing method and device, equipment and medium thereof |
| CN112883300B (en) * | 2021-02-02 | 2022-08-30 | 广州华多网络科技有限公司 | Function label customizing method and device, equipment and medium thereof |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104462421B (en) | 2018-06-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104462421A (en) | Multi-tenant expanding method based on Key-Value database | |
| US10180992B2 (en) | Atomic updating of graph database index structures | |
| Gonzalez et al. | Google fusion tables: data management, integration and collaboration in the cloud | |
| Li | Transforming relational database into HBase: A case study | |
| Sharma et al. | Sql and nosql databases | |
| CN102467521B (en) | Easily-extensible multi-level classification search method and system | |
| US10671671B2 (en) | Supporting tuples in log-based representations of graph databases | |
| US20180144061A1 (en) | Edge store designs for graph databases | |
| CN111427847B (en) | Indexing and querying method and system for user-defined metadata | |
| CN102646039A (en) | Software interface generating system and method based on extensible markup language (XML) Schema | |
| US8880463B2 (en) | Standardized framework for reporting archived legacy system data | |
| CN107977396B (en) | Method and device for updating data table of KeyValue database | |
| CN104346466B (en) | The method and apparatus for the data that Added New Attribute in database | |
| US7860903B2 (en) | Techniques for generic data extraction | |
| CN104537129A (en) | Web based database virtual storage processing method | |
| CN105389367A (en) | Power network graphic multi-tense and multi-level distributed storage method based on Mongo database | |
| US20180357330A1 (en) | Compound indexes for graph databases | |
| CN106503040B (en) | It is applicable in the KV database and its creation method of SQL query method | |
| CN104021210B (en) | Geographic data reading and writing method of MongoDB cluster of geographic data stored in GeoJSON-format semi-structured mode | |
| CN101963993B (en) | Method for fast searching database sheet table record | |
| EP3635580A1 (en) | Functional equivalence of tuples and edges in graph databases | |
| CN102360359A (en) | Data management device and data management method | |
| CN107992292A (en) | A kind of method defined by schema forms progress database | |
| US20180144060A1 (en) | Processing deleted edges in graph databases | |
| CN111008198A (en) | Service data acquisition method and device, storage medium and electronic equipment |
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 |
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 |
|
| TR01 | Transfer of patent right |