[GitHub] hive pull request #417: HIVE-20386: Allow not to strip hidden fields from Hi...

2018-08-14 Thread beltran
GitHub user beltran opened a pull request: https://github.com/apache/hive/pull/417 HIVE-20386: Allow not to strip hidden fields from Hiveconf You can merge this pull request into a Git repository by running: $ git pull https://github.com/beltran/hive HIVE-20386 Alternatively

hi

2018-06-26 Thread zhaodam...@sunlands.com
I`m using the junit test in hive project ,hcatalog streaming mutation,as saind in https://cwiki.apache.org/confluence/display/Hive/HCatalog+Streaming+Mutation+API Coordinators will verify a naturally ordered sequence of [lastTransactionId, rowId] and will throw an exception if this sequence

[jira] [Created] (HIVE-15639) HI

2017-01-16 Thread Jesus Camacho Rodriguez (JIRA)
Jesus Camacho Rodriguez created HIVE-15639: -- Summary: HI Key: HIVE-15639 URL: https://issues.apache.org/jira/browse/HIVE-15639 Project: Hive Issue Type: Bug Components

Re: hi

2013-04-18 Thread Jarek Jarcec Cecho
> Might take more time initially - so, making it a constraint might slow us > > down. > > > > > > On 4/18/13 9:41 PM, "Brock Noland" wrote: > > > > >Hi, > > > > > >I like the proposal as well! > > > > > >On Thu, Ap

Re: hi

2013-04-18 Thread Brock Noland
cult to write unit tests for operator > trees. > Might take more time initially - so, making it a constraint might slow us > down. > > > On 4/18/13 9:41 PM, "Brock Noland" wrote: > > >Hi, > > > >I like the proposal as well! > > > >On T

Re: hi

2013-04-18 Thread Namit Jain
Having said that, it might be difficult to write unit tests for operator trees. Might take more time initially - so, making it a constraint might slow us down. On 4/18/13 9:41 PM, "Brock Noland" wrote: >Hi, > >I like the proposal as well! > >On Thu, Apr 18, 2013 at 10:

Re: hi

2013-04-18 Thread Brock Noland
Hi, I like the proposal as well! On Thu, Apr 18, 2013 at 10:49 AM, Jarek Jarcec Cecho wrote: > Hi Namit, > I like your proposal very much and I would take it a bit further: > > > 1. ... For any complex function, clear examples (input/output) would > really help. >

Re: hi

2013-04-18 Thread Namit Jain
Agreed. On 4/18/13 9:19 PM, "Jarek Jarcec Cecho" wrote: >Hi Namit, >I like your proposal very much and I would take it a bit further: > >> 1. ... For any complex function, clear examples (input/output) would >>really help. > >I'm concerned that

Re: hi

2013-04-18 Thread Jarek Jarcec Cecho
Hi Namit, I like your proposal very much and I would take it a bit further: > 1. ... For any complex function, clear examples (input/output) would > really help. I'm concerned that examples in the code (comments) might very quickly become obsolete as it can very easily happen t

Re: hi

2013-04-18 Thread Gang Tim Liu
Super like it. On 4/18/13 5:31 AM, "Namit Jain" wrote: >Hi, > >Since we are developing at a very fast pace, it would be really useful to >think about maintainability and testing of the large codebase. >Historically, we have not focussed on a few things, and they might s

hi

2013-04-18 Thread Namit Jain
Hi, Since we are developing at a very fast pace, it would be really useful to think about maintainability and testing of the large codebase. Historically, we have not focussed on a few things, and they might soon bite us. I wanted to propose the following for all checkins: 1. Javadoc for