减少 Databricks 中的事务冲突——Asana 的基本原理和应用.pdf

1、Forward-looking StatementThis presentation has been prepared for informational purposes only.The information set forth herein does not purport to be complete or contain all relevant information.Statements contained herein are made as of the date of this presentation unless stated otherwise.This pres

2、entation and the accompanying oral commentary may contain forward-looking statements.In some cases,forward-looking statements can be identified by terms such as“may”,“will”,“should”,“expects”,“plans”,“anticipates”,“could”,“intends”,“projects”,“believes”,“estimates”,“predicts”,or“continue”,or the neg

3、ative of these words or other similar terms or expressions that concern Databricks expectations,strategy,plans,or intentions.Forward-looking statements are based on information available at the time those statements are made and are inherently subject to risks and uncertainties that could cause actu

4、al results to differ materially from those expressed in or suggested by the forward-looking statements.Forward-looking statements should not be read as a guarantee of future performance or outcomes.Except as required by law,Databricks does not undertake any obligation to publicly update or revise an

5、y forward-looking statement,whether as a result of new information,future developments or otherwise.2Reducing Transaction Conflicts in DatabricksFundamentals andApplications at AsanaDima KamalovDATE TBDWhats the Problem We Ran Into?Updating 1 table based on 700 upstream tablesWhen upstream changes,p

6、rocess kicks off to update downstreamMERGE INTO all_objects USING individual_object_tableUPDATE SET update_time=all_objects.update_timeWHEN NOT MATCHED INSERT*Many concurrency conflicts:(4How do transactions in Databricks workWhat Are Transactionsand Concurrency?TransactionPerform this set of action