Hitachi Vantara Pentaho Community Forums
Results 1 to 4 of 4

Thread: Saiku through proxy (nginx)

  1. #1
    Join Date
    Jan 2013
    Posts
    100

    Default Saiku through proxy (nginx)

    Hi. I'm having problems with working Saiku through proxy (nginx). Dimension filtering does not work (picture 1). By clicking on the dimensions given as follows:
    Code:
    Remote Address:192.168.133.128:80
    Request URL:http://olap.ru/pentaho/plugin/saiku/api/api/query/6AA5FA7F-29BF-CDB2-9F2C-A79CAD522AFE/result/metadata/hierarchies/%5BCustomers%5D/levels/Customer?result=true&searchlimit=3000&_=1421863217024
    Request Method:GET
    Status Code:400 Bad Request
    Request Headers
    Accept:application/json, text/javascript, */*; q=0.01
    Accept-Encoding:gzip, deflate, sdch
    Accept-Language:ru-RU,ru;q=0.8,en-US;q=0.6,en;q=0.4
    Connection:keep-alive
    Content-Type:application/x-www-form-urlencoded
    Cookie:JSESSIONID=AA97B3112606EE8927A1912633B459A0; session-flushed=true; JSESSIONID=E6C9E531280631BE9585EE7F0EA51216
    Host:olap.ru
    Referer:http://olap.ru/pentaho/content/saiku-ui/index.html?biplugin5=true&ts=1421863216736
    User-Agent:Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.99 Safari/537.36
    X-Requested-With:XMLHttpRequest
    Query String Parameters
    result:true
    searchlimit:3000
    _:1421863217024
    Response Headers
    Connection:keep-alive
    Content-Length:990
    Content-Type:text/html;charset=utf-8
    Date:Wed, 21 Jan 2015 18:04:29 GMT
    Server:nginx/1.2.1
    If you work with Saiku no through proxy, the dimensions filtering works correctly (picture 2). And browser given as follows:
    Code:
    Remote Address:192.168.133.131:8080
    Request URL:http://192.168.133.131:8080/pentaho/plugin/saiku/api/api/query/51FDFE1B-52CE-B549-8D51-44F742D7C0B5/result/metadata/hierarchies/%5BCustomers%5D/levels/Customer?result=true&searchlimit=3000&_=1421863797797
    Request Method:GET
    Status Code:200 OK
    Request Headers
    Accept:application/json, text/javascript, */*; q=0.01
    Accept-Encoding:gzip, deflate, sdch
    Accept-Language:ru-RU,ru;q=0.8,en-US;q=0.6,en;q=0.4
    Connection:keep-alive
    Content-Type:application/x-www-form-urlencoded
    Cookie:JSESSIONID=307A808950BA432FA0714B660E010753; session-flushed=true; JSESSIONID=2226796939574E006FE4F3315A9841EB
    Host:192.168.133.131:8080
    Referer:http://192.168.133.131:8080/pentaho/content/saiku-ui/index.html?biplugin5=true&ts=1421863797484
    User-Agent:Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.99 Safari/537.36
    X-Requested-With:XMLHttpRequest
    Query String Parameters
    result:true
    searchlimit:3000
    _:1421863797797
    Response Headers
    Content-Type:application/json
    Date:Wed, 21 Jan 2015 18:10:25 GMT
    Server:Apache-Coyote/1.1
    Transfer-Encoding:chunked
    Attached Images Attached Images

  2. #2
    Join Date
    Jan 2013
    Posts
    100

    Default

    Somebody uses Saiku through nginx?

  3. #3
    Join Date
    Nov 2015
    Posts
    15

    Default

    I got the same error, ¿someone knows how to fix it?

  4. #4
    Join Date
    Sep 2011
    Posts
    3

    Default

    I had a similar problem with other proxy server and the solution went rewrite the schema replacing all attributes name that contained white spaces for "_" or eliminate the white spaces. For example:

    old schema version <Dimension type="StandardDimension" visible="true" foreignKey="sk_natureza_ocupacao" highCardinality="false" name="Natureza Da Ocupacao" ...
    after correction <Dimension type="StandardDimension" visible="true" foreignKey="sk_natureza_ocupacao" highCardinality="false" name="Natureza_Da_Ocupacao" ...

    I don't know if your issue is the same but I believe that you should try this solucion

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Privacy Policy | Legal Notices | Safe Harbor Privacy Policy

Copyright © 2005 - 2017 Pentaho Corporation. All Rights Reserved.