Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Fri, 29 Aug 2014 00:21:08 +0000 (UTC)
From: "Suhas Satish (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12736430.1408917480547.5695.1409271668821@arcas>
In-Reply-To: <JIRA.12736430.1408917480547@arcas>
References: <JIRA.12736430.1408917480547@arcas>
Subject: [jira] [Updated] (HIVE-7869) Long running tests (1) [Spark Branch]
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HIVE-7869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Suhas Satish updated HIVE-7869:
-------------------------------

    Status: Patch Available  (was: Open)

> Long running tests (1) [Spark Branch]
> -------------------------------------
>
>                 Key: HIVE-7869
>                 URL: https://issues.apache.org/jira/browse/HIVE-7869
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Spark
>            Reporter: Brock Noland
>            Assignee: Suhas Satish
>         Attachments: HIVE-7869-spark.patch
>
>
> I have noticed when running the full test suite locally that the test JVM eventually crashes. We should do some testing (not part of the unit tests) which starts up a HS2 and runs queries on it continuously for 24 hours or so.
> In this JIRA let's create a stand alone java program which connects to a HS2 over JDBC, creates a bunch of tables (say 100) and then runs queries until the JDBC client is killed. This will allow us to run long running tests.


--
This message was sent by Atlassian JIRA
(v6.2#6252)