Abstract: The present disclosure discloses methods and systems for managing different versions of a document in a document management system. The method includes receiving a request at the document management system from a user to access a document, wherein the document management system stores multiple versions of the document along with respective location information. Further, the method includes checking whether a location option is enabled at the document management system. Furthermore, based on the check, a version of the document matching the location of the user from where the user is accessing it, is presented to the user, via a user interface, for further action. The methods and systems further allow the user to upload one or more documents versions, where the document versions are stored along with location information for easy access, later retrieval and/or use.

Abstract: Disclosed embodiments relate to systems and methods for securely performing actions on a resource. Techniques include receiving a request by the entity to perform a privileged action on a resource, the request including a token associated with the entity; providing a first indication of the request to a first handler; providing a second indication of the request to a second handler configured to perform the privileged action on the resource, wherein when the privileged action includes a query, the second indication of the request is provided to a query handler, and when the privileged action includes a write command, the second indication of the request is provided to a command handler.

Abstract: Embodiments disclosed herein provide systems, methods, and computer readable media for data lineage based multi-data store recovery. In a particular embodiment, a method provides identifying first data in a first table of a plurality of tables stored in a plurality of data stores and restoring the first data to a first correct version of the first data in a prior version of the first table. The method further provides identifying a second table of the plurality of tables that descends from the first table and includes second descendent data that stems from the first data. The method also provides restoring the second descendent data to a second correct version of the second descendent data in a prior version of the second table.

Abstract: Provided are a computer program product, system and method for retaining versions of an object. Changes are appended to a current version object resulting in a new current version object and a most recent previous version object comprising the current version object before the changes were appended. Version metadata, for each previous version object, includes the most recent previous version object, indicating an offset in the new current version object at which the previous version object can be recovered. The most recent previous version object is deleted and the version metadata, for the most recent previous version object after the most recent previous version object is deleted, is retained to allow recovery of a previous version object from the new current version object using the offset in the version metadata.

Abstract: The invention enables automated revision comparison of engineering data within a process control system. In various embodiments, the invention achieves this by (i) receiving user input defining a set of data retrieval parameters that identify change-set data for an engineering data file, (ii) retrieving from among change-sets retrieved based on the data retrieval parameters, a first change-set and a second change-set, (iii) retrieving from an engineering database, first and second revisions of the engineering data file corresponding to the first change-set and the second change-set (iv) comparing the retrieved first and second revisions, and (v) displaying a deviation report that is generated based on the identified deviations between the first and second revisions.

Abstract: A method of testing a system model is disclosed. The system model includes a system parameter and three or more equipment models, each equipment model includes an equipment parameter which models a parameter of a respective equipment. The method includes (a) making a series of changes of the equipment parameter of one of the equipment models so that the equipment parameter of the one of the equipment models adopts a series of test values of the equipment parameter; (b) operating the system model to determine a series of test values of the system parameter, each test value of the system parameter is determined in accordance with a respective one of the test values of the equipment parameter; (c) determining a weight of the selected one of the equipment models, the weight of the one of the equipment models indicates a sensitivity of the system parameter to the series of changes in the equipment parameter of the one of the equipment models; and (d) outputting the weight of the one of the equipment models.

Abstract: Intelligence production suffers from inadequate collaboration, poor information sharing, and lack of visibility into a complex production process, resulting in intelligence reports that are not aligned to the user's needs. This exacerbates decision-making problems by preventing critical data from reaching the appropriate staff, which prevents commanders from achieving their desired mission requirements due to incomplete or inadequate information. Using Object-Based Production, Adaptive Process Management, and Entity Management technologies, a new wiki-like capability was created that provides a wiki's ease of use and understanding while addressing weaknesses such as lack of multi-level security, no enforcement of publishing standards, and lack of product currency, providing an intelligence production solution addressing the above needs.

Abstract: There is described a system and method for managing timeseries data. A timeseries consumer receives timeseries data from multiple devices, provides the timeseries data to a particular partition of a data table based on an insert time of the timeseries data to the data table, and records metadata associated with the timeseries data provided to the particular partition at a track table. A timeseries archiver identifies recent records of the data table based on insert time(s) and archival time(s) of a milestone table, archives the timeseries data of the data table associated with the recent records to an external system, and updates the archival time(s) of the milestone table and the track table. The timeseries purger drops an archived partition of the data table based on determining that all records of the archived partition have been archived.

