Abstract: Systems and methods for managing membership in a private data exchange are provided herein. In one embodiment, the method comprises adding a new member to a data exchange, wherein the data exchange comprises a set of listings, each listing comprising data from one or more datasets stored on a cloud computing service. An account type is assigned to the new member, the account type comprising at least one of a consumer type, provider type, or exchange administrator type. Each of the account types associated with one or more rights with respect to the set of listings, such that the new member has a set of rights based on the account type. The set of rights of the new member are then modified with respect to one or more listings from the set of listings based on a set of visibility and access rules for each of the set of listings.

Abstract: Providing access to metrics on a private data exchange is described. An example computer-implemented method can include providing a data exchange by a cloud computing service on behalf of an entity. The data exchange may comprise several data listings provided by one or more data providers. The data listings reference one or more data sets stored in a data storage platform associated with the cloud computing service. The method may also include granting access the data listings, gathering consumer information based queries provided to data associated with the data listings, generating a new share comprising the consumer information, and granting access of the new share to the data provider that provided the data listing.

Abstract: Providing a private data exchange is described. An example computer-implemented method can include providing a data exchange by a cloud computing service on behalf of an entity. The data exchange may comprise several data listings provided by one or more data providers. The data listings reference one or more data sets stored in a data storage platform associated with the cloud computing service. The method may also include designating a data exchange administrator account of the data exchange. The data exchange administrator account may be associated with the entity and may be capable of: granting and denying requests from data consumers to access the data exchange; and granting and denying requests from data providers to publish data listings on the data exchange.

Abstract: A data warehouse storing databases for a plurality of users, including service providers hosting data for other users of the data warehouse may implement a data exchange. The data warehouse to verify identity of users and execute instructions with respect to databases of the data warehouse.

Abstract: Systems, methods, and devices for generating a secure join of database data are disclosed. A method includes determining data stored in a first account to be compared with data stored in a second account. The method includes determining a function for generating a secure join key, wherein the secure join key includes a hashed string that hashes one or more of a data entry of the first account and a data entry of the second account. The method includes providing the secure join key to the first account and/or the second account.

Abstract: A data warehouse storing databases for a plurality of users, including service providers hosting data for other users of the data warehouse may implement a data exchange. A provider of data creates a listing in the exchange including metadata. A consumer browses the metadata and select a listing to add to consumed shares of the consumer. Browsing may be filtered to implement a private exchange. Adding of data may be limited by access controls requiring verification of the consumer's identity. The added data may be filtered to include only data that relates to the consumer. Sharing may be bi-directional such that a request to add a listing for first data of a provider may also reference second data of the consumer such that the first data is added to the consumed shares of the consumer and the second data is added to the consumed shares of the provider.

Abstract: A data warehouse storing databases for a plurality of users, including service providers hosting data for other users of the data warehouse may implement a data exchange. The data warehouse to verify identity of users and execute instructions with respect to databases of the data warehouse.

Abstract: Systems, methods, and devices for generating a secure join of database data are disclosed. A method includes determining data stored in a first account to be compared with data stored in a second account. The method includes determining a function for generating a secure join key, wherein the secure join key includes a hashed string that hashes one or more of a data entry of the first account and a data entry of the second account. The method includes providing the secure join key to the first account and/or the second account.

Abstract: A data warehouse storing databases for a plurality of users, including service providers hosting data for other users of the data warehouse may implement a data exchange. The data warehouse to verify identity of users and execute instructions with respect to databases of the data warehouse.

Abstract: Systems and methods for managing membership in a private data exchange are provided herein. In one embodiment, the method comprises adding a new member to a data exchange, wherein the data exchange comprises a set of listings, each listing comprising data from one or more datasets stored on a cloud computing service. An account type is assigned to the new member, the account type comprising at least one of a consumer type, provider type, or exchange administrator type. Each of the account types associated with one or more rights with respect to the set of listings, such that the new member has a set of rights based on the account type. The set of rights of the new member are then modified with respect to one or more listings from the set of listings based on a set of visibility and access rules for each of the set of listings.

Abstract: Systems, methods, and devices for generating a secure join of database data are disclosed. A method includes determining data stored in a first account to be compared with data stored in a second account. The method includes determining a function for generating a secure join key, wherein the secure join key includes a hashed string that hashes one or more of a data entry of the first account and a data entry of the second account. The method includes providing the secure join key to the first account and/or the second account.

