MENU
In Avro, adding a field to a record without default is a __ schema evolution
Suggested Answer: A
Get Premium CCDAK Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
Since Confluent 5.4.0, Avro 1.9.1 is used. Since default value was added to enum complex type , the schema resolution changed from:
(<1.9.1) if both are enums:** if the writer's symbol is not present in the reader's enum, then an error is signalled. **(>=1.9.1) if both are enums:
if the writer's symbol is not present in the reader's enum and the reader has a default value, then that value is used, otherwise an error is signalled.
36 comments · newest first
AV
Avery
11 months ago
I thought it was full evolution, but now I'm not so sure.
TR
Truman
11 months ago
Nope, it's definitely forward if you add a field!
CH
Cherry
11 months ago
Wait, isn't it considered breaking?
CA
Carolann
11 months ago
Totally agree, adding without a default breaks compatibility!
RO
Rory
11 months ago
It's a backward schema evolution.
TA
Tatum
12 months ago
I’m confused about this one. I thought it was full evolution, but now I’m leaning towards breaking since it affects compatibility.
ED
Edelmira
12 months ago
I feel like this might be a backward schema evolution since older versions wouldn't know how to handle the new field.
CO
Cordell
12 months ago
I remember practicing a question about schema evolution, and I think adding a field is forward compatibility if it has a default value.
JE
Jess
1 year ago
I think adding a field without a default is considered a breaking change, but I'm not entirely sure.
JO
Josphine
1 year ago
I'm not totally confident, but I think the answer is A. Forward schema evolution. The key is that the new schema is compatible with the old one, so it's a non-breaking change.
SH
Shad
1 year ago
Okay, I've got this. Adding a field without a default is a forward schema evolution, because it allows the new schema to be read by older readers that don't have that field.
RI
Rikki
1 year ago
I'm pretty sure this is a forward schema evolution, since adding a field without a default value is considered a non-breaking change in Avro.
AJ
Aja
1 year ago
Hmm, I'm a bit confused on this one. I know schema evolution is important in Avro, but I can't remember the exact terminology for adding a field without a default. I'll have to think this through carefully.
LA
Lacresha
1 year ago
This seems like a pretty straightforward question. The key is ensuring the database dumps complete before the SnapMirror update, so I'd say OnCommand Workflow Automation is the tool that can help automate that process.
NI
Nina
1 year ago
Adding a field without a default? Sounds like a great way to 'Avro-id' compatibility issues. *ba dum tss*
EL
Ellsworth
1 year ago
Wait, you mean Avro has schemas? I thought it was just a fancy way to say 'Avocado'! *scratches head*
TE
Tesha
1 year ago
D all the way, baby! Breaking changes are my middle name. *flexes biceps*
AB
Abel
1 year ago
D) breaking
CA
Catina
1 year ago
C) full
PE
Pearlene
1 year ago
B) backward
AM
Amie
1 year ago
A) forward
DE
Devorah
1 year ago
Easy peasy, it's C. Full schema evolution, right? Who needs defaults anyway, am I right? *winks*
LE
Leota
1 year ago
Exactly, defaults are overrated. *winks*
TI
Tina
1 year ago
I agree, who needs defaults anyway?
SA
Sabrina
1 year ago
Yes, you're right! It's C. Full schema evolution.
LA
Lashawna
1 year ago
Hmm, I'm not sure about this one. Might be B or D. Gotta double-check the Avro docs on schema evolution.
JA
Jacquelyne
1 year ago
Let's check the Avro docs to be sure.
JU
Judy
1 year ago
I believe it's D) breaking.
KE
Kelvin
1 year ago
I think it's B) backward.
WE
Wei
1 year ago
I think the answer is D. Adding a field without a default is definitely a breaking change in Avro schema evolution.
ED
Edward
1 year ago
I'm not sure, but I think it's either A) forward or C) full.
ES
Esteban
1 year ago
I agree with Shad, adding a field without default is a forward schema evolution.
SH
Shad
1 year ago
I think the answer is A) forward.
HU
Hubert
2 years ago
That makes sense. I agree with you.
DA
Dahlia
2 years ago
I believe the answer is D) breaking because adding a field without default can break compatibility with existing data.
HU
Hubert
2 years ago
What do you think the answer is for this question?