Abstract: Performance data characterizing operations of an application may be collected by time interval, and a plurality of keys may be associated with each element of the performance data. A first time interval may be received. An iterative group-and-filter search may be executed against the keyed elements within the first time interval, each iteration including an iteration key used to perform a key-based grouping operation followed by a group-based filter operation, wherein each iteration key is added to a composite key at each iteration. A selection of at least one keyed element within the first time interval and obtained from the iterative group-and-filter search may be received. A second time interval that precedes the first time interval may be received, and the keyed elements may be filtered using the composite key and within the second time interval to return the at least one keyed element within the second time interval.

Abstract: A workflow project design system, method, and apparatus are disclosed. An example method includes creating a mapping between an executable version of an object-orientated process and an un-executable version of the object-orientated process. The method also includes transmitting the un-executable version of the object-orientated process and a toolset file to a client device for display in a web browser. The method further includes receiving from the client device a modify instruction to modify at least one of attributes or properties of the un-executable version of the object-orientated process and updating the executable version of the object-orientated process based on the modify instruction. Additionally, the method includes receiving an execution instruction to execute the workflow project, executing the updated executable version of the object-orientated process to generate a result of the workflow project, and transmitting to the client device the result for display within the user interface.

Abstract: Computer-implemented systems and methods are disclosed for indexing and aggregating proxy server data. In accordance with some embodiments, the systems comprise a memory device configured to store a set of instructions, and one or more processors configured to execute the set of instructions to receive a plurality of log lines of proxy server data comprising a plurality of data components and index one or more of the plurality of data components for the plurality of log lines. The processors also generate a plurality of log data records, each including the one or more indexed data components, and generate a summarized data record by aggregating one or more log data records having at least one matching indexed data component.

Abstract: In general, the invention relates to a method for performing backup operations. The method includes generating a backup on backup storage system, locking the backup for a retention span, generating a backup archive log image using archive log files for the backup, and locking the backup archive log image for a second retention span.

Abstract: A system for version control is presented. The system includes a computing device, wherein the computing device is configured to receive a package build, wherein the package build a package build manifest, identify a package syntax element from the package build perform a manifest search as a function of the package syntax element, produce a universal version element as a function of the manifest search, verify the universal version element as a function of a version authenticator, and install the package build as a function of the verification.

Abstract: Embodiments are described for a method of distributing n-tuples over a cluster of triple-store machines, by storing each n-tuple as text in a distributed file system using a key value store; providing each machine of the cluster with a resident semantic data lake component accessing one or more persistent RDF triplestores for the n-tuple data stored on each machine; and defining one part of each n-tuple as a partition variable to ensure locality of data within each respective n-tuple. A method includes inserting graphs into a key/value store to determine how the key/value store distributes the data across a plurality of servers, by generating textual triple data, and storing the triple data in key-value stores wherein a fourth element of the triple comprises the key, and a value associated with the key comprises all the triples about a subject; indexing the data in the key-value store in an RDF triplestore using a partition based on the fourth element.

Abstract: A data storage apparatus includes an interface and one or more processors. The interface is configured for communicating with a cloud-based object storage system 5 having a built-in versioning mechanism that assigns version numbers to objects stored therein. The one or more processors are configured to receive data for storage from one or more workloads, to store the data as objects in the cloud-based object storage system, and to 10 update and record reference counts for at least some of the objects, by forcing the built-in versioning mechanism of the cloud-based object storage system to update the version numbers so as to match the reference counts.

Abstract: A file system executing on a computing device may store a placeholder for a file on secondary storage of the computing device. The placeholder may comprise a sparse data stream containing none or some of the data of the file and information which enables the remotely stored data of the file to be retrieved from the network. As some or all of the data for the file is being stored remotely, the computing device may rely on a storage virtualization provider to create metadata for the file. Thus, the file system executing on the computing device may receive, from the storage virtualization provider, a request to store metadata associated with the file. In response to this request, the file system may store the metadata as a Binary Large Object (BLOB) in a secondary data stream of the placeholder for the file.