Abstract: Systems, methods, and devices for generating a secure join of database data are disclosed. A method includes determining data stored in a first account to be compared with data stored in a second account. The method includes determining a function for generating a secure join key, wherein the secure join key includes a hashed string that hashes one or more of a data entry of the first account and a data entry of the second account. The method includes providing the secure join key to the first account and/or the second account.

Abstract: Systems, methods, and devices for generating a secure join of database data are disclosed. A method includes determining data stored in a first account to be compared with data stored in a second account. The method includes determining a function for generating a secure join key, wherein the secure join key includes a hashed string that hashes one or more of a data entry of the first account and a data entry of the second account. The method includes providing the secure join key to the first account and/or the second account.

Abstract: A data warehouse storing databases for a plurality of users, including service providers hosting data for other users of the data warehouse may implement a data exchange. The data warehouse to verify identity of users and execute instructions with respect to databases of the data warehouse.

Abstract: In certain embodiments, queries may be facilitated via request-prediction-based temporary storage of query results. In some embodiments, a request for query results may be predicted, and, in response, a subset of results may be obtained. The subset of results may be a portion of a set of results that would have been obtained to respond to the request had the request been obtained from a client device. The subset of results may be caused to be stored in temporary data storage, and no storage of other subsets of the set of results in the temporary data storage occurs from the request prediction. The request may be obtained from the client device subsequent to the storage. Based on the obtained request, the subset of results may be obtained from the temporary data storage, and the other subsets of the set of results may be obtained via at least another data source.

Abstract: In some embodiments, data related to calculating a set of values may be obtained. The set of values may be approximated based on a subset of the related data. The approximated values may be stored at a first data storage and a second data storage that corresponds to a landing zone (via which a client device obtains at least some of the approximated values). The approximated values stored at the first data storage may be continuously updated based on further subsets of the related data such that the approximated values stored at the first data storage is updated at least a first number of times within a first time period. The approximated values stored at the second data storage may be continuously updated such that the approximated values stored at the second data storage is updated less than the first number of times within the first time period.

Abstract: In some embodiments, data related to calculating a set of values may be obtained. The set of values may be approximated based on a subset of the related data. The approximated values may be stored at a first data storage and a second data storage that corresponds to a landing zone (via which a client device obtains at least some of the approximated values). The approximated values stored at the first data storage may be continuously updated based on further subsets of the related data such that the approximated values stored at the first data storage is updated at least a first number of times within a first time period. The approximated values stored at the second data storage may be continuously updated such that the approximated values stored at the second data storage is updated less than the first number of times within the first time period.

Abstract: In certain embodiments, queries may be facilitated via request-prediction-based temporary storage of query results. In some embodiments, a request for query results may be predicted. Responsive to the request prediction, queries for data related to calculating a set of values may be performed. A subset of the related data may be obtained based on the performed queries. The performance of the queries may be caused to stop prior to obtaining other subsets of the related data. The set of values may be predicted based on the subset of the related data. The predicted set of values may be caused to be stored in temporary data storage. The request may be obtained from a client device subsequent to the storage of the predicted set of values. The predicted set of values may be obtained from the temporary data storage based on the request from the client device.

Abstract: In certain embodiments, queries may be facilitated via request-prediction-based temporary storage of query results. In some embodiments, a request for query results may be predicted. Queries for at least some of the query results may be predicted responsive to the request prediction, where the performed queries are a subset of a set of queries that would have been performed to respond to the request had the request been obtained from a client device, and no performance of one or more other queries of the set of queries occurs from the request prediction. Results may be obtained based on the performed queries and caused to be stored in temporary data storage. The request may be obtained from the client device subsequent to the storage of the results. The results may be obtained from the temporary data storage based on the request from the client device.

Abstract: In certain implementations, data presentation delay resulting from network-related delays may be reduced. As an example, delay of a presentation related to a requested value may be significantly reduced even if network-related delays for certain data relevant to the value occur (e.g., delays in retrieving certain subsets of data related to calculating the value). In some implementations, a set of queries for data related to a value may be performed, where the set of queries includes (i) a first subset of queries and (ii) one or more other subsets of queries. The value may be predicted based on subsets of data for calculating the value (which are derived from the first query subset). Such prediction of the value may be performed (and provided for presentation) before other subsets of data for calculating the value are received (which are derived from the other query subsets), thereby reducing data presentation delay.