<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Invalid field schema option provided-DatabricksDeltaLakeSinkConnector in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/invalid-field-schema-option-provided/m-p/24685#M17178</link>
    <description>&lt;P&gt;I understand that config is on confluent side (Confluent Databricks AWS Delta Lake Sink Connector).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Common issue is S3 problem (roles). Can you check that anything is saved in S3 staging bucket?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can also contact confluent support. &lt;/P&gt;</description>
    <pubDate>Thu, 24 Mar 2022 19:10:25 GMT</pubDate>
    <dc:creator>Hubert-Dudek</dc:creator>
    <dc:date>2022-03-24T19:10:25Z</dc:date>
    <item>
      <title>Invalid field schema option provided-DatabricksDeltaLakeSinkConnector</title>
      <link>https://community.databricks.com/t5/data-engineering/invalid-field-schema-option-provided/m-p/24684#M17177</link>
      <description>&lt;P&gt;I have configured a Delta Lake Sink connector which reads from an AVRO topic and writes to the Delta lake  . I have followed the docs and my config looks like below . &lt;/P&gt;&lt;P&gt;&amp;nbsp;{&lt;/P&gt;&lt;P&gt;&amp;nbsp;"name": "dev_test_delta_connector",&lt;/P&gt;&lt;P&gt;&amp;nbsp;"config": {&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;"topics": "dl_test_avro",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;"input.data.format": "AVRO",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;"connector.class": "io.confluent.connect.databricks.deltalake.DatabricksDeltaLakeSinkConnector",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;"name": "dev_test_delta_connector",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;"kafka.auth.mode": "SERVICE_ACCOUNT",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;"kafka.service.account.id":"****",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;"delta.lake.host.name": "******",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;"delta.lake.http.path": "*********",&lt;/P&gt;&lt;P&gt;	"delta.lake.database":"dl_test_db",&lt;/P&gt;&lt;P&gt;	"delta.lake.token": "*********",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;"delta.lake.table.auto.create": "true",&lt;/P&gt;&lt;P&gt;	"delta.lake.table.format":"kafka_${topic}",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;"staging.bucket.name": "dl-test-bucket",&amp;nbsp;&lt;/P&gt;&lt;P&gt;	"s3.region":"eu-west-2",&lt;/P&gt;&lt;P&gt;	"staging.s3.access.key.id":"*************",&lt;/P&gt;&lt;P&gt;	"staging.s3.secret.access.key":"**********",	&lt;/P&gt;&lt;P&gt;	"confluent.topic.bootstrap.servers":"****************",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;"flush.interval.ms": "100",&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;"tasks.max": "1"&lt;/P&gt;&lt;P&gt;&amp;nbsp;}&lt;/P&gt;&lt;P&gt;}&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am expecting the connector to automatically create the table , but it errors out as :&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;"trace": "org.apache.kafka.connect.errors.ConnectException: Exiting WorkerSinkTask due to unrecoverable exception.\n\tat org.apache.kafka.connect.runtime.WorkerSinkTask.deliverMessages(WorkerSinkTask.java:568)\n\tat org.apache.kafka.connect.runtime.WorkerSinkTask.poll(WorkerSinkTask.java:326)\n\tat org.apache.kafka.connect.runtime.WorkerSinkTask.iteration(WorkerSinkTask.java:228)\n\tat org.apache.kafka.connect.runtime.WorkerSinkTask.execute(WorkerSinkTask.java:196)\n\tat org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:184)\n\tat org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:234)\n\tat java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)\n\tat java.util.concurrent.FutureTask.run(FutureTask.java:266)\n\tat java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)\n\tat java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)\n\tat java.lang.Thread.run(Thread.java:750)\nCaused by: org.apache.kafka.connect.errors.ConnectException: Invalid field schema option provided\n\tat io.confluent.connect.databricks.deltalake.DatabricksDeltaLakeSinkTask.convertFieldSchemaToTableSchema(DatabricksDeltaLakeSinkTask.java:368)\n\tat io.confluent.connect.databricks.deltalake.DatabricksDeltaLakeSinkTask.autoCreateTable(DatabricksDeltaLakeSinkTask.java:309)\n\tat io.confluent.connect.databricks.deltalake.DatabricksDeltaLakeSinkTask.recordsToPutToS3(DatabricksDeltaLakeSinkTask.java:146)\n\tat io.confluent.connect.databricks.deltalake.DatabricksDeltaLakeSinkTask.put(DatabricksDeltaLakeSinkTask.java:98)\n\tat org.apache.kafka.connect.runtime.WorkerSinkTask.deliverMessages(WorkerSinkTask.java:546)\n\t... 10 more\n"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help on this would be appreciated , thanks &lt;/P&gt;</description>
      <pubDate>Thu, 24 Mar 2022 19:01:42 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/invalid-field-schema-option-provided/m-p/24684#M17177</guid>
      <dc:creator>Bency</dc:creator>
      <dc:date>2022-03-24T19:01:42Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid field schema option provided-DatabricksDeltaLakeSinkConnector</title>
      <link>https://community.databricks.com/t5/data-engineering/invalid-field-schema-option-provided/m-p/24685#M17178</link>
      <description>&lt;P&gt;I understand that config is on confluent side (Confluent Databricks AWS Delta Lake Sink Connector).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Common issue is S3 problem (roles). Can you check that anything is saved in S3 staging bucket?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can also contact confluent support. &lt;/P&gt;</description>
      <pubDate>Thu, 24 Mar 2022 19:10:25 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/invalid-field-schema-option-provided/m-p/24685#M17178</guid>
      <dc:creator>Hubert-Dudek</dc:creator>
      <dc:date>2022-03-24T19:10:25Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid field schema option provided-DatabricksDeltaLakeSinkConnector</title>
      <link>https://community.databricks.com/t5/data-engineering/invalid-field-schema-option-provided/m-p/24686#M17179</link>
      <description>&lt;P&gt;Generally you need to be sure that confluent can connect to S3/Databricks resources (ip/roles) and this message from confluent is not much helpful &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Mar 2022 19:13:37 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/invalid-field-schema-option-provided/m-p/24686#M17179</guid>
      <dc:creator>Hubert-Dudek</dc:creator>
      <dc:date>2022-03-24T19:13:37Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid field schema option provided-DatabricksDeltaLakeSinkConnector</title>
      <link>https://community.databricks.com/t5/data-engineering/invalid-field-schema-option-provided/m-p/24687#M17180</link>
      <description>&lt;P&gt;@Hubert Dudek​&amp;nbsp;,  Should I be configuring anything with respect to schema in the connector config ? &lt;/P&gt;&lt;P&gt;Because I did successfully stage some data from another topic of a different format(JSON_SR) into delta lake table , but its with AVRO topic that I get this error. &lt;/P&gt;</description>
      <pubDate>Thu, 24 Mar 2022 19:23:17 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/invalid-field-schema-option-provided/m-p/24687#M17180</guid>
      <dc:creator>Bency</dc:creator>
      <dc:date>2022-03-24T19:23:17Z</dc:date>
    </item>
  </channel>
</rss>