Abstract: Methods, systems, and computer-readable storage media for determining that a first transaction results in a first version of data stored in a page in a database system, the first version being stored in a version space and the data being stored in a table space, in response to the first version, providing a version table for the page, the version table including a set of cells each cell corresponding to a record in the page, setting a version table pointer of the page to point to the version table, and setting a version pointer of a first cell to point to the first version in the version space, the first cell corresponding to a record of the data in the page.

Abstract: An image output management apparatus includes a determination unit and a generating unit. The determination unit compares, with one another, pieces of request information for requesting image output, and thus determines pieces of request information satisfying a predetermined similarity condition. The generating unit generates presentation information as prior information. The presentation information indicates the pieces of request information satisfying the similarity condition. The prior information is presented to a user before execution of image output according to the pieces of request information.

Abstract: A processing system including at least one processor may be maintain an historical graph database storing historical graph state information for a graph including a set of elements, where the historical graph state information includes, for each element, respective element state information and respective state version tracking information for the respective element. The processing system may receive an event indicative of a management action associated with a first element, where the first element may include a new element to be added to the graph or an existing element of the set of elements. The processing system may update, based on the event, the historical graph state information of the historical graph database, where the updating may include providing respective state version tracking information for the first element, and handle, based on the historical graph database, a query to retrieve a set of information of the graph.

Abstract: A method comprises receiving a stream of change log records from a source database system; generating change statistics based on a number of pending changes per table partition according to the change log records; estimating, based on performance statistics, a first amount of time for applying the pending changes to a target database system using an incremental update path; estimating, based on the performance statistics, a second amount of time for applying the pending changes to the target database using a bulk update path; dynamically selecting, based on comparison of the first amount of time with the second amount of time, one of the incremental update path and the bulk update path for applying the pending changes to the target database system; and applying the pending changes to the target database system using the selected update path.

Abstract: A shared log system can provide a key-index structure (main map) that allows clients (users) to access the state of objects stored in the shared log system. The client can define secondary indices on the main map to provide access to the data that are tailored to the client's data needs. Each client can generate their own customized set of secondary indices different from other clients.

Abstract: Methods, systems, and computer-readable media for highly available storage using independent data stores are disclosed. A request to create a data object using an atomic operation is received. A selected data store is determined of a plurality of data stores comprising a first data store and a second data store. The data stores are mutually independent. An identifier assigned to the data object indicates the selected data store. An event associated with creation of the data object is generated. The event is associated with the identifier. The selected data store stores the data object and the event such that the event is consistent with the data object.

Abstract: Apparatuses, methods, systems, and program products are disclosed for displaying edits for a user's portion of a shared document. An apparatus includes a processor and a memory that stores code executable by the processor. The code is executable by the processor to receive a selection of a user who has contributed to a document that is editable by a plurality of users. The code is executable by the processor to determine portions of the selected user's contributions to the document that have been edited by other users of the plurality of users. The code is executable by the processor to visually indicate the edits made to the portions of the selected user's contributions to the document.

Abstract: Described are systems and methods for storing a data object using a hierarchical erasure encoding to store a physical representation of the data object across a plurality of fault domains. A first erasure encoding is applied to the data object to generate a first set of shards of the data object. Individual shards of the set of shards may then be distributed across the fault domains for storage. Within the fault domains a second erasure encoding may be applied to the individual shards to generate a second set of shards. Finally, a manifest may be generate in order to reconstruct the data object from the first set of shards and the second set of shards.

Abstract: Techniques are disclosed relating to concurrently processing transactions. A computer system may maintain a database table having a plurality of versions. Each of the versions may identify a corresponding portion of the database table that transactions associated with that version are permitted to access. The computer system may receive a first request to perform a first transaction to modify a definition of the database table. The computer system may receive a second request to perform a second transaction to modify data stored in the database table. In response to determining that the first and second transactions are associated with different versions of the plurality of versions, the computer system may concurrently process the first and second transactions.

Abstract: This invention discloses a novel system and method for displaying electronic documents on remote devices and enabling collaborative editing where the system upon a request by a user to access a document, automatically determines the latest version of a document that the person had accessed and also whether a newer version had been created. The invention also merges parallel changes that have not been viewed by the user into the comparison result. The invention also includes running a comparison on the two versions and presenting the result to the user.

