https://hive.apache.org/community/people/
On Wednesday, October 18, 2023, Edward Capriolo
wrote:
> Don't know if you guys are trolling me or not but I dont currently nor
> ever worked at hortonwoks lol
>
> --
> Sorry this was sent from mobile. Will do less grammar and spel
Don't know if you guys are trolling me or not but I dont currently nor ever
worked at hortonwoks lol
--
Sorry this was sent from mobile. Will do less grammar and spell check than
usual.
recommendation from the Hive team is to use the hive-exec.jar artifact.
You know about 10 years ago. I mentioned that oozie should just use
hive-service or hive jdbc. After a big fight where folks kept bringing up
concurrency bugs in hive-server-1 my prs were rejected (even though hive
server2 wou
t; It will be amazing if the community could produce a release every
> quarter/6months. :-)
>
> Le ven. 26 févr. 2021 à 14:30, Edward Capriolo a
> écrit :
>
>> Hive was releasable trunk for the longest time. Facebook days. Then the
>> big data vendors got more involved. Then it
I do not know how it works for most of the world. But in cloudera where the
TEZ options were never popular hive-on-spark represents a solid way to get
things done for small datasets lower latency.
As for the spark adoption. You know a while ago I came up with some ways to
make hive more spark lik
Hive was releasable trunk for the longest time. Facebook days. Then the big
data vendors got more involved. Then it became a pissing match about
features. This vendor likes tez this vendor dont, this vendor likes hive on
spark this one dont.
Then this vendor wants to tell everyone hive stinks use
Hello,
I would like to declare myself emeritus.
Thank you,
Edward Capriolo
--
Sorry this was sent from mobile. Will do less grammar and spell check than
usual.
I do not think we should remove:
https://issues.apache.org/jira/browse/HIVE-18692
One of the challenges of HQL is not having a procedure language. This
forces users into oozie/airflow/spark even to orchestrate simple flows.
Lets give that one some time to marinate, but I agree technically it coul
On Wed, Jul 5, 2017 at 1:51 PM, Alan Gates wrote:
> On Mon, Jul 3, 2017 at 6:20 AM, Edward Capriolo
> wrote:
>
> >
> > We already have things in the meta-store not directly tied to language
> > features. For example hive metastore has a "retention" propert
On Sun, Jul 2, 2017 at 10:15 PM, Alan Gates wrote:
> Comments inlined.
>
> On Sun, Jul 2, 2017 at 3:22 PM, Edward Capriolo
> wrote:
>
> > I am not sure I am on the fence with this.
> >
> > I am -1, and I offer this -1 with the hope of being convinced otherwise
ean "you" or "anyone" as a statement to a
particular person in this chain. I meant that: Forming a TLP should not
directly increase the commiter/pmc list to anyone not currently in the Hive
pmc/committer list.
On Sun, Jul 2, 2017 at 6:50 PM, Edward Capriolo
wrote:
>
>
On Fri, Jun 30, 2017 at 2:49 PM, Julian Hyde wrote:
> +1
>
> As a Calcite PMC member, I am very pleased to see this change. Calcite
> reads metadata from a variety of sources (including JDBC databases, NoSQL
> databases such as Cassandra and Druid, and streaming systems), and if more
> of those s
I am not sure I am on the fence with this.
On Sat, Jul 1, 2017 at 6:38 AM, Chaoyu Tang wrote:
> +1. A nice move which might help HMS to be more easily adopted by more
> other components.
>
> On Sat, Jul 1, 2017 at 12:41 AM, Sushanth Sowmyan
> wrote:
>
> > +1
> >
> > On Jun 30, 2017 17:05, "Owen
On Mon, Apr 3, 2017 at 7:40 PM, Edward Capriolo
wrote:
> I think we should take this opportunity to move to apache-hive. I dont
> think anyone every used this channel for anything. There is many things on
> the internet named hive and naturally it will get spam-ish. We could also
&
Hello impala devs!
Let me say that I have used impala a lot and am very impressed with it.
I know impala is moving into the Apache incubator (I have an incubator
prodling gossip so I know this is challenging). There are few things I want
to bring to your attention/discuss, so that they do not bec
I think we should take this opportunity to move to apache-hive. I dont
think anyone every used this channel for anything. There is many things on
the internet named hive and naturally it will get spam-ish. We could also
renew an effort to actually use IRC.
On Fri, Mar 31, 2017 at 8:59 PM, Sergey S
Also i dont follow how we remove
On Saturday, March 4, 2017, Edward Capriolo wrote:
>
>
> On Fri, Mar 3, 2017 at 8:46 PM, Thejas Nair > wrote:
>
>> +1
>> There are some features that are incomplete and what I would not recommend
>> for any real production use.T
On Fri, Mar 3, 2017 at 8:46 PM, Thejas Nair wrote:
> +1
> There are some features that are incomplete and what I would not recommend
> for any real production use.The 'legacy authorization mode' is a great
> example of that -
> https://cwiki.apache.org/confluence/display/Hive/Hive+
> Default+Auth
Im not a fan of this our feature branching was supposed to protect us from
broken trumk syndrome.
I am a believer in releaseable trunk. Make it work and keep it working.
On Friday, March 3, 2017, Sergey Shelukhin wrote:
> Can we at least release 2.2 first? There’s massive amount of unreleased
>
nd ask that they not do this.
>
> As for them dissing on us in benchmarks, we all know you can set up Hive
> to run like mule (use MR on text files) and people do it all the time to
> make their stuff look good. I'm not sure what to do about that other than
> publish our own benc
early to discuss but we welcome your suggestion.
>
> Thanks,
> Makoto
>
> 2017-03-03 15:15 GMT+09:00 Edward Capriolo :
> > Hivemall in the incubator has a fairly impressive set of features that do
> > machine learning directly from hive.
> >
> > http://hivemal
Hivemall in the incubator has a fairly impressive set of features that do
machine learning directly from hive.
http://hivemall.incubator.apache.org/overview.html
https://github.com/myui/hivemall/wiki/Logistic-regression-dataset-generation
While we can not put the cart before the horse, i can imag
gt;
> Reading about Hive at Facebook, I feel like we've already solved those
> problems that were due to FB Corona + Hadoop-1 (or, 0.20 *shudder*)
> limitations.
>
> Spark does not need be limited by Corona and the version of Hive being
> compared might not have YARN or Tez
All,
I have compiled a short (non exhaustive) list of items related to Spark's
forking of Apache Hive code and usage of Apache Hive trademarks.
1)
The original spark proposal repeatedly claims that Spark "inter operates"
with hive.
https://wiki.apache.org/incubator/S
Good stuff!
On Fri, Apr 29, 2016 at 1:30 PM, Jörn Franke wrote:
> Dear all,
>
> I prepared a small Serde to analyze Bitcoin blockchain data with Hive:
>
> https://snippetessay.wordpress.com/2016/04/28/hive-bitcoin-analytics-on-blockchain-data-with-sql/
>
> There are some example queries, but I w
becomes a
> burden, and it’s outdated with 2 alternatives, one of which has been
> around for 2 releases.
> The branches are a graceful way to get rid of the legacy burden.
>
> Alternatively, when sweeping changes are made, we can do what Hbase did
> (which is not pretty imho), wher
API was (mapred,
new mapreduce), no one know what to link off of cdh?, vanilla?, yahoo
distribution?.
IMHO. This is just going to increase fragmentation.
On Mon, May 18, 2015 at 1:04 PM, Edward Capriolo
wrote:
> Up until recently Hive supported numerous versions of Hadoop code base
> w
Up until recently Hive supported numerous versions of Hadoop code base with
a simple shim layer. I would rather we stick to the shim layer. I think
this was easily the best part about hive was that a single release worked
well regardless of your hadoop version. It was also a key element to hive's
s
using this instability.
Like i said, I get around it by running a load balancer etc, but I do not
want to be 100% reliant on it.
On Thu, Apr 30, 2015 at 10:39 AM, Edward Capriolo
wrote:
> For what it is worth, even with all the enhancements made to hive-server 2
> it is just not as rel
For what it is worth, even with all the enhancements made to hive-server 2
it is just not as reliable as the CLI. I am actually using cloudera 5.3 and
we have multiple hive-server2 instances behind a load balancer. The load we
are doing is not particularly heavy and the mean time to failure is < 3
To reiterate, one thing I want to avoid is having hive rely on code that
sits in several tiny silos across Apache projects, or Apache Licensed but
not ASF projects. Hive is a mature TLP with a large number of committers
and it would not be a good situation if often work gets bottle necked
because c
Recently I found out about the
http://www.gnu.org/licenses/gcc-exception.html which is interesting, and
governs some projects/components. Like intel's high performance collection
library.
On Fri, Feb 20, 2015 at 9:16 PM, Alan Gates wrote:
> No.
>
> Alan.
>
> Alexander Pivovarov
> February 20
[
https://issues.apache.org/jira/browse/HIVE-9664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14317581#comment-14317581
]
Edward Capriolo commented on HIVE-9664:
---
Just so you know. You can use a groovy
Because we can not really have a stable api if by definition we build
around snapshot dependencies.
On Mon, Feb 9, 2015 at 11:38 AM, Edward Capriolo
wrote:
> Question.
>
> https://issues.apache.org/jira/browse/HIVE-8614
>
> Did we not just agree in this thread that hive wi
Question.
https://issues.apache.org/jira/browse/HIVE-8614
Did we not just agree in this thread that hive will no long have dependency
that are SNAPSHOT?
On Fri, Jan 23, 2015 at 1:06 AM, Brock Noland wrote:
> Hi Alan,
>
> I agree with Xuefu and what was suggested in your statement. I was
> thin
[
https://issues.apache.org/jira/browse/HIVE-8614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14312431#comment-14312431
]
Edward Capriolo commented on HIVE-8614:
---
This is bad. Hive should not depen
A while back the datastax people did this for brisk + cassandra. We should
probably make this pluggable so it works with nosql beyond hbase.
On Fri, Jan 23, 2015 at 1:48 AM, Nick Dimiduk wrote:
> +1
>
> On Thursday, January 22, 2015, Brock Noland wrote:
>
> > +1
> >
> > On Thu, Jan 22, 2015 at
If we do a 1.0.0 release there is no problem with us later releasing 14.1
or a 14.2. I think everyone would understand that the 14.2 being released
after 1.0.0 would likely have back ported features. Releasing a 15.0 after
1.0 would not make as much sense as we probably do not want two active
branc
[
https://issues.apache.org/jira/browse/HIVE-8848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Capriolo updated HIVE-8848:
--
Status: Open (was: Patch Available)
You can re-open if I am wrong but in TextInputFormats null
[
https://issues.apache.org/jira/browse/HIVE-8848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14218908#comment-14218908
]
Edward Capriolo edited comment on HIVE-8848 at 11/20/14 2:2
[
https://issues.apache.org/jira/browse/HIVE-8848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14218906#comment-14218906
]
Edward Capriolo commented on HIVE-8848:
---
Nulls are supposed to be stored
[
https://issues.apache.org/jira/browse/HIVE-5538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14207314#comment-14207314
]
Edward Capriolo commented on HIVE-5538:
---
I do not like the idea of turnin
+1
On Tue, Oct 7, 2014 at 7:51 PM, Vikram Dixit wrote:
> +1
>
> On Tue, Oct 7, 2014 at 4:44 PM, Bill Busch
> wrote:
> > +1
> >
> > Follow me on @BigData73
> >
> > -Original Message-
> > From: Gunther Hagleitner [mailto:ghagleit...@hortonworks.com]
> > Sent: Tuesday, October 07, 2014 7
[
https://issues.apache.org/jira/browse/HIVE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14098623#comment-14098623
]
Edward Capriolo commented on HIVE-1434:
---
There is going to be no jira. I am d
[
https://issues.apache.org/jira/browse/HIVE-5538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14088074#comment-14088074
]
Edward Capriolo commented on HIVE-5538:
---
{quote}If so, one possibility is to tur
[
https://issues.apache.org/jira/browse/HIVE-5538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062456#comment-14062456
]
Edward Capriolo commented on HIVE-5538:
---
This is especially relavant since we
[
https://issues.apache.org/jira/browse/HIVE-5538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062176#comment-14062176
]
Edward Capriolo commented on HIVE-5538:
---
I would suggest that we handle thi
So Everyone is running around saying "hive is slow" "x is faster". I think
hive's biggest issue is that the mr2 entire process to acquire containers
and then launch a job in them is super overkill. I see it result in 40
seconds startup time for what amounts to a 2 second job. In the old hadoop
0.20
[
https://issues.apache.org/jira/browse/HIVE-7025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14054910#comment-14054910
]
Edward Capriolo commented on HIVE-7025:
---
I like this. I coded something like thi
[
https://issues.apache.org/jira/browse/HIVE-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14040802#comment-14040802
]
Edward Capriolo commented on HIVE-3392:
---
Please feel free to take over the revie
[
https://issues.apache.org/jira/browse/HIVE-5857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14029325#comment-14029325
]
Edward Capriolo commented on HIVE-5857:
---
{code}
} catch (FileNotFoundException
[
https://issues.apache.org/jira/browse/HIVE-7115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025767#comment-14025767
]
Edward Capriolo commented on HIVE-7115:
---
That would be really nice especially i
[
https://issues.apache.org/jira/browse/HIVE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Capriolo resolved HIVE-1434.
---
Resolution: Won't Fix
> Cassandra Storage
[
https://issues.apache.org/jira/browse/HIVE-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025539#comment-14025539
]
Edward Capriolo commented on HIVE-1434:
---
This feature is a complete utter fai
[
https://issues.apache.org/jira/browse/HIVE-5538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14016114#comment-14016114
]
Edward Capriolo commented on HIVE-5538:
---
Do we thing we are rushing this? Bes
[
https://issues.apache.org/jira/browse/HIVE-5538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14016115#comment-14016115
]
Edward Capriolo commented on HIVE-5538:
---
To be clear we need a long term solutio
+1
On Tue, May 27, 2014 at 7:54 PM, Alan Gates wrote:
> +1 (non-binding) - Built it, checked the signature and md5, and ran some
> basic tests.
>
> Alan.
>
> On May 23, 2014, at 1:45 AM, Sushanth Sowmyan wrote:
>
> >
> > Apache Hive 0.13.1 Release Candidate 2 is available here:
> >
> > http://
[
https://issues.apache.org/jira/browse/HIVE-7121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14008377#comment-14008377
]
Edward Capriolo commented on HIVE-7121:
---
Does this effect bucketed tables? I t
"Voting will conclude in 72 hours."
This statement is not correct. The vote stays open as long as it needs to.
The 72 hour window is a window for someone to register a -1 vote. The vote
stays open until it passes. So... if there are two +1 votes in 24 hours and
6 days later someone registers the t
[
https://issues.apache.org/jira/browse/HIVE-7025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13992808#comment-13992808
]
Edward Capriolo commented on HIVE-7025:
---
We do something similar however we
My protobuf server
https://github.com/edwardcapriolo/hive-protobuf/extracts the schema
from a class name.
The avro serde does similar things.
On Mon, May 5, 2014 at 9:31 PM, Eugene Koifman wrote:
> Hi,
> is it possible to write a SerDe (or something else) so that DESCRIBE
> (as we all query
LOL. I thought I was the last 0.20.2 hold out.
On Wed, Apr 23, 2014 at 4:01 PM, Thejas Nair wrote:
> There is a jira for the hadoop 1.0.x compatibility issue.
> https://issues.apache.org/jira/browse/HIVE-6962
> I have suggested a possible workaround there. There is no patch for it yet.
>
> I am
[
https://issues.apache.org/jira/browse/HIVE-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13977685#comment-13977685
]
Edward Capriolo commented on HIVE-6469:
---
If a user is willing to commit an opti
[
https://issues.apache.org/jira/browse/HIVE-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13973210#comment-13973210
]
Edward Capriolo commented on HIVE-1608:
---
It is not much. SequenceFile + none (c
[
https://issues.apache.org/jira/browse/HIVE-6212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967874#comment-13967874
]
Edward Capriolo commented on HIVE-6212:
---
We dont support presto.
> Using
[
https://issues.apache.org/jira/browse/HIVE-6212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Edward Capriolo resolved HIVE-6212.
---
Resolution: Won't Fix
Contact presto developers.
> Using Presto-0.56 for sql q
[
https://issues.apache.org/jira/browse/HIVE-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13961224#comment-13961224
]
Edward Capriolo commented on HIVE-1608:
---
If the sequence file is not compresse
I believe thrift has two transports , framed an unframed, cassandra used to
topple over with random messagea to thrift. We should look at how they
hardened it.
On Wednesday, April 2, 2014, Vaibhav Gumashta (JIRA)
wrote:
>
> [
https://issues.apache.org/jira/browse/HIVE-6468?page=com.atlassian.
[
https://issues.apache.org/jira/browse/HIVE-6721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13954359#comment-13954359
]
Edward Capriolo commented on HIVE-6721:
---
[~alangates]
One trick I notice a
[
https://issues.apache.org/jira/browse/HIVE-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13951675#comment-13951675
]
Edward Capriolo commented on HIVE-6570:
---
No major concern the release note is en
[
https://issues.apache.org/jira/browse/HIVE-6570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13932506#comment-13932506
]
Edward Capriolo commented on HIVE-6570:
---
WE should make a release note if som
quests as patches. Just that we'll be notified of them and could
> perhaps use them as code review.
>
> One additional item I think we should investigate is disabling merge
> commits on trunk and feature branches.
> On Mar 7, 2014 7:57 PM, "Edward Capriolo" wrote:
>
gt;
> >
> > On Fri, Mar 7, 2014 at 11:06 PM, Thejas Nair
> > wrote:
> >
> > > OK, so just one of the pages in wiki has changed, and hive behavior
> > > has not changed ? (I have been using -hiveconf, but i haven't verified
> > > that with the ti
I was not around when this change was made but I think we should have kept
the old - dash version. We should consider adding it back.
On Fri, Mar 7, 2014 at 8:56 PM, Lefty Leverenz wrote:
> Xuefu just fixed the AdminManual Configuration
> wiki<
> https://cwiki.apache.org/confluence/display/Hive/
We need to keep patches in Jira I feel. We have gotten better on the
documentation front but having a patch in the jira is critical I feel. We
must at least have a perma link to the changes.
On Fri, Mar 7, 2014 at 8:40 PM, Sergey Shelukhin wrote:
> +1 to git!
>
>
> On Fri, Mar 7, 2014 at 12:46 P
nk. Or, Ed are you still planning to use Hive on
> Hadoop 0.20.2, 6 months from now (or whenever 0.14 gets released)
>
> Thanks,
> Ashutosh
>
>
> On Thu, Sep 19, 2013 at 7:11 PM, Edward Capriolo >wrote:
>
> > Remeber that the shim layer will continue to exist.
>
[
https://issues.apache.org/jira/browse/HIVE-6311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882432#comment-13882432
]
Edward Capriolo commented on HIVE-6311:
---
I really like the hive logo. I surely
[
https://issues.apache.org/jira/browse/HIVE-6167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868485#comment-13868485
]
Edward Capriolo commented on HIVE-6167:
---
In my opinion we must keep the cur
[
https://issues.apache.org/jira/browse/HIVE-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866153#comment-13866153
]
Edward Capriolo commented on HIVE-6171:
---
If I had to be picky I see methods n
[
https://issues.apache.org/jira/browse/HIVE-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13864890#comment-13864890
]
Edward Capriolo commented on HIVE-6047:
---
Theoreticallly you could compile anyt
[
https://issues.apache.org/jira/browse/HIVE-6047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13863870#comment-13863870
]
Edward Capriolo commented on HIVE-6047:
---
We just added the ability to write UDF
[
https://issues.apache.org/jira/browse/HIVE-6100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13863402#comment-13863402
]
Edward Capriolo commented on HIVE-6100:
---
I think Alan and I are speaking of
[
https://issues.apache.org/jira/browse/HIVE-6100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13863147#comment-13863147
]
Edward Capriolo commented on HIVE-6100:
---
Having UDFs would still be useful. I u
"silos", and as the project adds more "silos"
the number of people who review issues outside of their silos is not
growing.
On Sun, Dec 29, 2013 at 1:05 PM, Edward Capriolo wrote:
> I think the terms is good. We do not want to have a lame duck scenario.
>
> Strict
t spelling)*.
>
>
> -- Lefty
>
>
> On Fri, Dec 27, 2013 at 6:12 PM, Ashutosh Chauhan >wrote:
>
> > This is what Thejas has also suggested earlier in thread. Sounds good to
> > me.
> >
> >
> > On Fri, Dec 27, 2013 at 5:43 PM, Edward Capriolo
" I propose to modify
> that one such that there must be 24 hour duration between creation of jira
> and patch commit, that will ensure that there is sufficient time for folks
> to see changes which are happening on trunk."
One thing. Many of the jira's have little detail. So someone could file a
I like the changes. I believe rotating the PMC chair will keep the project
fresh. Work and life events come in spurts, and it's hard to step down when
your at the top (
http://disinfo.com/2013/02/ratzinger-resigns-first-pope-to-quit-since-1415/
:) .
On Thu, Dec 26, 2013 at 10:08 PM, Carl Steinbac
[
https://issues.apache.org/jira/browse/HIVE-5783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13841693#comment-13841693
]
Edward Capriolo edited comment on HIVE-5783 at 12/6/13 8:5
[
https://issues.apache.org/jira/browse/HIVE-5783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13841693#comment-13841693
]
Edward Capriolo commented on HIVE-5783:
---
{quote}
I would normally agree with
[
https://issues.apache.org/jira/browse/HIVE-5783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13841674#comment-13841674
]
Edward Capriolo commented on HIVE-5783:
---
{quote}
regarding the support being b
[
https://issues.apache.org/jira/browse/HIVE-5783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13841601#comment-13841601
]
Edward Capriolo commented on HIVE-5783:
---
Why does support need to be build dire
[
https://issues.apache.org/jira/browse/HIVE-5875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13830393#comment-13830393
]
Edward Capriolo commented on HIVE-5875:
---
hive.mapred.mode=st
[
https://issues.apache.org/jira/browse/HIVE-5317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13826207#comment-13826207
]
Edward Capriolo commented on HIVE-5317:
---
{quote}
"In theory the base can
[
https://issues.apache.org/jira/browse/HIVE-5317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13826191#comment-13826191
]
Edward Capriolo commented on HIVE-5317:
---
{quote}
Ed,
If you don't use t
[
https://issues.apache.org/jira/browse/HIVE-5317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13825619#comment-13825619
]
Edward Capriolo commented on HIVE-5317:
---
By the way. I do work like this very o
[
https://issues.apache.org/jira/browse/HIVE-5317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13825611#comment-13825611
]
Edward Capriolo commented on HIVE-5317:
---
I have two fundamental problems with
[
https://issues.apache.org/jira/browse/HIVE-5731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13818289#comment-13818289
]
Edward Capriolo commented on HIVE-5731:
---
{quote}
GenericUDF class is the latest
[
https://issues.apache.org/jira/browse/HIVE-5107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13817813#comment-13817813
]
Edward Capriolo commented on HIVE-5107:
---
Generally it is better to but unit t
The future is here!
On Thu, Oct 31, 2013 at 3:11 PM, Brock Noland wrote:
> More details here
>
> https://issues.apache.org/jira/browse/HIVE-5610
>
> How to configure your development environment is here:
>
> https://cwiki.apache.org/confluence/display/Hive/HiveDeveloperFAQ
>
[
https://issues.apache.org/jira/browse/HIVE-5602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13808331#comment-13808331
]
Edward Capriolo commented on HIVE-5602:
---
Thanks for looking.
> Micro o
1 - 100 of 1477 matches
Mail list logo
