https://pinot.apache.org/ logo
Join Slack
Powered by
# general
  • k

    Kishore G

    10/30/2019, 7:14 PM
    ah, may be validation is failing
  • k

    Kishore G

    10/30/2019, 7:15 PM
    can you paste the schema or send it via DM
  • a

    Alex

    10/30/2019, 7:26 PM
    same schema I was using when running locally
  • a

    Alex

    10/30/2019, 7:26 PM
    1 sec
  • j

    Jackie

    10/30/2019, 7:37 PM
    @User When you try to add the schema, are you sending a PUT request or GET request? If you got the 404, probably you are sending the GET?
  • a

    Alex

    10/30/2019, 7:37 PM
    I’m using PinotAdministrator
  • a

    Alex

    10/30/2019, 7:37 PM
    it looks like internally it is doing file upload
  • a

    Alex

    10/30/2019, 7:38 PM
    image.png
  • a

    Alex

    10/30/2019, 7:39 PM
    image.png
  • k

    Kishore G

    10/30/2019, 8:00 PM
    created https://github.com/apache/incubator-pinot/issues/4762
  • k

    Kishore G

    10/30/2019, 8:01 PM
    @User please add steps you followed
  • a

    Alex

    10/30/2019, 8:01 PM
    1 sec
  • a

    Alex

    10/30/2019, 8:06 PM
    done
  • j

    Jackie

    10/30/2019, 8:06 PM
    @User I tried on my local box and is able to post the schema with
    ./pinot-admin.sh AddSchema -controllerPort 8100 -schemaFile <filePath>
    (My controller is running on port 8100)
  • a

    Alex

    10/30/2019, 8:07 PM
    local box worked for me as well
  • a

    Alex

    10/30/2019, 8:07 PM
    kube proxy didn’t
  • a

    Alex

    10/30/2019, 8:07 PM
    😕
  • a

    Alex

    10/30/2019, 8:07 PM
    not a big deal, jsut weird
  • k

    Kishore G

    10/30/2019, 8:11 PM
    if I have to guess, its got to do with some http headers we set from pinot admin code vs what curl sets
  • k

    Kishore G

    10/30/2019, 8:12 PM
    can you do curl -v and dump the headers
  • a

    Alex

    10/30/2019, 8:16 PM
    Copy code
    curl -v localhost:9000/schemas
    *   Trying ::1...
    * TCP_NODELAY set
    * Connected to localhost (::1) port 9000 (#0)
    > GET /schemas HTTP/1.1
    > Host: localhost:9000
    > User-Agent: curl/7.63.0
    > Accept: */*
    >
    < HTTP/1.1 200 OK
    < Pinot-Controller-Host: pinot-controller-0.pinot-controller.pinot.svc.cluster.local
    < Pinot-Controller-Version: 0.2.0-SNAPSHOT-e74ff90aff7cf0f110c91a1698ee72905e10f593
    < Access-Control-Allow-Origin: *
    < Content-Type: application/json
    < Content-Length: 15
    <
    * Connection #0 to host localhost left intact
    ["orders"]
  • a

    Alex

    10/30/2019, 10:42 PM
    hi, does pinot pay attention to x-forwarded-proto headers?
  • a

    Alex

    10/30/2019, 10:43 PM
    I put it behind https gateway and while queries are working, some operations are not
  • j

    Jackie

    10/30/2019, 10:46 PM
    @User AFAIK, we don't check this header. @User Do you know if we use this header?
  • a

    Alex

    10/30/2019, 10:53 PM
    @User by operations I meant swagger UI examples. It tries to call over http
  • k

    Kishore G

    10/30/2019, 10:54 PM
    We don’t look into those headers explicitly
  • a

    Alex

    10/30/2019, 10:55 PM
    this one was an issue for the swagger - https://github.com/RicoSuter/NSwag/pull/2196
  • a

    Alex

    10/30/2019, 10:55 PM
    ups, that is wrong one )
  • s

    Subbu Subramaniam

    10/30/2019, 11:00 PM
    we dont look for the headers expliciitly. In fact, we use X-Forwarded-Proto setting to $scheme in nginx where we place the controllers behind nginx
  • c

    Chinmay Soman

    11/01/2019, 6:04 PM
    @User ^^
1...909192...160Latest