Abstract:
A system may be configured to implement two or more different types of data stores for data storage. For example, the system may include a small object data store and a large object data store. The system may compare the size of a data file to a predetermined threshold size. If the data file is smaller than the predetermined threshold size, the system may write the data to the small object data store. If the data is larger than the predetermined threshold size, the system may write an intent message to the small object data store referencing the data in the large object data store, and may write the data to the large object data store. The system may update the intent message in the small object data store to indicate that the data was successfully written.
Abstract:
A database may delete rows of data based on one or more predicate parameters. A method of data storage includes receiving a delete request for a database, where the delete request includes one or more predicate parameters and adding the predicate parameters to a set of deletion predicate parameters in metadata of the database. The method may further include performing a compaction of the database, where the compaction includes rewriting each data element of the database unless a key of the data element corresponds to at least one of the set of deletion predicate parameters.
Abstract:
Systems and methods for installing and upgrading application packages to an application platform. Application packages may be uploaded to a directory by developing users (developers) for installation by subscribing users (subscribers). Alternatively, a developer may send identification information to a subscribing user to allow that user to access and install that application package created by the developer. Application packages may also be upgraded. If a developer changes the original source package, a subscriber can choose to pull into their organization the change(s) made by the publisher while preserving any data rows the subscriber had created since first importing the package.
Abstract:
A database system may store data at a primary database and replicate the data to one or more disaster recover (DR) databases. The database system may determine which DR database to use for data replication based on an identifier of the data. A method for data storage may include receiving and storing a first data block and a second data block at a first database server. The method may further include transmitting a first backup request for the first data block to a second database server based on an identifier of the first data block and transmitting a second backup request for the second data block to a third database server based on an identifier of the second data block.
Abstract:
A database may delete rows of data based on one or more predicate parameters. A method of data storage includes receiving a delete request for a database, where the delete request includes one or more predicate parameters and adding the predicate parameters to a set of deletion predicate parameters in metadata of the database. The method may further include performing a compaction of the database, where the compaction includes rewriting each data element of the database unless a key of the data element corresponds to at least one of the set of deletion predicate parameters.
Abstract:
A database may store a plurality of database revisions corresponding to a time period, including a current version and one or more backup versions of a data object. After a threshold time has passed, the database may identify a plurality of time intervals within the time period and identify, for each of the plurality of time intervals, at most one database revision corresponding to the time interval. The database may delete, for each of the plurality of time intervals, all of the database revisions except for the identified at most one database revision. The database may periodically repeat this process to reduce the granularity of backup data over time.
Abstract:
Systems and methods for installing and upgrading application packages to an application platform. Application packages may be uploaded to a directory by developing users (developers) for installation by subscribing users (subscribers). Alternatively, a developer may send identification information to a subscribing user to allow that user to access and install that application package created by the developer. Application packages may also be upgraded. If a developer changes the original source package, a subscriber can choose to pull into their organization the change(s) made by the publisher while preserving any data rows the subscriber had created since first importing the package.
Abstract:
A system may be configured to implement two or more different types of data stores for data storage. For example, the system may include a small object data store and a large object data store. The system may compare the size of a data file to a predetermined threshold size. If the data file is smaller than the predetermined threshold size, the system may write the data to the small object data store. If the data is larger than the predetermined threshold size, the system may write an intent message to the small object data store referencing the data in the large object data store, and may write the data to the large object data store. The system may update the intent message in the small object data store to indicate that the data was successfully written.
Abstract:
Systems and methods for installing and upgrading application packages to an application platform. Application packages may be uploaded to a directory by developing users (developers) for installation by subscribing users (subscribers). Alternatively, a developer may send identification information to a subscribing user to allow that user to access and install that application package created by the developer. Application packages may also be upgraded. If a developer changes the original source package, a subscriber can choose to pull into their organization the change(s) made by the publisher while preserving any data rows the subscriber had created since first importing the package.
Abstract:
Systems and methods for installing and upgrading application packages to an application platform. Application packages may be uploaded to a directory by developing users (developers) for installation by subscribing users (subscribers). Alternatively, a developer may send identification information to a subscribing user to allow that user to access and install that application package created by the developer. Application packages may also be upgraded. If a developer changes the original source package, a subscriber can choose to pull into their organization the change(s) made by the publisher while preserving any data rows the subscriber had created since first importing the package.