[Backlogmanager] [FIWARE-JIRA] (HELP-9296) [fiware-stackoverflow] Error accessing Cosmos through Hive

[Fernando Lopez (JIRA)]

     [ https://jira.fiware.org/browse/HELP-9296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fernando Lopez updated HELP-9296:
---------------------------------
    Status: Answered  (was: In Progress)

> [fiware-stackoverflow] Error accessing Cosmos through Hive
> ----------------------------------------------------------
>
>                 Key: HELP-9296
>                 URL: https://jira.fiware.org/browse/HELP-9296
>             Project: Help-Desk
>          Issue Type: Monitor
>          Components: FIWARE-TECH-HELP
>            Reporter: Backlog Manager
>            Assignee: Francisco Romero
>              Labels: fiware, fiware-cosmos, fiware-cygnus
>
> Created question in FIWARE Q/A platform on 14-09-2015 at 11:09
> {color: red}Please, ANSWER this question AT{color} https://stackoverflow.com/questions/32561861/error-accessing-cosmos-through-hive
> +Question:+
> Error accessing Cosmos through Hive
> +Description:+
> Literally from:
> https://ask.fiware.org/question/84/cosmos-error-accessing-hive/
> As the answer in the quoted FIWARE Q&A entry suggest the problem is fixed by now. its here: https://ask.fiware.org/question/79/cosmos-database-privacy/. However, it seems like other issues arisen related to the solution, namely: Through ssh connection, the typing the hive command results in the following error: https://cloud.githubusercontent.com/assets/13782883/9439517/0d24350a-4a68-11e5-9a46-9d8a24e016d4.png the hiveSQL queries work fine (through ssh) regardless the error message.
> When launching exactly the same hiveSQL queries (each one of them worked flawlessly two weeks ago) remotely, the request times out even in absurd time windows (10 minutes). The most basic commands ('use $username;', 'show tables';) also time out.
> (The thrift client is: https://github.com/garamon/php-thrift-hive-client)
> Since the Cosmos usage is an integral part of our project, it is of utmost importance whether it is a temporal issue caused by the fixes or it is a permanent change in the remote availability (could not identify relevant changes in the documentation).



--
This message was sent by Atlassian JIRA
(v6.4.1#64016)