Abstract: Example embodiments provide methods, mediums, and systems for making and evaluating changes to a model. According to example embodiments, checkpoints may be created as a user changes components in the model. The checkpoints may store changed components in the model that have been changed since a previous checkpoint, and a reference (e.g., a pointer) to the previous checkpoint. A user may freely create new checkpoints, revert to previous checkpoints, and select a checkpointed version of the model to be used as an official working version of the model. Upon activating an existing checkpoint, parametric relationships in the model assembly may be automatically updated in order to make components in the model consistent with each other. Thus, the user can readily change the model and evaluate variations of a design, while at the same time saving storage space by avoiding the need to repeatedly save different versions of the model.

Abstract: Example distributed storage systems, version control managers, and methods provide persistent version control for data transfers between heterogeneous data stores. A first object data store includes a versioned data object with a plurality of sequential versions corresponding to the versioned data object. A version control manager is configured to determine a creation timestamp for each of the plurality of sequential versions and store a persistent version field for each. The persistent version field remains associated with each of the plurality of sequential versions when transferred from the first object data store to a second object data store.

Abstract: Optimized techniques are disclosed for sorting variable-length records using an optimized amount of memory while maintaining good locality of references. The amount of memory required for sorting the variable length records is optimized by reusing some of the memory used for storing the variable length records being sorted. Pairs of input runs storing variable length records may be merged into a merged run that contains the records in a sorted order by incrementally scanning, sorting, and copying the records from the two input runs being merged into memory pages of the merged run. When all the records of a memory page of an input run have been processed or copied to the merged run, that memory page can be emptied and released to a cache of empty memory pages. Memory pages available from the cache of empty memory pages can then be used for generating the merged run.

Abstract: A storage device includes: a plurality of memory devices configured as a virtual device utilizing stateless data protection; and a virtual device layer configured to manage the virtual device to store objects by applying a first data protection to some of the objects and a second data protection to other ones of the objects depending on respective sizes of the objects.

Abstract: One example method includes implementing a function as a service (FaaS) at a datacenter by performing operations including receiving an application program interface (API) gateway call from a client application, wherein the API gateway call is associated with an object PUT request, and automatically triggering, with the API gateway call, performance of an object insertion function. The object insertion function includes retrieving, from backend object storage, a previous version of the object, differentially compressing the object relative to the previous version of the object so as to generate a differential, and storing the differential in the backend object storage.

Abstract: Systems and methods for generating tables using data associated with records. For example, a system may store the data associated with the record in one or more databases. The system may then generate tables associated with fields of the record, where the tables indicate updates and/or changes to the fields. For instance, when changes are made to a field of the record, the system may update the table to indicate the changes, times at which the changes occurred, identifiers of users that made the changes, reasons for the changes, and/or so forth. The system may further update a version of the record when updates and/or changes are made to the fields. Furthermore, the system may update the tables to indicate versions of the record when the updates and/or changes occurred to the fields.

Abstract: Implementations include, during development of a second version within a development environment, tracing activities to determine development tables, the second version including changes that are incompatible with the first version, the development tables including deploy tables, activation tables, and troubleshooting tables, computing, by a configuration generator, an upgrade configuration based on the development tables, the upgrade configuration defining tables to deploy the changes during an upgrade, the tables being computed based on the development tables, during the upgrade: continuing production use of a first version using a first runtime at least partially including a first data schema, and establishing a second runtime at least partially by defining a second data schema within the database system using the upgrade configuration, the second data schema including the tables, and completing the upgrade by switching production use to the second version from the first version.

Abstract: A system and method for determining ancestry in directed acyclic graphs (DAGs). The method includes accessing a first node of a plurality of nodes in a DAG to obtain first change time data and ancestry data, wherein the plurality of nodes includes at least one point of interest, wherein the first change time data indicates a time of a first change to ancestry of the closest point of interest (CPOI); accessing a CPOI of the first node to obtain second change time data, wherein the second change time data indicates a time of a most recent change to ancestry of the CPOI; comparing the first change time data with the second change time data; and determining ancestry of the first node, wherein the ancestry of the first node is determined based on the ancestry data when the first change time data matches the second change time data.

