-
公开(公告)号: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
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.
-
公开(公告)号:US10332129B2
公开(公告)日:2019-06-25
申请号:US14529674
申请日:2014-10-31
Applicant: salesforce.com, inc.
Inventor: Adam Torman , Alex Warshavsky , Derrill Dabkoski , Thomas William D'Silva , Aakash Pradeep , Robert Woollen , Samarpan Jain , Soumen Bandyopadhyay
Abstract: Disclosed are methods, apparatus, systems, and computer program products for provisioning log file data. To provision the log file data, a server can parse through log files by identifying particular log entries and data fields. Customer-facing log files can be generated based on the identified log entries and data fields. A customer-facing log file has log file data specific to a particular customer, which can be a tenant of a multi-tenant database system. A security mechanism can be configured to prevent one tenant from accessing the customer-facing log file of another tenant of the multi-tenant database system.
-
公开(公告)号: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.
-
公开(公告)号:US10178156B2
公开(公告)日:2019-01-08
申请号:US14688917
申请日:2015-04-16
Applicant: salesforce.com, inc.
Inventor: Aakash Pradeep , Adam Torman , Alex Warshavsky , Samarpan Jain , Soumen Bandyopadhyay , Thomas William D'Silva
IPC: G06F15/177 , H04L29/08 , G06F17/30 , G06F11/00
Abstract: A database system captures custom information of a header section associated with a logged interaction of a user. The database system may receive a hypertext transfer protocol (http) message including the header section and determine whether the header section includes a predetermined data pattern associated with the custom information added by a second application that is different than a first application which initiated the http message. The database system may extract the custom information from the header section in response to determining that the header section includes the predetermined data pattern. The custom information and event data extracted from the logged interaction of the user may be stored on the database system as a storage element.
-
公开(公告)号:US20180095790A1
公开(公告)日:2018-04-05
申请号:US15281559
申请日:2016-09-30
Applicant: salesforce.com, inc.
Inventor: Aakash Pradeep , Abhishek Sreenivasa , Adam Torman , Alex Warshavsky , Samarpan Jain , Soumen Bandyopadhyay
CPC classification number: G06F9/4887 , G06F17/30115
Abstract: Disclosed are some examples of systems, methods, apparatus and computer program products for scheduling jobs to process log files. In some implementations, a scheduler can be configured to identify a final state of a previously scheduled first job as a failure in execution by one or more processors. For instance, the first job may have been defined to process a first input log file saved to a database during a first timeframe of a sequence of timeframes of a designated interval. The scheduler can detect a second input log file saved to the database. The scheduler can then define a second job to process the first input log file and the second input log file and schedule the second job in association with a second timeframe of the sequence.
-
公开(公告)号: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
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.
-
公开(公告)号:US09417840B2
公开(公告)日:2016-08-16
申请号:US14705750
申请日:2015-05-06
Applicant: salesforce.com, inc.
Inventor: Aakash Pradeep , Adam Torman , Alex Warshavsky , Samarpan Jain , Soumen Bandyopadhyay , Thomas William D'Silva , Abhishek Bangalore Sreenivasa
CPC classification number: G06F12/0804 , G06F5/14 , G06F9/542 , G06F9/544 , G06F2205/126 , G06F2212/1041 , G06F2212/281 , G06F2212/311 , H04L67/28
Abstract: A capture service running on an application server receives events from a client application running on an application server to be stored in a data store and stores the events in an in-memory bounded buffer on the application server, the in-memory bounded buffer comprising a plurality of single-threaded segments, the capture service to write events to each segment in parallel. The in-memory bounded buffer provides a notification to a buffer flush regulator when a number of events stored in the in-memory bounded buffer reaches a predefined limit. The in-memory bounded buffer receive a request to flush the events in the in-memory bounded buffer from a consumer executor service. The consumer executor service consumes the events in the in-memory bounded buffer using a dynamically sized thread pool of consumer threads to read the segments of the bounded buffer in parallel, wherein consuming the events comprises writing the events directly to the data store.
Abstract translation: 在应用服务器上运行的捕获服务从在应用服务器上运行的客户端应用程序接收要存储在数据存储中的事件,并将事件存储在应用服务器上的内存有界缓冲区中,内存有界缓冲区包括 多个单线程段,捕获服务将事件并行写入每个段。 当存储在内存有界缓冲区中的多个事件达到预定义的限制时,内存有界缓冲区向缓冲区清除调节器提供通知。 内存有界缓冲区接收到从消费者执行器服务刷新内存有界缓冲区中的事件的请求。 消费者执行器服务使用动态大小的消费者线程的线程池来消耗内存有界缓冲器中的事件,以并行读取有界缓冲器的片段,其中消耗事件包括将事件直接写入数据存储器。
-
公开(公告)号:US20160041976A1
公开(公告)日:2016-02-11
申请号:US14717848
申请日:2015-05-20
Applicant: salesforce.com, inc.
Inventor: Aakash Pradeep , Adam Torman , Alex Warshavsky , Derrill Dabkoski , Samarpan Jain , Soumen Bandyopadhyay , Thomas William D'Silva
IPC: G06F17/30
CPC classification number: G06F16/23 , G06F16/2358 , G06Q30/0201
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 log file having a release version. The log file includes data entries identifying system events corresponding to user activity. The server generates or updates, based on the release version of the log file, a metadata file indicating approved entry types and approved data. The server also generates or updates, based on the log file and the metadata file, customer-facing log files. Each customer-facing log file is associated with a corresponding customer entity capable of being serviced by the database system. Each customer-facing log file includes a subset of the entries and a subset of the data items of at least one of the entries.
Abstract translation: 公开了用于处理日志文件的数据库系统,方法和计算机程序产品的一些示例。 在一些实现中,数据库系统的服务器访问具有发布版本的日志文件。 日志文件包括标识与用户活动相对应的系统事件的数据条目。 服务器根据日志文件的发行版本生成或更新指示已批准的条目类型和已批准数据的元数据文件。 服务器还会根据日志文件和元数据文件生成或更新面向客户的日志文件。 每个面向客户的日志文件与能够由数据库系统服务的相应的客户实体相关联。 每个面向客户的日志文件包括条目的子集和至少一个条目的数据项的子集。
-
公开(公告)号:US11599526B2
公开(公告)日:2023-03-07
申请号:US16671151
申请日:2019-10-31
Applicant: salesforce.com, inc.
Inventor: Sivananda Reddy Thummala Abbigari , Lawrence Eugenio McAlpin , Vikram Kommaraju , John Arlan Brock , Soumen Bandyopadhyay
IPC: G06F16/23
Abstract: Implementations are described for selectively publishing an event responsive to an operation on a database in a transaction. Publishing the event is delayed or not delayed respectively, responsive to determining that a value of an attribute for the event indicates that publishing the event is to be delayed, or not to be delayed, until the transaction is rolled back or committed. If publishing the event is delayed, the event is published if the transaction is committed and discarded if the transaction is rolled back. If publishing the event is not delayed, the event is published. Optionally, if the event is published, the event is published in a database or a datastore respectively, responsive to determining whether another value of another attribute for the event indicates that the event is to be published in a database or a datastore.
-
-
-
-
-
-
-
-
-