[jira] [Updated] (HIVE-13163) ORC MemoryManager thread checks are fatal, should WARN
[
https://issues.apache.org/jira/browse/HIVE-13163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gopal V updated HIVE-13163:
---
Resolution: Fixed
Fix Version/s: 2.1.0
Status: Resolved (was: Patch Available)
Committed to master, thanks [~prasanth_j]
> ORC MemoryManager thread checks are fatal, should WARN
> ---
>
> Key: HIVE-13163
> URL: https://issues.apache.org/jira/browse/HIVE-13163
> Project: Hive
> Issue Type: Bug
> Components: ORC
>Affects Versions: 2.0.0, 2.1.0
>Reporter: Gopal V
>Assignee: Gopal V
> Labels: PIG
> Fix For: 2.1.0
>
> Attachments: HIVE-13163.1.patch
>
>
> The MemoryManager is tied to a WriterOptions on create, which can occur in a
> different thread from the writer calls.
> This is unexpected, but safe and needs a warning not a fatal.
> {code}
> /**
>* Light weight thread-safety check for multi-threaded access patterns
>*/
> private void checkOwner() {
> Preconditions.checkArgument(ownerLock.isHeldByCurrentThread(),
> "Owner thread expected %s, got %s",
> ownerLock.getOwner(),
> Thread.currentThread());
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HIVE-13163) ORC MemoryManager thread checks are fatal, should WARN
[
https://issues.apache.org/jira/browse/HIVE-13163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gopal V updated HIVE-13163:
---
Status: Patch Available (was: Open)
> ORC MemoryManager thread checks are fatal, should WARN
> ---
>
> Key: HIVE-13163
> URL: https://issues.apache.org/jira/browse/HIVE-13163
> Project: Hive
> Issue Type: Bug
> Components: ORC
>Affects Versions: 2.0.0, 2.1.0
>Reporter: Gopal V
>Assignee: Gopal V
> Labels: PIG
> Attachments: HIVE-13163.1.patch
>
>
> The MemoryManager is tied to a WriterOptions on create, which can occur in a
> different thread from the writer calls.
> This is unexpected, but safe and needs a warning not a fatal.
> {code}
> /**
>* Light weight thread-safety check for multi-threaded access patterns
>*/
> private void checkOwner() {
> Preconditions.checkArgument(ownerLock.isHeldByCurrentThread(),
> "Owner thread expected %s, got %s",
> ownerLock.getOwner(),
> Thread.currentThread());
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HIVE-13163) ORC MemoryManager thread checks are fatal, should WARN
[
https://issues.apache.org/jira/browse/HIVE-13163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gopal V updated HIVE-13163:
---
Attachment: HIVE-13163.1.patch
> ORC MemoryManager thread checks are fatal, should WARN
> ---
>
> Key: HIVE-13163
> URL: https://issues.apache.org/jira/browse/HIVE-13163
> Project: Hive
> Issue Type: Bug
> Components: ORC
>Affects Versions: 2.0.0, 2.1.0
>Reporter: Gopal V
>Assignee: Gopal V
> Labels: PIG
> Attachments: HIVE-13163.1.patch
>
>
> The MemoryManager is tied to a WriterOptions on create, which can occur in a
> different thread from the writer calls.
> This is unexpected, but safe and needs a warning not a fatal.
> {code}
> /**
>* Light weight thread-safety check for multi-threaded access patterns
>*/
> private void checkOwner() {
> Preconditions.checkArgument(ownerLock.isHeldByCurrentThread(),
> "Owner thread expected %s, got %s",
> ownerLock.getOwner(),
> Thread.currentThread());
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HIVE-13163) ORC MemoryManager thread checks are fatal, should WARN
[
https://issues.apache.org/jira/browse/HIVE-13163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gopal V updated HIVE-13163:
---
Labels: PIG (was: )
> ORC MemoryManager thread checks are fatal, should WARN
> ---
>
> Key: HIVE-13163
> URL: https://issues.apache.org/jira/browse/HIVE-13163
> Project: Hive
> Issue Type: Bug
> Components: ORC
>Affects Versions: 2.0.0, 2.1.0
>Reporter: Gopal V
>Assignee: Gopal V
> Labels: PIG
>
> The MemoryManager is tied to a WriterOptions on create, which can occur in a
> different thread from the writer calls.
> This is unexpected, but safe and needs a warning not a fatal.
> {code}
> /**
>* Light weight thread-safety check for multi-threaded access patterns
>*/
> private void checkOwner() {
> Preconditions.checkArgument(ownerLock.isHeldByCurrentThread(),
> "Owner thread expected %s, got %s",
> ownerLock.getOwner(),
> Thread.currentThread());
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