Abstract: According to various example embodiments, a method of providing information by a computing device may include checking an input information set, receiving a first result information set corresponding to the input information set from a first server, receiving a second result information set corresponding to the input information set from a second server, and providing a third result information set including information on or regarding a difference between the first result information set and the second result information set. Various other example embodiments may be possible.

Abstract: This disclosure relates to a method for rendering images. First, a user request is received from a user interface to access an image effect renderer recipe, comprising conditional logic and non-visual image data, from an effect repository. Next, at least one image signal is received. Objects are identified within the image signal(s). The image effect renderer recipe is processed via an effect renderer recipe interpreter to generate image processing steps and image processing prioritizations. The image processing steps are then ordered in accordance with the image processing prioritizations. Next, an image processor applies the image processing steps to the identified objects of the image signal(s) to generate at least one processed image signal. The processed image signal(s) are then displayed on a display device.

Abstract: The subject technology executes a change on an existing micro-partition of a table, the executing of the change comprising generating a new micro-partition that embodies the change and deleting the existing micro-partition. The subject technology receives a request for a delta for the table between a first timestamp and a second timestamp. The subject technology responsively determines the delta based on a table history, the delta including information indicating at least one operation that was performed to at least one row of a set of rows of the table, without including information as to intermediate changes made to at least one row of the set of rows of the table between the first timestamp and the second timestamp, that facilitates a reduction in storage of historical versions of the set of rows of the table.

Abstract: A method for merging transactions for execution by a database management system. The method includes a computer processor receiving a database query that is comprised of a plurality of transactions. The method further includes a computer processor placing each of the plurality of transactions, of the database query, in respective chronological order, in a scheduling queue. The method further includes a computer processor determining that at least a first transaction and a second transaction within the plurality of transactions each contains one or more transaction delineation descriptions. The method further includes computer processor responding to the determination that the first transaction and the second transaction, within the plurality of transactions, each contains one or more transaction delineation descriptions, and merging the first transaction and the second transaction to create a merged transaction combination and merging also includes combining two or more table-scan operations.

Abstract: The present approach relates generally to systems and methods for generating a hierarchical model of a plurality of software development streams, identifying points of interest on the plurality of software development streams having a status indication, and determining descendant development streams corresponding to the points of interest. The present approach also relates to systems and methods for traversing the descendant development streams sequentially in descending order of creation date of the points of interest corresponding to the descendant development streams, determining a software build file status indication for software build files associated with the descendant development streams based at least on the status indication of the points of interest, and evaluating the software build file status indication for the software build files to generate an indication of a first subset of build files having an unfixed status indication and a second subset of build files having a fixed status indication.

Abstract: Embodiments regard maintaining data consistency between transactional and non-transactional data stores. Embodiments may include receiving a request to archive a set of data stored in a first data store, recording a high water mark in the first data store for the set of data, and archiving the set of data. Archiving the set of data may include copying the set of data into a second data store and inserting a high water mark for the set of data in the first data store and the second data store. Embodiments may further include updating a reference high water mark upon successful completion of operations for the archiving of the data, the reference high water mark representing completion of a last successful archive operation, and, upon receiving a query for requested data contained in the first or second data store, determining whether to allow viewing of the requested data based at least in part on a current value of the reference high water mark.

Abstract: Systems, components, devices, and methods for privately editing shared files in a collaborative space are provided. A non-limiting example includes a server computing device for allowing a user to privately edited shared files in a collaborative space. The server computing device includes an interface engine configured to generate a user interface. The user interface includes a listing of a plurality of shared files accessible in the collaborative space and an edit privately control to privately edit an identified shared file of the plurality of shared files. When the edit privately control is actuated, the server computing device generates a personal copy of the identified shared file and updates metadata associated with the identified shared file to indicate that the personal copy has been generated.

Abstract: Example object storage systems, meta object generators, and methods provide versioned meta objects for internal operational data that may be replicated between data object stores. A meta object may be generated that includes meta object data, such as internal operational data. A meta object identifier may be assigned to the meta object. A first version identifier may be associated with the meta object data and a second version identifier may be associated with a marker for the meta object, where the marker prevents exposure as a user data object.

