Thanks Viral, i pass this info onto aour dba's however i dont think the
problem is creating the tables, when looking at the logs Hive checks to see
if a table called COLUMNS exists and finds a View called COLUMNS instead and
therfore does not try to create the table after which any alter statements
Thanks Appan, the goal was just to have the metadata backing Hive in
SQLServer not the hadoopp data itself.. Our DBA.s monitored the sql
generated by DataNucleus against sql server and were typically non to happy
:-) Hive & SQL server therefore is a no goer for us at the moment so were
looking at a
If this is important enough you should probably patch the source code
to get this working and then submit a patch so those changes can be
rolled into a future version of hive.
My 2 cents.
-Vijay
On Mon, Mar 28, 2011 at 10:30 AM, Viral Bajaria wrote:
> Appan,
> Not sure if you meant to email me,
Appan,
Not sure if you meant to email me, but my setup uses MySQL for the
metastore. I ingest/export a lot of data to SqlServer.
Andy, for using SqlServer, the user's schema might be different but is it
owned by DBO ? Maybe instead of using the default msdb for CREATE DATABASE
your admins could u
Andy,
Here is a short term work around - If your goal is to backup data in SQL Server
just copy the data out of hadoop and import it into SQL (DTS / BCP/SSIS based
on which version you are in). Email Viral (I guess he is still active in the
email list) and I'm sure he is using Hive, Hadoop & SQ
Good Morning,
Our DBA's created a new schema associated with the database and then made
that the default schema for our hive user, unfortunately this resulted in
the same problem in the logs…
*“Check of existence of COLUMNS returned table type of VIEW”*
* *
*… *in that Hive still sees the def
Interesting. Sounds like a valid reason. I haven't used any version after 2k
myself hopefully the changing the default schema works.
Op 24 mrt. 2011 om 16:33 heeft "shared mailinglists"
mailto:shared.mailingli...@gmail.com>> het
volgende geschreven:
Thanks Bernie, hopefully they will.
Were a
Hi Carl,
Many thanks for your suggestions I will put these to our DBAs and see if we
can disable the default schema :-) Will post back soon.
Cheers & thanks for the rapid replies guys,
Andy.
On 24 March 2011 17:12, Carl Steinbach wrote:
> Hi Andy,
>
> From what I understand SQLServer has the
Hi Andy,
>From what I understand SQLServer has the notion of a "default schema"
(usually dbo) which is used to resolve identifiers that are not defined in a
user's current schema. I think you need to either undefine the default
schema for your metastore user account, or else make it point to the
m
Thanks Edward,
I actually added some notes to that JIRA issue. Yes DataNucleus should work,
but when debug logging is enabled I can see that Hive looks for the
existence of a table called COLUMNS. By default SQL server already has a
COLUMNS View and therefore the check returns true and the auto t
On Thu, Mar 24, 2011 at 11:36 AM, shared mailinglists
wrote:
> Thanks Bernie, hopefully they will.
>
> Were a small Java development team within a predominately MS development
> house. We’re hopefully introducing new ideas but the normal company politics
> dictate that we should use SQL Server. Th
Thanks Bernie, hopefully they will.
Were a small Java development team within a predominately MS development
house. We’re hopefully introducing new ideas but the normal company politics
dictate that we should use SQL Server. That way maintenance, backup, recover
etc etc can be handed over to the i
Sorry to become a bit offtopic but how do you get into a situation where
sqlserver 2005 becomes a requirement for a hive internal meta store?
I doubt many of the developers of hive will have access to this database
so I don't expect a lot of response on this. But hopefully someone can
prove me
Hi Hive users :-)
Does anybody have experience of using Hive with MS SQL Server 2005? I’m
currently stumped with the following issue
https://issues.apache.org/jira/browse/HIVE-1391 where Hive (or DataNucleus?)
confuses the COLUMNS table it requires internally with that of the default
SQL Server
14 matches
Mail list logo
