Dynamic chronometry data orientation

Patent metadata

Field	Value
Publication number	US-11797568-B2
Application number	US-202218067452-A
Country	US
Kind code	B2
Filing date	Dec 16, 2022
Priority date	Mar 30, 2020
Publication date	Oct 24, 2023
Grant date	Oct 24, 2023

Abstract

Operating a low-latency database analysis system using domain-specific chronometry may include obtaining chronometry configuration data including chronometric instance data describing an instance of a chronometric unit of a domain-specific chronometry dataset that describes an era, such that the chronometry configuration data includes respective chronometric instance data describing each instance of the first chronometric unit of the domain-specific chronometry dataset for the era of the domain-specific chronometry dataset, generating, in the low-latency database analysis system, a domain-specific chronometry dataset in accordance with the chronometry configuration data, such that the domain-specific chronometry dataset describes a chronometric unit such that a temporal location expressed with reference to the chronometric unit and indicative of an epoch value differs from a temporal location indicative of the epoch value and expressed in accordance with a canonical chronometry, and storing the domain-specific chronometry dataset in the low-latency database analysis system.

First claim

What is claimed is:

1. An apparatus for use in a database analysis system, the apparatus comprising:
a memory storing computer executable instructions for dynamic chronometry data orientation; and
a processor configured to execute the instructions to:
obtain chronometry configuration data;
generate, in the database analysis system, a domain-specific chronometry dataset in accordance with the chronometry configuration data, such that the domain-specific chronometry dataset describes chronometric units including a chronometric unit such that a temporal location expressed with reference to the chronometric unit and indicative of an epoch value differs from a temporal location indicative of the epoch value and expressed in accordance with a canonical chronometry; and
store the domain-specific chronometry dataset in the database analysis system.

2. The apparatus of claim 1 , wherein to store the domain-specific chronometry dataset the processor executes the instructions to:
generate a table in a distributed in-memory database of the database analysis system; and
store the domain-specific chronometry dataset in the table.

3. The apparatus of claim 1 , wherein to store the domain-specific chronometry dataset the processor executes the instructions to:
generate an object that represents the domain-specific chronometry dataset; and
store the object in a distributed in-memory ontology of the database analysis system as ontological data that represents the domain-specific chronometry dataset.

4. The apparatus of claim 3 , wherein to store the domain-specific chronometry dataset the processor executes the instructions to:
obtain a descriptor value for the chronometric unit from the domain-specific chronometry dataset, wherein the chronometric unit is associated with a chronometric unit type; and
generate a chronometry index for indexing descriptor values for chronometric units from the domain-specific chronometry dataset associated with the chronometric unit type, wherein to generate the chronometry index the processor executes the instructions to include the descriptor value for the chronometric unit in the chronometry index.

5. The apparatus of claim 3 , wherein to store the domain-specific chronometry dataset the processor executes the instructions to:
generate a finite state machine based on the ontological data representing the domain-specific chronometry dataset.

6. The apparatus of claim 1 , wherein the canonical chronometry describes a Gregorian calendar.

7. The apparatus of claim 1 , wherein to obtain the chronometry configuration data the processor executes the instructions to:
obtain data expressing a usage intent with respect to the database analysis system, the data expressing the usage intent including chronometry boundary configuration data.

8. The apparatus of claim 7 , wherein the chronometry boundary configuration data includes:
first chronometric location data representing a minimum temporal location for the domain-specific chronometry dataset, the first chronometric location data expressed in the chronometry boundary configuration data in accordance with the canonical chronometry;
second chronometric location data representing a maximum temporal location for the domain-specific chronometry dataset, the second chronometric location data expressed in the chronometry boundary configuration data in accordance with the canonical chronometry, such that the domain-specific chronometry dataset describes an era corresponding to a duration from the minimum temporal location to the maximum temporal location;
a chronometry type identifier;
first chronometric relationship data indicating, for a first chronometric unit of the domain-specific chronometry dataset, wherein the first chronometric unit corresponds with an ordered sequence of second chronometric units of the domain-specific chronometry dataset, a sequentially earliest second chronometric unit expressed in the chronometry boundary configuration data with reference to a month-ordinal of the canonical chronometry;
second chronometric relationship data indicating, for a third chronometric unit of the domain-specific chronometry dataset, wherein the third chronometric unit corresponds with an ordered sequence of fourth chronometric units of the domain-specific chronometry dataset, a sequentially earliest fourth chronometric unit expressed in the chronometry boundary configuration data with reference to a day-ordinal of the canonical chronometry;
third chronometric relationship data indicating, for the third chronometric unit, a fourth chronometric unit from the ordered sequence of fourth chronometric units, represented with reference to a day-ordinal of the canonical chronometry, such that an instance of a chronometric unit of the domain-specific chronometry dataset that includes an instance of the fourth chronometric unit from the ordered sequence of fourth chronometric units includes an instance of the third chronometric unit that includes the instance of the fourth chronometric unit; and
descriptor data for the first chronometric unit of the domain-specific chronometry dataset.

9. The apparatus of claim 8 , wherein to obtain the chronometry configuration data the processor executes the instructions to:
obtain the chronometry boundary configuration data; and
automatically generate primary chronometry configuration data in response to the chronometry boundary configuration data.

10. The apparatus of claim 9 , wherein:
the chronometry boundary configuration data includes output location data indicating a computer storage location for outputting the primary chronometry configuration data generated based on the chronometry boundary configuration data; and
to obtain the chronometry configuration data the processor executes the instructions to output the primary chronometry configuration data in accordance with the output location data.

11. The apparatus of claim 1 , wherein the chronometry configuration data includes chronometric instance data describing an instance of a first chronometric unit of the domain-specific chronometry dataset.

12. The apparatus of claim 11 , wherein the domain-specific chronometry dataset describes an era corresponding to a duration from a minimum chronometric location of the domain-specific chronometry dataset to a maximum chronometric location of the domain-specific chronometry dataset, such that the chronometry configuration data includes respective chronometric instance data describing each instance of the first chronometric unit of the domain-specific chronometry dataset for the era of the domain-specific chronometry dataset.

13. The apparatus of claim 12 , wherein the chronometric instance data includes:
a first temporal location expressed in accordance with the canonical chronometry;
a descriptor for the instance of the first chronometric unit with respect to an ordered sequence of first chronometric units within an instance of a second chronometric unit of the domain-specific chronometry dataset;
a descriptor for an instance of a third chronometric unit, wherein the instance of the third chronometric unit includes the instance of the first chronometric unit;
a descriptor for an instance of a fourth chronometric unit, wherein the instance of the fourth chronometric unit includes the instance of the first chronometric unit;
a descriptor for an instance of a fifth chronometric unit, wherein the instance of the fifth chronometric unit includes the instance of the first chronometric unit;
an ordinal value for the instance of the first chronometric unit with respect to the ordered sequence of first chronometric units within the instance of the

Assignees

• Thoughtspot Inc

Inventors

• Mahale Tushar
• Singaram Siva
• Sharma Vishwas
• Donjerkovic Donko
• Gill Simranjyot Singh
• Bansal Archit
• Kothari Rakesh
• Gupta Sanchit

Classifications

• G06F16/27 Primary

  Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor · CPC title

• G06F16/2477 Primary

  Temporal data queries · CPC title

• G06F16/21

  Design, administration or maintenance of databases · CPC title