Abstract: Embodiments are disclosed for a multi-tier storage system (MTSS). The techniques include identifying a first data extent stored in a first storage pool of MTSS based on a read-write heat mapping by the MTSS. The first data extent is associated with a mirrored volume. The first data extent is a mirrored copy of a second data extent stored in a second storage pool of the MTSS. The first storage pool is asymmetric to the second storage pool. The techniques also include determining that a second top promotion tier of the second storage pool is faster than a first top promotion tier of the first storage pool. The techniques further include promoting the second data extent to the second top promotion tier based on the determination. Additionally, the techniques include updating an I/O access policy to direct future I/O operations for the mirrored volume to the second data extent.

Abstract: A method for controlling access to a shared filesystem stored in a distributed data storage system is provided. The method can include storing a file comprising a shared filesystem as an inode object and a series of data block objects comprising the shared filesystem. Responding to a request from a client to open the file can include generating, in the shared filesystem, a client object, an open file object, and a client index object. The client object can be linked to the open file object and the client index object. The open file object and the client index object can be further linked to the inode object to indicate the file being accessed by the client. Related systems and articles of manufacture, including computer program products, are also provided.

Abstract: A method is described that includes providing a snapshot counter for a storage system implemented with multiple distributed consistent database instances. The method further includes recognizing the taking of a snapshot of the storage system by incrementing the snapshot counter from a first snapshot counter value to a second snapshot counter value. The method further includes, in response to a first change for one of the distributed consistent databases subsequent to the taking of the snapshot, performing the following: saving state information of the distributed consistent database as the state information existed prior to the change and associating the first snapshot counter value to the state information. Associating the second snapshot counter's value with the distributed consistent database having the first change. Another method for the taking of a snapshot of a distributed consistent database is also described.

Abstract: Embodiments of the present invention provide a system for executing a smart tool for enterprise-wide software integration and deployment. The system is typically configured for executing instruction in one or more modules of the smart tool to identify and gather one or more application prerequisites required for application development of an application, receiving a set of development codes from one or more users and storing the set of development codes in a first environment system, creating a package comprising at least one version of the set of development codes, deploying a packaged development code to a second environment system, performing a plurality of test on the packaged development code, in response to passing the plurality of tests, deploying the packaged development code to a real-time environment system.

Abstract: When a user sees a content item presented by a social networking system, the user may select an option to save the content item. The saved content item may be reinserted in a newsfeed presented to the user, integrated into collections, archived, used for notifications to the user, or otherwise subsequently presented to the user. A plug-in may be used to save content items accessed through websites external to the social networking system. As privacy settings associated with a saved content item are modified, the modified privacy settings are applied to the saved content item, which may prevent the user saving the content item from subsequently viewing the saved content item.

Abstract: Technologies described herein can be used to support modification to data by a client computing device without a concurrency check. An update to a data document can be received from a client computing device. Contents of the update can be analyzed to determine whether a concurrency check is required before applying the update to the data document. In at least some embodiments, at least part of the contents of the data document can be organized in such a way that multiple, independent modifications can be made to the contents of the data document without concurrency checks. A server computer can be configured to identify updates to these contents of the data document, and to apply the updates to the data document without performing concurrency checks. In at least some embodiments, a list of concurrency-safe data document properties can be accessed when determining whether to omit the concurrency check.

Abstract: The present disclosure relates to system(s) and method(s) for real-time synchronization of source repositories is illustrated. The system is configured to receive a set of documents corresponding to history of changes and changed data associated with a source repository since last replication of the source repository over an intermediate storage. Further, the system may convert the set of documents in an intermediate format to generate a set of intermediate documents. Further, the system may comprise steps to identify one or more target repositories from the set of repositories based on analysis of the set of intermediate documents and current status associated with each repository from set of repositories. Further, the system transmit the set of intermediate documents to the one or more target repositories.

Abstract: In some embodiments, a client generates an operation modifying a local copy of a content item on a user account at a content management system and records an intent to commit the operation to a journal of revisions at the content management system. Based on the operation, the client sends to the content management system a first request to commit the operation at the journal, the first request including a cursor identifying a current position of the client in the journal. The client sends, to the content management system, a second request for a status of the commit and, based on the second request, determines whether the commit of the operation to the journal has succeeded. Based on whether the commit of the operation to the journal has succeeded, the client determines whether to update one or more tree data structures on the client and clear the intent to commit.