Abstract: Techniques for automated query retry in a database platform include decoding, by at least one hardware processor, a query directed to database data. The query is received by a first management node from a client account of a database system. The method further includes configuring an execution of the query by a first computing node associated with the first management node. The method includes detecting the execution of the query results in a failed execution. The query is transferred from the first management node to a second management node based on the failed execution. The second management node is configured to process tasks that are internal to the database system. A retry execution of the query by a second computing node is configured. The second computing node is associated with the second management node. A cause of the failed execution is determined based on a result of the retry execution.

Abstract: Systems and methods for generating object references with selectable scopes are provided. The systems and methods perform operations including calling, by a first entity, a reference generator function using one or more arguments associated with a database object that the first entity is authorized to access according to a first set of access privileges, the one or more arguments comprising a scope definition that defines persistence of a reference. The operations include obtaining, from the reference generator function, a reference to the database object, the reference persisting according to the scope definition. The operations include passing the reference to a second entity to enable the second entity to perform one or more database operations on the database object according to a second set of access privileges derived from the first set of access privileges.

Abstract: The cloud data platform receives a first query directed towards a shared dataset, the first query identifying a first operation. The platform accesses a first set of data from the shared dataset to perform the first operation, the first set of data including data accessed from a first table of the shared dataset. The cloud data platform determines that an aggregation constraint policy is attached to the first table, the aggregation constraint policy restricts output of data values stored in the first table and enforces the aggregation constraint policy on the first query based on a context of the first query. The cloud data platform generates an output to the first query based on the first set of data and the first operation, based on enforcing the aggregation constraint policy on the first query.

Abstract: A mounting system for telecommunications equipment comprises: a mast for supporting telecommunications equipment; a first mounting bracket, affixable to supporting infrastructure; a pivot, secured to the first mounting bracket, into which a first end of the mast is mounted, the pivot enabling the mast to be pivoted between a first, raised position and a second, lowered position; and a second mounting bracket, affixable to the supporting infrastructure, for selectively supporting the mast while in the first position.

Abstract: A database system facilitates secure data sharing by implementing projection constraints within a query processing framework. Upon receiving a query directed to a shared dataset, the system, utilizing hardware processors, identifies a subset of data within the dataset that is subject to a projection constraint policy. The applicability of the projection constraint is determined based on the context of the query, which is derived from a data sharing agreement. The system processes the query by selectively restricting the projection of data values from constrained columns, while allowing specific operations to be performed on the data. The output generated in response to the query is compliant with the projection constraint policy, providing derived data based on the allowed operations without revealing the actual data values. This ensures the confidentiality of sensitive information while enabling collaborative data analysis and sharing among various users of the database system.

Abstract: A system for enforcing projection constraints on data values stored in specified variables of a shared dataset of a cloud data platform. A request is received from a first account of the cloud data platform that identifies a first operation to be performed on the shared dataset. A first set of data, including data accessed from a first variable, is accessed from the shared dataset to use in performing the first operation. A projection constraint policy attached to the first variable of the shared dataset is determined, and the projection constraint policy is further determined to be enforced based on the request. Based on the first set of data and the first operation, an output to the first request is generated.

Abstract: Automated query retry includes selecting a first node of a plurality of nodes of an execution platform in response to a query. The first node is configured with a first version of a database platform. A first execution of the query is performed using the first version of the database platform at the first node. The method further includes detecting the first execution results in a failed execution. A second execution of the query is scheduled. The second execution uses at least one of the first version of the database platform or a second version of the database platform configured at a second node of the plurality of nodes. The second version is released after the first version. A cause of the failed execution of the query at the first node is determined based at least in part on a result of the second execution of the query.

Abstract: Systems and methods for generating transient object references are provided. The systems and methods perform operations including establishing a session between a first entity and a second entity. The operations include identifying an object that the first entity is authorized to access according to a first set of access privileges. The operations include generating a reference associated with the object. The operations include temporarily authorizing the second entity to access the object using the reference according to a second set of access privileges, the second set of access privileges being derived from the first set of access privileges.

Abstract: A constraint system enforces projection constraints on data values stored in specified columns of a shared dataset when queries are received by a database system. A projection constraint identifies that the data in a column may be restricted from being projected (e.g., presented, read, outputted) in an output to a received query, while allowing specified operations to be performed on the data and a corresponding output to be provided. For example, the projection constraint may indicate a context for a query that triggers the constraint, such as based on the user that submitted the query. Enforcing projection constraints on queries received at the database system allows for data to be shared and used anonymously by entities to perform various operations without the need to tokenize the data.

Abstract: A system for enforcing projection constraints on data values stored in specified variables of a shared dataset of a cloud data platform. A request is received from a first account of the cloud data platform that identifies a first operation to be performed on the shared dataset. A first set of data, including data accessed from a first variable, is accessed from the shared dataset to use in performing the first operation. A projection constraint policy attached to the first variable of the shared dataset is determined, and the projection constraint policy is further determined to be enforced based on the request. Based on the first set of data and the first operation, an output to the first request is generated.

