公开(公告)号：US20170075922A1

公开(公告)日：2017-03-16

申请号：US15097090

申请日：2016-04-12

Applicant: salesforce.com, inc.

Inventor： Adam Torman ,  Ivan Daya Weiss ,  Aakash Pradeep ,  Abhishek Bangalore Sreenivasa ,  Alex Warshavsky ,  Soumen Bandyopadhyay ,  Choapet Oravivattanakul ,  Samarpan Jain

IPC: G06F17/30

CPC classification number: G06F16/1805 ,  G06F16/164 ,  G06F16/2358

Abstract: Disclosed are some examples of database systems, methods, and computer program products for processing log files. In some implementations, a server of a database system accesses a metadata file indicating algorithms that can be applied to data of log files. The server generates customer-facing log files using the log file and metadata file. The customer-facing log files include new data derived from using the algorithms and the data of the log files.

Abstract translation: 公开了用于处理日志文件的数据库系统，方法和计算机程序产品的一些示例。 在一些实现中，数据库系统的服务器访问指示可应用于日志文件的数据的算法的元数据文件。 服务器使用日志文件和元数据文件生成面向客户的日志文件。 面向客户的日志文件包括从使用算法和日志文件的数据导出的新数据。

公开(公告)号：US10592474B2

公开(公告)日：2020-03-17

申请号：US15097090

申请日：2016-04-12

Applicant: salesforce.com, inc.

Inventor： Adam Torman ,  Ivan Daya Weiss ,  Aakash Pradeep ,  Abhishek Bangalore Sreenivasa ,  Alex Warshavsky ,  Soumen Bandyopadhyay ,  Choapet Oravivattanakul ,  Samarpan Jain

IPC: G06F16/18 ,  G06F16/23 ,  G06F16/16

Abstract: Disclosed are some examples of database systems, methods, and computer program products for processing log files. In some implementations, a server of a database system accesses a metadata file indicating algorithms that can be applied to data of log files. The server generates customer-facing log files using the log file and metadata file. The customer-facing log files include new data derived from using the algorithms and the data of the log files.

公开(公告)号：US10678757B2

公开(公告)日：2020-06-09

申请号：US15093920

申请日：2016-04-08

Applicant: salesforce.com, inc.

Inventor： Aakash Pradeep ,  Abhishek Bangalore Sreenivasa ,  Adam Torman ,  Alex Warshavsky ,  Ivan Daya Weiss ,  Samarpan Jain ,  Somesh Sasalatti ,  Soumen Bandyopadhyay ,  Choapet Oravivattanakul

IPC: G06F16/182 ,  G06F16/27 ,  G06F16/28 ,  G06F16/13 ,  G06F16/25

Abstract: A database system may determine that a database is unavailable to generate an identifier for an event or that events may not be written to the database. As a result, the database system may write the event to a low-latency, supplementary file system. The database system may determine that the database is available at a later time, and read the event from the supplementary file system, store the event in a memory component, and then delete the event from the supplementary file system. The database system may then access the database to generate an identifier for the event, write the event to the database, and then delete the event from the memory component.

公开(公告)号：US20180025113A1

公开(公告)日：2018-01-25

申请号：US15218468

申请日：2016-07-25

Applicant: salesforce.com, Inc.

Inventor： Adam Torman ,  Abhishek Bangalore Sreenivasa ,  Aakash Pradeep ,  Ivan Daya Weiss ,  Soumen Bandyopadhyay ,  Alex Warshavsky ,  Samarpan Jain

IPC: G06F19/00 ,  G06F17/30

CPC classification number: G16H10/60 ,  G06F16/211 ,  G06F16/2471

Abstract: Disclosed are some examples of database systems, methods, and computer program products for run-time schema for event records. In some implementations, event records satisfying a query can be identified. Attribute-value pairs of data of those identified event records can be stored in an unstructured data field of an event record.

公开(公告)号：US20170293632A1

公开(公告)日：2017-10-12

申请号：US15093920

申请日：2016-04-08

Applicant: salesforce.com, inc.

Inventor： Aakash Pradeep ,  Abhishek Bangalore Sreenivasa ,  Adam Torman ,  Alex Warshavsky ,  Ivan Daya Weiss ,  Samarpan Jain ,  Somesh Sasalatti ,  Soumen Bandyopadhyay ,  Choapet Oravivattanakul

IPC: G06F17/30

Abstract: A database system may determine that a database is unavailable to generate an identifier for an event or that events may not be written to the database. As a result, the database system may write the event to a low-latency, supplementary file system. The database system may determine that the database is available at a later time, and read the event from the supplementary file system, store the event in a memory component, and then delete the event from the supplementary file system. The database system may then access the database to generate an identifier for the event, write the event to the database, and then delete the event from the memory component.