Re: does anyone care about list bucketing stored as directories?

[Xuefu Zhang]

Lack a response doesn't necessarily means "don't care". Maybe you can have
a good description of the problem and proposed solution. Frankly I cannot
make much sense out of the previous email.

Thanks,
Xuefu

On Fri, Oct 6, 2017 at 5:05 PM, Sergey Shelukhin 
wrote:

> Looks like nobody does… I’ll file a ticket to remove it shortly.
>
> From: Sergey Shelukhin >
> Date: Tuesday, October 3, 2017 at 12:59
> To: "u...@hive.apache.org" <
> u...@hive.apache.org>, "dev@hive.apache.org
> "  v...@hive.apache.org>>
> Subject: does anyone care about list bucketing stored as directories?
>
> 1) There seem to be some bugs and limitations in LB (e.g. incorrect
> cleanup - https://issues.apache.org/jira/browse/HIVE-14886) and nobody
> appears to as much as watch JIRAs ;) Does anyone actually use this stuff?
> Should we nuke it in 3.0, and by 3.0 I mean I’ll remove it from master in a
> few weeks? :)
>
> 2) I actually wonder, on top of the same SQL syntax, wouldn’t it be much
> easier to add logic to partitioning to write skew values into partitions
> and non-skew values into a new type of default partition? It won’t affect
> nearly as many low level codepaths in obscure and unobvious ways, instead
> keeping all the logic in metastore and split generation, and would
> integrate with Hive features like PPD automatically.
> Esp. if we are ok with the same limitations - e.g. if you add a new skew
> value right now, I’m not sure what happens to the rows with that value
> already sitting in the non-skew directories, but I don’t expect anything
> reasonable...
>
>

[jira] [Created] (HIVE-17744) Acid LockManager optimization

[Eugene Koifman (JIRA)]

Eugene Koifman created HIVE-17744:
-

 Summary: Acid LockManager optimization
 Key: HIVE-17744
 URL: https://issues.apache.org/jira/browse/HIVE-17744
 Project: Hive
  Issue Type: Bug
  Components: Transactions
Reporter: Eugene Koifman
Assignee: Eugene Koifman


does it make sense to periodically compute and store min(lock_id) of a 
Write/semi shared lock to know that all earlier locks are Read locks and thus 
don't need to be even retrieved from storage to check if a new Read/semi shared 
lock can be granted?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (HIVE-17743) Add InterfaceAudience and InterfaceStability annotations for Thrift generated APIs

[Sahil Takiar (JIRA)]

Sahil Takiar created HIVE-17743:
---

 Summary: Add InterfaceAudience and InterfaceStability annotations 
for Thrift generated APIs
 Key: HIVE-17743
 URL: https://issues.apache.org/jira/browse/HIVE-17743
 Project: Hive
  Issue Type: Sub-task
  Components: Thrift API
Reporter: Sahil Takiar
Assignee: Sahil Takiar


The Thrift generated files don't have {{InterfaceAudience}} or 
{{InterfaceStability}} annotations on them, mainly because all the files are 
auto-generated.

We should add some code that auto-tags all the Java Thrift generated files with 
these annotations. This way even when they are re-generated, they still contain 
the annotations.

We should be able to do this using the 
{{com.google.code.maven-replacer-plugin}} similar to what we do in 
{{standalone-metastore/pom.xml}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (HIVE-17742) AccumuloIndexedOutputFormat Use SLF4J

[BELUGA BEHR (JIRA)]

BELUGA BEHR created HIVE-17742:
--

 Summary: AccumuloIndexedOutputFormat Use SLF4J
 Key: HIVE-17742
 URL: https://issues.apache.org/jira/browse/HIVE-17742
 Project: Hive
  Issue Type: Improvement
  Components: Accumulo Storage Handler
Affects Versions: 3.0.0
Reporter: BELUGA BEHR
Priority: Trivial


{{org.apache.hadoop.hive.accumulo.mr.AccumuloIndexedOutputFormat}}

# Change to use SL4J instead of core Log4J classes
# Use SL4J parameterization



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (HIVE-17741) hive server2 ha register 0.0.0.0 to zookeeper

[Nie Gus (JIRA)]

Nie Gus created HIVE-17741:
--

 Summary: hive server2 ha register 0.0.0.0 to zookeeper
 Key: HIVE-17741
 URL: https://issues.apache.org/jira/browse/HIVE-17741
 Project: Hive
  Issue Type: Bug
  Components: HiveServer2
Reporter: Nie Gus
Assignee: Nie Gus
Priority: Blocker


Hive Server2 HA based on zookeeper. 

when set hive.server2.thrift.bind.host to "0.0.0.0"

hive server2 will register this "0.0.0.0" to zookeeper, and when client request 
the hive server address, it will return the wrong address "0.0.0.0".

 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)