I-Snowpark Scala isebenzisa umshayeli we-Snowflake JDBC ukuxhuma. Umakhi wesikhathi sayo wamukela izimfanelo zokuhlelwa kwe-JDBC, ngakho izilungiselelo zeproxy zingahamba nemebala yokuxhumana ekhona:

val proxyOptions = Map(
  "useProxy" -> "true",
  "proxyHost" -> "proxy.example",
  "proxyPort" -> "8080"
)

val session = com.snowflake.snowpark.Session.builder
  .configs(connectionOptions ++ proxyOptions)
  .create

connectionOptions iqukethe i-akhawunti, ukuqinisekisa kanye nezinye izilungiselelo umsebenzi osewuzisebenzisayo. Lezi zingenelelo zemebala yezinhlamvu ze-Scala; igama lomsingathi weproxy alinayo isikimu se-URL noma imbobo yaso. Ngomzila weproxy womphakathi ovunyelwe ngaphandle kokuqinisekisa kweproxy, khetha umsingathi nembobo ku-uhlu lwamaproxy e-HTTP ngenkathi ugcina izilungiselelo ze-akhawunti ye-Snowflake.

I-Snowflake JDBC ibuye ibhale proxyUser ne-proxyPassword ye-akhawunti yomlamuli. Zinikeze ngomthombo wemininingwane yokuqinisekisa okhona womsebenzi uma kudingeka.

Isimfanelo se-JDBC nonProxyHosts sisebenzisa amaphethini ahlukaniswe ngomugqa oqondile ngokusekelwa kwe-wildcard. Kunani lemebala, isihlukanisi siwukuthi | ngokwezwi; ukufakwa kwekhodi kwe-URL kubalulekile kuphela lapho kwakhiwa i-JDBC URL. Ungakushintshi ngesintaksi se-NO_PROXY somunye iklayenti esihlukaniswe ngokhefana.

Gcina lokhu kuhlelwa kukhethekile ku-Snowpark Scala. I-Snowpark Python kanye nesixhumi se-Snowflake Spark ziletha izixhumanisi zokuxhumana namagama ezinketho ahlukile.

I-Snowflake idinga ukuthi isitifiketi sesevisi sidlule kuproxy ngaphandle kokushintshwa. Umzila we-HTTP CONNECT nokuhlolwa kwe-TLS kuyizinhlelo ezahlukene; iproxy ekhipha kabusha isitifiketi se-Snowflake ayifezi leso simo.

Izihloko ezihlobene