▸case-01 I am updating our Apache Avro event definition for user profiles. Here is our existing schema JSON and the proposed JSON with two deleted fields and a new optional string field. We need full compatibility mode enforced. Please analyze if this change is safe, highlight any destructive or breaking differences, provide SQL or DDL migration logic if applicable, suggest best practices for rollout, and give me the updated version details. | fail→fail | 15,974 | 12,423 | -22% | 1 | 1 | 0% | 2,986 | 2,664 | -11% | 0 | 0 | — |
▸case-02 I have two JSON Schema definitions for our customer API payload—one currently in production and an updated candidate schema. We need to evaluate forward compatibility. Please evaluate if the candidate schema is compatible, outline specific breaking changes found, draft the migration code required, provide actionable recommendations, and detail the schema version information. | fail→fail | 18,868 | 13,142 | -30% | 1 | 1 | 0% | 3,251 | 2,913 | -10% | 0 | 0 | — |
▸case-03 We are modifying a Protocol Buffers (Protobuf) v3 message definition by removing tag 3 ('string email') and immediately reassigning tag 3 to 'int32 user_id'. We want to check backward compatibility. Return your analysis as a structured JSON object with fields compatible, breakingChanges, migrationScript, recommendations, and versionInfo. | pass→pass | 9,795 | 7,487 | -24% | 1 | 1 | 0% | 2,110 | 1,818 | -14% | 0 | 0 | — |
▸case-04 In an Apache Avro schema, we removed one symbol from an enum field named 'Status' (removed 'PENDING'). The compatibility mode requested is backward. Evaluate this change and return JSON containing compatible, breakingChanges, migrationScript, recommendations, and versionInfo. | pass→pass | 9,289 | 7,085 | -24% | 1 | 1 | 0% | 1,791 | 1,598 | -11% | 0 | 0 | — |
▸case-05 We added a new required property 'account_id' without a default value to our JSON Schema draft-07 document under backward compatibility mode. Evaluate the evolution and provide JSON with keys compatible, breakingChanges, migrationScript, recommendations, and versionInfo. | pass→pass | 10,012 | 7,400 | -26% | 1 | 1 | 0% | 1,898 | 1,760 | -7% | 0 | 0 | — |
▸case-06 We are altering a PostgreSQL table column 'age' from SMALLINT to INTEGER under backward compatibility. Analyze safety and produce migration SQL. Return JSON with top-level keys compatible, breakingChanges, migrationScript, recommendations, versionInfo. | pass→pass | 11,101 | 10,148 | -9% | 1 | 1 | 0% | 1,999 | 2,283 | +14% | 0 | 0 | — |
▸case-07 When deprecating field 4 in a Protobuf v3 message, we added 'reserved 4;' to prevent future tag collisions under full compatibility mode. Analyze this change and format output as JSON with compatible, breakingChanges, migrationScript, recommendations, and versionInfo. | fail→fail | 11,733 | 9,212 | -21% | 1 | 1 | 0% | 2,092 | 2,010 | -4% | 0 | 0 | — |
▸case-08 In Apache Avro schema evolution, we added a new field 'middle_name' of type ['null', 'string'] with default null under backward compatibility. Return JSON output with keys compatible, breakingChanges, migrationScript, recommendations, versionInfo. | pass→pass | 7,150 | 5,614 | -21% | 1 | 1 | 0% | 1,523 | 1,354 | -11% | 0 | 0 | — |
▸case-09 We changed 'additionalProperties' from true to false in our production API JSON Schema document under forward compatibility mode. Evaluate this modification and respond in JSON format with compatible, breakingChanges, migrationScript, recommendations, and versionInfo. | pass→fail | 9,224 | 14,165 | +54% | 1 | 1 | 0% | 1,643 | 2,939 | +79% | 0 | 0 | — |
▸case-10 An existing MySQL column 'legacy_hash' is being removed via DROP COLUMN in a database schema update under backward compatibility. Assess safety and supply JSON with compatible, breakingChanges, migrationScript, recommendations, versionInfo. | pass→pass | 9,973 | 9,741 | -2% | 1 | 1 | 0% | 1,721 | 1,783 | +4% | 0 | 0 | — |
▸case-11 In a Protobuf definition, we changed field tag 2 from int32 to int64 under backward compatibility mode. Evaluate safety and reply in JSON format with compatible, breakingChanges, migrationScript, recommendations, versionInfo. | fail→pass | 11,252 | 8,630 | -23% | 1 | 1 | 0% | 2,115 | 1,875 | -11% | 0 | 0 | — |
▸case-12 We expanded an Avro field type from ['string'] to ['string', 'int'] under forward compatibility mode. Evaluate compatibility and format response as JSON with keys compatible, breakingChanges, migrationScript, recommendations, versionInfo. | pass→pass | 13,578 | 7,675 | -43% | 1 | 1 | 0% | 2,375 | 1,718 | -28% | 0 | 0 | — |
▸case-13 In a JSON Schema document, the string pattern constraint for 'zipcode' was changed from '^[0-9]+$' to '^[0-9]{5}$' under backward mode. Respond with JSON formatted as compatible, breakingChanges, migrationScript, recommendations, versionInfo. | pass→pass | 8,018 | 6,832 | -15% | 1 | 1 | 0% | 1,573 | 1,766 | +12% | 0 | 0 | — |
▸case-14 We are adding a nullable TIMESTAMP column 'last_login' to an Apache Hive table under backward compatibility. Assess compatibility and produce output JSON containing compatible, breakingChanges, migrationScript, recommendations, versionInfo. | pass→pass | 8,237 | 4,448 | -46% | 1 | 1 | 0% | 1,416 | 1,189 | -16% | 0 | 0 | — |
▸case-15 We converted a .proto file from syntax = 'proto2' to syntax = 'proto3', changing required fields to optional. Check compatibility under full compatibility mode and output JSON with compatible, breakingChanges, migrationScript, recommendations, versionInfo. | pass→pass | 11,591 | 8,493 | -27% | 1 | 1 | 0% | 2,066 | 1,821 | -12% | 0 | 0 | — |
▸case-16 An Apache Avro record was renamed from 'UserV1' to 'UserProfile' without specifying an 'aliases' property under backward mode. Analyze compatibility and return JSON with keys compatible, breakingChanges, migrationScript, recommendations, versionInfo. | pass→pass | 8,548 | 5,930 | -31% | 1 | 1 | 0% | 1,648 | 1,433 | -13% | 0 | 0 | — |
▸case-17 In a JSON Schema, we added 'PENDING_APPROVAL' to an existing enum string array ['ACTIVE', 'INACTIVE'] under forward compatibility mode. Evaluate safety and respond with JSON matching compatible, breakingChanges, migrationScript, recommendations, versionInfo. | pass→pass | 7,844 | 6,938 | -12% | 1 | 1 | 0% | 1,456 | 1,657 | +14% | 0 | 0 | — |
▸case-18 We plan to execute RENAME TABLE user_orders TO customer_orders in Snowflake under full compatibility mode. Assess safety and produce JSON containing compatible, breakingChanges, migrationScript, recommendations, versionInfo. | pass→pass | 8,490 | 7,837 | -8% | 1 | 1 | 0% | 1,453 | 1,919 | +32% | 0 | 0 | — |
▸case-19 We are dropping three required columns from a SQL table definition and setting compatibilityMode to 'none'. Return JSON output with keys compatible, breakingChanges, migrationScript, recommendations, versionInfo. | fail→pass | 7,572 | 8,282 | +9% | 1 | 1 | 0% | 1,129 | 1,902 | +68% | 0 | 0 | — |
▸case-20 Our PostgreSQL database query on customer_orders(created_at, status) is performing slowly. Should we create a B-tree index or a BRIN index for historical timestamp partitioning? | pass→pass | 15,329 | 14,006 | -9% | 1 | 1 | 0% | 2,817 | 2,790 | -1% | 0 | 0 | — |
▸case-21 We are scaling our Apache Kafka event stream from 8 partitions to 32 partitions. How should we handle consumer group rebalancing and key hashing during this scale-out? | pass→pass | 16,748 | 16,073 | -4% | 1 | 1 | 0% | 2,744 | 3,014 | +10% | 0 | 0 | — |
▸case-22 How should we configure retry policies and SLA timeouts in an Apache Airflow DAG for an ELT pipeline that loads data from S3 to Snowflake? | pass→pass | 19,005 | 17,293 | -9% | 1 | 1 | 0% | 3,551 | 3,527 | -1% | 0 | 0 | — |