Hello! I have problem with metadata ingestion from...
# ingestion
b
Hello! I have problem with metadata ingestion from kafka-connect source. if my connector connects to sqlserver via jdbc then ingestion fails because of sqlserver jdbc connection string does not confront to rfc1738 spec. 😞 Has someone workaround for this?
h
Hey @bright-egg-4386 how does your sqlserver jdbc connection string look like ?
b
In my case: jdbc:sqlserver://GS-NAVDEV01:1433;database=GSTEST (https://docs.microsoft.com/en-us/sql/connect/jdbc/building-the-connection-url?view=sql-server-ver15). Even for oracle database connection string validation is failed.
g
Hey @bright-egg-4386 - it looks like we do not support this at the moment. @hundreds-photographer-13496 can give us some guidance on what it would take to support this. Is this critical for you to use Datahub?
b
We use MSSQL and Oracle databases as JDBC source/sink in Kafka Connect service. Datahub kafka connect plugin is almost useless in our case. To get it work I added connection strings text replacement in plugin source code to get it work. As temporary solution it works.
g
Got it- we will work on adding this support then cc @hundreds-photographer-13496
h
Hi, I am getting tjhe same issue when using kafka connect with oracle(jdbce source connector) . @bright-egg-4386 - Can you please help on the workaround solution? @green-football-43791 - This issue still exist and do plan to add support anytime soon. Thank you
@hundreds-photographer-13496 _ any resolution? I am getting the same error while connecting to oracle thro kafka connect. also i would like to know what should be the value of path_key and also the format of valu if i am using provided_configs optional parameter to override the existing issue
h
Hi Priyanka! Unfortunately I haven't been able to get to it. Would you mind creating a github issue ? Please mention the redacted oracle JDBC URL you are using. I believe , the core implementation piece required here is the logic to implement a different parser for oracle/sql-server that can process these URLS to extract 1. database used (
database_name
) 2. redacted or sanitized url as a property(
db_connection_url
) (Ref) It would be great if you or your team can contribute this support OR I can attempt to get to it somewhere next month.