Haɗa masana'antar safarar wakili zuwa abokin ciniki na REST na BigQuery Java

Yi amfani da HttpTransportOptions a kan tsarin aikin da takardun shaidar da suke akwai, tare da saitin safara daban idan takardar shaidar da kanta tana yin buƙatun token.

import java.net.InetSocketAddress;
import java.net.Proxy;
import com.google.api.client.http.javanet.NetHttpTransport;
import com.google.cloud.http.HttpTransportOptions;
import com.google.cloud.bigquery.BigQuery;
import com.google.cloud.bigquery.BigQueryOptions;

var proxy = new Proxy(Proxy.Type.HTTP,
    new InetSocketAddress("proxy.example", 8080));
var httpOptions = HttpTransportOptions.newBuilder()
    .setHttpTransportFactory(() ->
        new NetHttpTransport.Builder().setProxy(proxy).build())
    .build();

BigQuery bigQuery = BigQueryOptions.newBuilder()
    .setProjectId(projectId)
    .setCredentials(credentials)
    .setTransportOptions(httpOptions)
    .build()
    .getService();

Yi amfani da wannan bigQuery don ayyukan REST. projectId da credentials suna zuwa daga tsarin da aikace-aikacen ke da shi.

Masana'antar tana ƙirƙirar safarar HTTP wadda ta isa API na BigQuery ta hanyar mai shiga tsakani. Ƙarshen API ɗin ya kasance makoma; maye gurbinsa da adireshin wakili yana neman wata sabis. Don hanyar wakili na jama'a da aka yarda zuwa BigQuery, jerin wakilan HTTP yana ba da 'yan takara don filayen InetSocketAddress.

Samun ko sabunta takardar shaidar na iya samun nata safarar HTTP, don haka saita wannan shigarwar da ake tallafawa lokacin da buƙatunta ke buƙatar wakili. Waɗannan zaɓuɓɓukan REST kuma ba sa saita tashar gRPC mai zaman kanta.

Don gano tsarin, java.net.useSystemProxies yana da ɗabi'a ta musamman ga dandamali kuma ba ya tabbatar da cewa darajar Docker HTTP_PROXY za ta zama hanyar wannan abokin ciniki. Masana'antar bayyananna da ke sama tana sa safarar REST da aka zaɓa a bayyane a lokacin ginawa.

Labarai masu alaƙa