Abstract: A constraint system enforces projection constraints on data values stored in specified columns of a shared dataset when queries are received by a database system. A projection constraint identifies that the data in a column may be restricted from being projected (e.g., presented, read, outputted) in an output to a received query, while allowing specified operations to be performed on the data and a corresponding output to be provided. For example, the projection constraint may indicate a context for a query that triggers the constraint, such as based on the user that submitted the query. Enforcing projection constraints on queries received at the database system allows for data to be shared and used anonymously by entities to perform various operations without the need to tokenize the data.

Abstract: Disclosed herein are systems and methods for performing a geospatial-function join using an implied interval join. In an embodiment, a database platform receives a query that includes a geospatial-function join, which applies a geospatial-function predicate to a first geography data object of a first relation and a second geography data object of a second relation. The database platform processes the first and second relations through an interval join that applies an interval-join predicate that is implied by the geospatial-function predicate. The database platform obtains query results at least in part by implementing a filter that applies the geospatial-function predicate to an output of the interval join, and outputs the query results.

Abstract: Disclosed herein are embodiments of systems and methods for query-attempt processing in a database environment. In an embodiment, a database platform receives a query, and operates a first query manager of the database platform to manage a first attempt to execute the query. Based on determining that the attempt to execute the query was unsuccessful, the database platform identifies a second query manager of the database platform as implementing a same version of the database platform as the first query manager, and operates the second query manager to manage a first retry attempt to execute the query.

Abstract: Techniques for automated query retry in a database platform include decoding, by at least one hardware processor, a query directed to database data. The query is received by a first management node from a client account of a database system. The method further includes configuring an execution of the query by a first computing node associated with the first management node. The method includes detecting the execution of the query results in a failed execution. The query is transferred from the first management node to a second management node based on the failed execution. The second management node is configured to process tasks that are internal to the database system. A retry execution of the query by a second computing node is configured. The second computing node is associated with the second management node. A cause of the failed execution is determined based on a result of the retry execution.

Abstract: Automated query retry includes selecting a first node of a plurality of nodes of an execution platform in response to a query. The first node is configured with a first version of a database platform. A first execution of the query is performed using the first version of the database platform at the first node. The method further includes detecting the first execution results in a failed execution. A second execution of the query is scheduled. The second execution uses at least one of the first version of the database platform or a second version of the database platform configured at a second node of the plurality of nodes. The second version is released after the first version. A cause of the failed execution of the query at the first node is determined based at least in part on a result of the second execution of the query.

Abstract: Techniques for automated query retry in a database platform include decoding, by at least one hardware processor, a query directed to database data from a client account of a database platform. The method further includes decoding, by the at least one hardware processor, an indication that execution of the query on at least one computing node of the database platform results in a failed execution. The method further includes configuring a processing loop with continuous retry executions of the query on the at least one computing node based on the indication. The method further includes exiting the processing loop based on detecting a retry execution of the continuous retry executions results in at least one successful execution of the query. The method includes logging each attempt to execute the query during the continuous retry executions in a query status log until the at least one successful execution of the query.

Abstract: Techniques for automated query retry in a database platform include assigning by at least one hardware processor a first execution of a query directed to database data to a first execution node of a plurality of execution nodes of an execution platform. The first execution node uses a first set of configurations during the first execution. The techniques further include determining that the first execution of the query by the first execution node results in a failed execution. The query is transferred to a second execution node of the plurality of execution nodes. A second execution of the query at the second execution node is caused. The second execution node uses a second set of configurations during the second execution. A cause of the failed execution at the first execution node is determined based on a result of the second execution of the query at the second execution node.

Abstract: In an embodiment, a database platform receives query instructions for a query on a database, where the query instructions include instructions for a geospatial-function join that includes a geospatial-function predicate. The database platform generates a query-execution plan based on the query instructions, including replacing the geospatial-function join with one or more interval joins that each include one or more predicates implied by the geospatial-function predicate. The database platform inserts, into the query-execution plan above the one or more interval joins, a filter operator that applies the geospatial-function predicate. The database platform obtains results of the query at least in part by executing the query-execution plan, and returns the query results in response to the query.

Abstract: Techniques for automated query retry in a database platform include decoding, by at least one hardware processor, a query directed to database data from a client account of a database platform. The method further includes decoding, by the at least one hardware processor, an indication that execution of the query on at least one computing node of the database platform results in a failed execution. The method further includes configuring a processing loop with continuous retry executions of the query on the at least one computing node based on the indication. The method further includes exiting the processing loop based on detecting a retry execution of the continuous retry executions results in at least one successful execution of the query. The method includes logging each attempt to execute the query during the continuous retry executions in a query status log until the at least one successful execution of the query.

Abstract: Techniques for automated query retry in a database platform include assigning by at least one hardware processor a first execution of a query directed to database data to a first execution node of a plurality of execution nodes of an execution platform. The first execution node uses a first set of configurations during the first execution. The techniques further include determining that the first execution of the query by the first execution node results in a failed execution. The query is transferred to a second execution node of the plurality of execution nodes. A second execution of the query at the second execution node is caused. The second execution node uses a second set of configurations during the second execution. A cause of the failed execution at the first execution node is determined based on a result of the second execution of the query at the second execution node.