►
From YouTube: Delta Hack: Committers AMA and Happy Hour
Description
Join us for a casual Ask Me Anything and happy hour with some of the Delta Lake committers. Let's talk about the future of Delta Lake, fun problems we're going to solve, or cool uses of Delta Lake!
B
Boom
live
streaming
is
enabled
that
means
we
are
live
with
a
very
serious,
very
serious
session,
with
we've
got
ryan
and
denny.
I'm
waiting
to
see
if
qp
will
join
us
for
a
committer's,
ama
and
happy
hour.
I
was
just
lamenting
to
denny
that
I
don't
have
any
beer,
so
my
happy
hour
is
a
little
less
happy,
but
it
will.
I
have
I
have
a
water
here,
so
it
will
be
hydrating.
B
So
we'll
see
how
it
goes.
You
know
denny,
I
I
said
I
called
it
a
committer's
happy
hour,
but
I
don't.
Actually.
I
don't
know
if
I've
ever
seen.
You
actually
commit
to.
A
C
B
C
So
basically,
like
I
basic
star
work
with
like
michael
who
is
the
likely
author
of
the
data
lake,
which
basically
ended
up
at
the
beginning.
So
I
made
like
a
lot
of
commits
to
the
toyota
lake
like
in
the
past
several
years
and
in
addition,
I'm
also
like
a
spark
update
bar
committee,
which
also
contributes
like
hundreds
of
commits
to
our
budget
spark
in
the
past
yeah
and
then
now
we
are,
I'm
basically
focused
on
like
teletubbing,
which
is
a
new
open
source
project.
B
I
I
wanna
I
wanna
pull
up,
I'm
gonna
pull
up
two
two
graphs,
okay,
because
so
so
let
me
share
my
my
window
here
to
to
give
anybody
anybody
watching
an
idea.
So
here's
ryan-
this
is
the
delta
main
repository
for
delta.
B
There's
barack
is
number
one
and
then
ryan
here
at
number
two
in
terms
of
committers
getting
lots
of
lots
of
commits
in
lately.
Unfortunately,
I
can't
go
back
more
than
a
couple
of
months
here,
but
then
delta
sharing.
C
B
So
let
me
let
me
ask
you
ryan,
with
delta
sharing,
I
mean
a
lot
of
it.
A
lot
of
it
was
coming
together,
sort
of
in
the
in
the
final
final
weeks
before
data
nai
summit,
where,
where
y'all
announced
it
yeah
were
there,
were
there
any
features
or
any
things
that
you
you
had
to
like
cut
to
make
the
deadline
that
you
you're
you're,
looking
forward
to
bringing
in
now
that
data
and
ai
summit
is
over.
C
Yeah
so
basically
yeah,
because
we
actually
just
had
like
only
several
weeks
before
they
don't
have
time.
So,
basically,
we
are
just.
We
were
basically
focusing
on
like
the
major
features
like
python
connector
and
also
like
a
spark
connector
that
you
can
read
from
this
like
a
data
sharing
server
and
then
the
open
source
data,
australian
server.
C
Kindly
right
now
is
kind
of
a
reference
implementation
which
supports
the
major
features,
but
regarding
like
a
security
or
other
like
optimizations,
we
actually
haven't
spent
quite
a
lot
on
these
parts
and
yeah
for
the
open
source
client.
There
are
also
like
a
lot
of
peace.
We
can
improve
in
the
future
like
a
currently
we
are.
C
A
A
Sorry,
you
know
fire
drill
right
now,
just
right.
The
second.
B
B
I
mean
denny,
you're,
you're,
more
than
welcome
to
jump
in,
but
ryan
is
the
the
main
committer
to
delta.
Sharing,
I
feel
like
is
the
start
of
the
show
here
at
the
moment,.
B
I'm
I'm
interested
ryan
to
know
like
where
you
imagine
this
going
like
delta
delta
itself.
Has
all
of
these
features
like
time
travel.
There's
right,
I
mean
there's
writer
support
as
well,
and
delta.
Sharing
right
now
is
very
reader
oriented,
but
it's
sort
of
like
a
single
snapshot
in
time
of
of
a
data
set,
how
much
of
like
what
we
see
in
delta,
as
sort
of
like
support
or
or
compatibility
do,
you
think,
is
going
to
come
over
into
delta
sharing.
C
So
you
so
maybe
we
can
use
some
example
like
time
travel
like
you
mentioned,
let's,
let's
definitely
we
can
support
this
easily
in
this
internationally.
We
can
extend
a
kind
of
protocol
like
you
can
specify
a
table
version
in
a
request,
and
then
we
can
support
this
and
and
another,
like
other
features
like
kindly.
C
B
B
C
C
B
Yeah,
one
of
the
things
that
qp
and
christian
and
and
misha
and
neville
from
the
the
delta
rs
community
have
spent
a
lot
of
time.
Thinking
about
are
concurrency
challenges
because
you
know
having
multiple
writers
on
top
of
something
like
s3.
B
B
I
was
telling
I
was
telling
qp
this
morning
that
or
christian
this
morning
I
really
would
like
to
to
stop
thinking
or
having
to
think
about
coordination
and
concurrency
problems
with
delta
for
a
little
while.
C
Yeah,
maybe
eight
others
can
like
support
like
put
a
represent
feature
on
s3.
Then
it's
much
easier
to
do.
A
C
B
So
qp
we
were
just
talking
about
about
delta
sharing
and
that
sort
of
led
us
into
some
of
the
concurrency
fund
that
we've
had
in
delta
rs.
Since
you
joined,
I
want
to
make
use
of
your
time.
Let
me
ask
you
a
question
you
know
for,
for
anybody
that
that
doesn't
know
who
qp
is
qp
is
the
original
creator
and
committer
on
delta
rs,
which
he
created
last
year.
I'm
kind
of
curious
where
you
think
delta
rs
goes
over
the
next.
Let's
say
six
to
12
months.
D
So
obviously
the
most
important
thing
is
to
get
into
production
a
script,
so
we
have
a
pretty
cool
project
called
delta
interest.
I
think
that
that's
the
first
goal
that
I
would
like
to
see
happens
and
then,
after
that,
I
think
there
are
a
couple
interesting
use
use
cases
that
could
come
out
of
it.
For
example,
we
have
been
talking
about
well,
we've
been
we'll
say,
tighter
I've
been
talking
about
using
lambda
to
do
some
cool
delta
liquidated
hacking.
D
One
of
those
relates
to
using
lambda
to
automatically
archive
status
in
data
table
for
cost
savings
and
auditing
purposes.
So
I
think
there
are
a
couple
interesting
applications
that
could
come
out
of
it
with
lambda
and
rust.
B
It's
I
I
feel
like
sometimes
with
these
these
ideas
that
I'll
have,
I
feel,
like
I'm
a
toddler
who's
like.
Why
can't
we
do
this,
but
what
about
that?
What
if
we
did
this,
would
that
work
and
then
kp's
like
well
yeah,
maybe-
and
I
feel,
like
I'm
spending,
far
less
intellectual
time.
Thinking
about
how
possible
it
is,
I'm
just
like
what,
if
we
did
it
like
this
yep.
D
And
another
pretty.
D
Another
pretty
cool
application.
I
think
that
could
come
out
of
that
is
so
we
we.
We
can
now
easily
create
language
bindings
for
almost
any
language.
We
want
with
with
very
little
effort
right.
So
one
thing
that
in
python
so
far
it's
been
pretty
good
because
we
have
a
pretty.
D
We
have
pandas
pandas
library,
which
is
really
useful
that
we,
we
can
do
all
kinds
of
advanced
query
without
a
table
already
in
python,
but
that
is
not
the
case
for
other
languages
like
ruby,
for
example,
and
we've
been
thinking
of
exposing
rust
data
fusion
project
to
for
these
other
languages
so
that
they
can
also
query
data
tables
with
really
high
performance,
query
engine.
D
B
You've
been
you've
been
working
on
on
data
fusion
a
bit
lately.
I
think
it
it
may
be
a
lesser
known
project.
Could
you
maybe
introduce
it
yeah
so
and
he's
googling
it
right
now.
So.
D
Efficient,
it's
basically
a
query
execution
engine
and
an
analytical
query
execution
engine
based
on
arrow,
the
arrow
in
memory
format
and
it's
sort
of
similar
to
pandas
for
python.
But
it's
for
rust
or
or
in
rust,
and
it
implements
the
same
set
of
data
frame
api
and
then,
on
top
of
that
it
provides
a
sql
query
interface
for
you
to
query
any
kind
of
tabular
data
or
that
that
in
any
language
well
in
rust.
But
I
think
the
cool
thing
about
that
is
because
it's
in
rust.
D
It
does
not,
there
is
a
project,
but
that's
still
like
in
early
development
phase,
but
right
now
it's
only
local.
B
C
A
Yeah,
that
was
that
was
actually
announced
during
during
the
sparky
day,
two
keynotes,
that
that
were
merging
that
quality
into
it.
Actually
so.
B
A
A
Okay,
fair
enough.
Well,
then,
for
me
it's
we've
got
a
lot
of
people
who
are
asking
or
interested
in
various
connectors,
like
you
know,
flink
presto,
whatever
else,
and
so
we've
actually
even
started
various
channels
on
the
delta
lake
slack
channel
to
go
ahead
and
talk
about
that,
and
in
fact,
that's
probably
what
I
would
love
to
have
more
involvement
within.
You
know
the
flint
community,
the
presto
community
kafka
communities,
all
these
other
communities
that
really
want
to
it's,
not
just
about
them.
Telling
us
hey,
we'd,
love
to
see
it.
A
It's
like
no
we'd
love
to
go
ahead
and
actually
sit
down
and
engage
more,
and
so
it's
starting
to
happen
like
I
said
so,
we've
started
placing
some
channels
in
delta
lake
specifically
for
that,
but
love
to
see
you
know,
since
we've
got
a
nice,
you
know
promotion
vehicle
here
right
now,
right,
love
to
actually
have
more
people
involved,
we'll
be
starting
once
every
two
week
meetings
I
believe
in
I
want
to
say
early
july.
That's
when
we're
starting
those
meetings.
Yeah,
I
think
the
flink
one
we've
already.
A
A
B
D
We
have
that
in
all
parts
in
memory,
but
we
don't
have
api
to
expose
that.
Yet
there
is
a
github
issue
on
that.
It's
actually
really
good
for
first-time
contributors.
It's
really
easy
to
add
that
api.
We
just
have
to
expose
the
what
we
have
in
memory
through
api.
B
All
right,
I'm
gonna,
have
to
go
dig
up
that
issue
now,
one
of
our
good
first
issues,
one
of
the
things
I'll
I'll
just
call
out
here.
There's
a
lot
of
good.
First
issues
linked
for
delta,
rs
ryan
have
y'all
done
that
for
the
delta
repo
as
well
gone
and
tagged
issues
that
are
like
beginner
or
you
know,
introductory
things.
C
Yeah
we
have
some
special
tags
actually
right
now,
we
are
have
like
on-call
duty
for
in
for
os
and
delta
elect,
which
will
have
people
start
looking
at
the
monetary
report
and
then
try
to
like
bring
like
a
great
like
issues
or
pull
requests,
and
then
we
basically
will
discuss
it
live
every
day
to
see
what
we
can
do
to
improve
the
community.
C
For
example,
if
we
find
something
like
simple
issue,
I
will
just
probably
just
add
some
text
there
and
if
something,
it's
pretty
hard
that
we
probably,
but
if
someone
would
like
to
contribute,
we
would
like
to
discuss
our
flag
about
what
we
should
do
for
like
some
like
larger
features,
yeah
at
least
answer
your
question.
B
There's
when
I
look
at
when
I
look
at
the
delta
repository,
there
are
136
issues
there
and
then
in
delta
rs.
We
we
recently
crossed
40.
and
so
between
the
two
of
them.
I
think
we
have
lots
of
opportunity
for
contribution.
A
B
A
B
Week,
let
me
go
back
to
my
my
list
of
questions
again.
If
you've
got
any
questions,
you're
welcome
to
throw
them
in
the
youtube
chat
and
we'll
see
what
we
can
do
to
to
answer
them,
maybe
denny's
something
that
you
might
be
willing
to
share,
or
maybe
not
we'll
see,
but
I'm
curious,
let's
say
over
the
past
year
or
so
like.
What's
the
coolest
use
of
delta
lake,
that
you've
seen
that
you
are
able
to
talk
about
publicly.
A
I
think
the
coolest
use
in
some
ways
is
actually
almost
pretty
boring
right.
So
the
reason
I
say
that
is
because
a
lot
of
this
has
to
do
with
the
the
I
can't
mention
the
company,
but
I
can
definitely
mention
the
use
case,
and
so
the
use
case
actually
is
very
much
dpr
and
in
fact,
if
you,
if
you
do
a
bunch
of
youtube
stuff,
you
probably
will
find
the
company.
What
was
that
acronym?
Oh
sorry,
gdpr
compliance.
B
A
Yeah,
so
compliance
use
cases
where,
because
they
needed
the
ability
to
delete,
merge,
update
things
of
that
nature
and
so,
for
example,
the
way
they
did.
A
Compliance
actually
wasn't
just
deleting
the
information
but
was
actually
updating
the
information
first,
because
that
way
they
can
ensure
that
their
downstream
systems
could
also
comply
properly
with
ccp
and
gtbr,
and
then
finally,
they
would
delete
afterwards.
But
the
context
was
that
first
was
an
update,
and
that
would
signal-
and
that
would
trigger
a
bunch
of
downstream
systems
and
in
the
process
of
doing
that,
because
people
are
saying.
Oh,
how
can
you
do
update
end
up
involving
a
bunch
of
data
warehousing
techniques,
so
in
other
words,
your
surrogate
keys,
slowly
changing
dimensions?
A
You
know
type
2,
slowly,
changing
dimensions.
A
lot
of
the
traditional
data.
Warehousing
type
techniques
are
actually
basically
applied
with
the
delta
link,
and
so
that
part
I
find
sort
of
cool
just
because
I'm
an
old
data
warehousing
hound
and
the
idea
that
my
old
data
warehousing
knowledge
actually
is
applicable
to
the
new
world.
Today
it's
actually
pretty
sweet,
so.
B
A
B
C
Yeah
one
thing
like,
for
example,
in
the
past
we
saw
like
some
customers
that
have
like
very
like
big
tables
and
then
before
delta.
Actually,
a
query
is
very
slow
because
when
you
are
creating
this
metadata,
if
you
need
to
like
read
from
high
mega
store-
and
unfortunately
it's
like
from
like
a
database-
is
pretty
slow
and
then
after
we
like
this,
let's
switch
it
to
delta
lag.
C
So
and
if
you
have
enough
results,
let's
say
you
can
like
start
like
a
100
node
to
process
like
a
tablet,
have
billions
of
files
left
yeah,
and
this
is
impossible
when
before
delta,
which
you,
if
you
have
one.
D
D
C
C
D
So
I
I
I've
kept
going
back
to
kafka
down
the
stream
because
big
interest,
because
I
think
we
are
also
sort
of
stress
testing
the
transaction
action
in
delta
particle,
where
I
think
we
might
be
the
first
application
that
try
to
use
try
to
create
one
transaction
application
per
per
copy
partition
to
keep
track
of
the
ingestion
progress
within
the
other
table
itself.
So
we'll
see
how
it
goes.
Hopefully,
it'll
go
well,
but
so
far
we're
pretty
happy
with
the
design.
B
Let
me
go
to
a
question
that
came
in
through
chat.
Maybe
denny,
could
you
you
mentioned
connectors?
Could
you
maybe
just
introduce
what
connectors
is
and
why
that
repository
exists
and
what's
supposed
to
go
there.
A
Oh
absolutely
thanks
for
the
question
actually,
so
the
point
of
the
connectors
repository
is
the
ability
for
systems
different
systems
like
to
be
able
to
interact
with
delta
lake
right.
We
want
to
make
sure
that
it
it's
easy
for
when
the
project
started.
A
Like
you
know,
we
definitely
started
with
spark
right,
and
so,
let's
not
bother
the
pretense
that
we
haven't
done
that
right,
but
the
reason
we
wanted
the
connectors
is
because
interacting
with
delta
lake
and
utilizing
the
advantages
of
asset
transactions
for
your
data,
lake
with
delta
lake
is
not
specifically
a
spark
project
right.
It's.
It
can
be
anything
right.
It
doesn't
matter
what
language
you're
using
doesn't
matter.
A
A
No
problem,
that's
me
it's
on
me,
so
I
own
this
okay
power,
bi
connectors,
for
example,.
A
There
are
pull
requests
for
the
presto
connector
right
now
that
is
currently
being
worked
on
the
obviously
the
stuff
that
ryan
has
created.
The
hive
connectors
jvm
standalone,
the
delta
native
standalone
reader,
things
of
that
nature.
So
we'd
like
this
is
just
one
repo,
though
right.
We
have
actually
have
many
connectors
that
can
talk
to
delta
and
both
from
right
now,
mostly
primarily
on
read,
but
we're
actually
working
closely
with
the
community,
including
teams
like
yourselves
for
also
writing
capacity.
A
B
I
think
the
once
one
as
qp
was
alluding
to
once
kafka
delta
ingest
is,
is
live
and
in
production
I'm
I'm
hoping
we
don't
have
to
do
anything,
but
I
can
imagine
us
having
some
feedback
on
on
how
the
the
texan
actions
or
transaction
actions
are
are
handled
in
in
the
delta
protocol.
B
Let
me
go
back
to
my
list
of
questions.
Thank
you
all
for
for
those
answers,
ryan.
Let
me
come
back
to
you
with
with
this
question.
We've
got,
I
think,
right
now,
from
what
I've
seen.
I
think
reader
and
writer
versions
are
just
at
one
yep.
What
would
be,
let's
say,
we're
evolving
the
protocol.
B
What
do
you
think
would
be
significant
enough
to
require
us
to
to
actually
make
use
of
that
min
reader
or
min
writer
version
in
the
delta
protocol.
C
In
this
case,
we
like
to
bump
at
least
write
a
version,
because
the
other
version
will
be
able
to
understand
how
to
generate
these
values,
just
based
on
this
expression
for
the
later
version
part
which
we
haven't
done
any
change
in
the
past,
but
in
future
we
may
like
bomb
police,
for
example
like
if
we
would
like
to
support
like
a
hidden
columns
that,
like
we
would
like
to
allow
the
user
space
file.
Okay,
I
don't
want
to
show
this
column
in
a
table.
I
need
just
some
metadata
something
like
this.
C
B
How
do
you
I
want?
I
I'd
like
to
hear
from
you
ryan
and
qp
on
this.
We
now
have
three
implementations
of
of
the
delta
lake
protocol,
one
in
rust,
one
in
that
standalone
java
project
and
then
in
the
the
spark
reference
implementation.
C
What
do
you
think
right
yeah?
So,
basically
we,
if
you
like
to
change
the
protocol
and
first
I
think
it's
better
to
like
discuss
in
a
delta
core
project,
which
you
may
just
open
a
pool
request,
a
change
to
the
protocol,
and
then
we
can
discuss
later
what
you
like
to
change,
and
how
can
we
coordinate
this
with
other
projects.
D
I
was
going
to
ask
the
same
question,
but
I'm
good
to
know.
I
thought
the
process
was
was
to
send
an
email
to
the
dev
mailing
list,
but
I
think
just
to
summarize
the
process
should
be
starting
with
the
pr
right
with
that
proposed
change
to
the
protocol.
C
Yeah,
you
can
also
send
an
email
if
let's
have
simple,
but
if
you
have
like
a
very
complete
case,
maybe
also
just
try
to
like
modify
this
protocol
talk.
So
we
can
have
a
better
idea
of
what
you
are
going
to
change.
D
B
Six
to
12
months,
because
we
have,
we
have
a
lot
of
versions
of
things
now
yeah
there
there's
the
spark
implementation
version,
there's
the
the
standalone
reader
and
then
the
delta
rs
has
its
own
versioning
and
we
don't
have
any
shared
understanding.
Right
now
of
you
know.
Delta
lake
is
1.0.
We
said
that
at
data
in
nai
summit.
C
C
Yeah,
I
think
we
can
also
like
have
a
document
or
a
document
page
to
describe
obvious
capability
like
issues
or
at
least
what
do
we
support
yeah
in
each
version.
A
Yeah,
perfect,
no
good
call
up
by
ryan
for
starters,
but
thanks
the
the
context
I
was
saying
is
that
we're
gonna
we're
taking
the
inspiration
from
the
delta
rest,
api,
twice
monthly
meetings
or
once
a
meeting
once
every
two
weeks,
and
so
same
idea
that
we
want
to
start
that
process
for
the
delta
core,
where
we
can
actually
have
more
open
discussions
about
the
protocol.
A
So,
in
addition
to
the
document,
I
feel
that
that
that's
a
good
way
for
us
to
make
sure
everybody's
on
the
same
page
that
we
actually
just
just
have
more
discussions
on
this,
because
there's
also
different
interpretations
of
what
the
protocol
is
doing.
Right
we've
been
talking
to
plenty
of
just
like
you
guys
right.
We've
been
talking
to
plenty
of
other
partners
about
how
they
want
to
use
delta,
and
you
know
what
ultimately
happens
like
there
was
a
different,
even
though
we're
all
reading
the
same
boards.
It
was
a
different
based
on
the
context.
A
B
Having
our,
I
would
say,
regular
meetings
of
of
the
implementers
certainly
would
go
a
long
way
to
making
sure
we
don't
screw
anything
up
right
now,
and
I
I
don't
know
if
qp
you
feel
that
there's
any
different
or
anything
different
here,
but
from
delta
rs,
I
kind
of
feel
like
we
just
are-
are
sort
of
chasing
behind
the
spark
implementation.
B
D
D
B
C
C
B
Almost
we're
delta
0.99
compatible,
not
quite
not
quite
there,
so
just
to
be
respectful
of
of
ryan,
denny
and
qp's
time.
I
could
talk
all
day,
but
let's
give
it
a
a
a
couple
more
minutes.
If
you've
got
any
questions,
please
dump
them
in
the
in
the
youtube
chat.
If
you've
got
a
question,
if
it's,
this
is
no
longer
live
and
you're
watching
this
through
through
youtube,
you
can
go
to
delta.io
and
scroll
to
the
bottom.
There's
the
the
link
to
the
slack
workspace.
B
You
can
join
the
delta
lake
oss
channel
there
or
the
delta
rs
channel,
or
a
myriad
of
other
connectors
channels
that
denny
denny
was
suggesting
earlier.
If
you've
got
further
questions
about
those
tools,
I
keep
coughing.
Excuse
me
danny.
Take
the
wheel.
A
A
A
Fair
enough,
fair
enough,
so
stay
hydrated
tyler.
If
you're
going
to
be
doing
this
you've
got
to
stay
hydrated.
That's
why
I
have
coffee.
B
Maybe
I'll
I'll
ask
this
of
you
qp.
Are
you
hacking
on
anything
interesting
for
delta
hack.
D
So
I'm
planning
to
so
previously
tobacco.
On
this,
we
we
have
we're
working
on
this
multi
writer
for
s3
support,
right,
which
you
all
were
talking
about
about
lack
of
access
to
atomic
rename
industry.
So
we
have
a
design
that
we
sort
of
partially
improved
with
tla
plus
and
during
that
process
I
found
a
lot
of
problem.
It's
actually
not
a
really
easy
to
think
easy
thing
to
use.
D
So
I'm
planning
to
use
that
with
delta
rs
the
nice
thing
about
statewide
is
it
also
lets
you
specify
the
spec
with
your
within
your
implementation,
so
it
makes
sure
that
it
makes
sure
that
the
spec
is
always
up
to
date
with
the
implementation,
and
I
think
that
that's
really
that's
something.
That's
it's
not
possible
to
do
in
tla
plus,
so
I'm
pretty
excited
to
learn
more
about
the
project
and
see
if
we
can
adopt
it
for
data
rs.
B
What
tla
plus
does
and
what
states
right
does
that's,
not
formal
verification
right.
What's.
D
So
it's
I'm
pretty
sure,
it's
not
because
that
that
would
be
too
much
thing
to
verify,
but
I
guess
verification
of
the
delta
right
itself.
The
writing,
to
tell
the
table
that
the
whole
optimistic
concurrency
control
that
can
be
formally
verified
as
well.
D
Mean
so
it's
more
about
formally
writing
out
the
the
the
design
for
a
data
table
so
that
we
we
can
automatically
catch
all
the
edge
cases
without
writing
unit
tests,
it's
more,
like
writing,
mathematical
proof
for
the
design,
so
that
we
have
a
proof,
a
system
to
check
the
proof
to
make
sure
that
the
proof
is
correct.
C
Yeah,
that's
a
good
question.
Actually
we
don't
have
such
check.
It's
kind
of
we
are,
but
every
time
when
we
try
to
make
changes
to
this
like
transaction
conflict
detection,
we
need
to
go
through
many
senior
engineers
to
review
what
you
would
like
to
change,
because
it
is
the
core
part
of
the
correctness
of
the
table.
D
D
Well,
I
started
the
work
that
without
knowing
much
much
about
the
other
past,
so
knowing
what
would
have
happened,
I
thought
we
wouldn't
have
done.
B
It
so,
let's
hope,
what's
it
called
state
stage,
right,
state
right:
okay,
ryan,
how
about
you
anything
cool,
you're,
hacking
on
coming
up.
C
Soon,
actually,
finally,
I
kind
of
working
on
like
delta,
sharing
server
in
databricks
yeah.
We
have
like
open
source
server,
but
in
order
to
like
make
this
working
and
database,
there
are
a
lot
of
like
work.
I
need
to
do
yeah
because
we
have
like
a
different
like
environment.
You
know
like
prototype,
so
we
need
to
it's
kind
of
probably
I
we
need.
I
don't
really
write
a
lot
of
code.
You
know
infrastructure.
B
And
I
think
the
the
the
lambdas
that
qp
pointed
out
earlier.
That's
that's
my
answer
to
this
question.
B
I've
gotta
put
my
money
where
my
mouth
is
on.
Those
writing.
Lambdas
is
so
fun
and
rest.
I
don't
know
they're
so
simple,
all
right,
I
should
I
should
go
ahead
and
wrap
this
up
so
that
we
can
all
get
back
to
our
respective
day
jobs
or
hacking,
or
what
have
you
ryan?
Thank
you.
So
much
for
your
time.
Qp
denny.
Also
thank
you
so
much
for
your
time.
B
If
you've
got
again,
if
you've
got
further
questions
about
delta
lake
or
where
the
project
is
or
where
it's
going
definitely
join
us
in
our
slack
workspace
or
the
delta
users.
Google
group,
both
of
those
are
linked
from
delta.io
and
yeah.
I
guess
come
join
us
delta,
lake's,
a
fun
project
to
work
on,
and
thank
you
all
for
joining
me
I'll,
see
you
all
later.