[jira] [Created] (ASTERIXDB-2316) NPE on Dataset Full Merge

[Murtadha Hubail (JIRA)]

Murtadha Hubail created ASTERIXDB-2316:
--

 Summary: NPE on Dataset Full Merge
 Key: ASTERIXDB-2316
 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2316
 Project: Apache AsterixDB
  Issue Type: Bug
  Components: STO - Storage
Reporter: Murtadha Hubail
Assignee: Murtadha Hubail


To reproduce run:
{code:java}
create type a as {id:int};
compact dataset Metadata.`Datatype`;
{code}
Stack trace:
{code:java}
java.lang.NullPointerException: null
at 
org.apache.hyracks.storage.am.lsm.common.util.LSMComponentIdUtils.persist(LSMComponentIdUtils.java:52)
 ~[classes/:?]
at 
org.apache.asterix.common.ioopcallbacks.AbstractLSMIOOperationCallback.putComponentIdIntoMetadata(AbstractLSMIOOperationCallback.java:198)
 ~[classes/:?]
at 
org.apache.asterix.common.ioopcallbacks.AbstractLSMIOOperationCallback.afterOperation(AbstractLSMIOOperationCallback.java:122)
 ~[classes/:?]
at 
org.apache.hyracks.storage.am.lsm.common.impls.LSMHarness.merge(LSMHarness.java:639)
 [classes/:?]
at 
org.apache.hyracks.storage.am.lsm.common.impls.LSMTreeIndexAccessor.merge(LSMTreeIndexAccessor.java:128)
 [classes/:?]
at 
org.apache.hyracks.storage.am.lsm.common.impls.MergeOperation.call(MergeOperation.java:45)
 [classes/:?]
at 
org.apache.hyracks.storage.am.lsm.common.impls.MergeOperation.call(MergeOperation.java:30)
 [classes/:?]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_151]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 
[?:1.8.0_151]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 
[?:1.8.0_151]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_151]
{code}
 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Change in asterixdb[master]: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back

[Jenkins (Code Review)]

Jenkins has posted comments on this change.

Change subject: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back
..


Patch Set 4:

Build Started 
https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-notopic/8432/ (1/12)

-- 
To view, visit https://asterix-gerrit.ics.uci.edu/2456
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: If8d5df630f1d9119002ef91da5c282da18901acc
Gerrit-PatchSet: 4
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Murtadha Hubail 
Gerrit-Reviewer: Anon. E. Moose #1000171
Gerrit-Reviewer: Ian Maxon 
Gerrit-Reviewer: Jenkins 
Gerrit-Reviewer: Luo Chen 
Gerrit-Reviewer: Michael Blow 
Gerrit-Reviewer: Murtadha Hubail 
Gerrit-Reviewer: Till Westmann 
Gerrit-Reviewer: abdullah alamoudi 
Gerrit-HasComments: No

Change in asterixdb[master]: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back

[Jenkins (Code Review)]

Jenkins has posted comments on this change.

Change subject: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back
..


Patch Set 4:

Build Started 
https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-asterix-app-sql-execution/2972/
 (8/12)

-- 
To view, visit https://asterix-gerrit.ics.uci.edu/2456
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: If8d5df630f1d9119002ef91da5c282da18901acc
Gerrit-PatchSet: 4
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Murtadha Hubail 
Gerrit-Reviewer: Anon. E. Moose #1000171
Gerrit-Reviewer: Ian Maxon 
Gerrit-Reviewer: Jenkins 
Gerrit-Reviewer: Luo Chen 
Gerrit-Reviewer: Michael Blow 
Gerrit-Reviewer: Murtadha Hubail 
Gerrit-Reviewer: Till Westmann 
Gerrit-Reviewer: abdullah alamoudi 
Gerrit-HasComments: No

Change in asterixdb[master]: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back

[Jenkins (Code Review)]

Jenkins has posted comments on this change.

Change subject: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back
..


Patch Set 4:

Build Started 
https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-cancellation-test/2961/ 
(12/12)

-- 
To view, visit https://asterix-gerrit.ics.uci.edu/2456
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: If8d5df630f1d9119002ef91da5c282da18901acc
Gerrit-PatchSet: 4
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Murtadha Hubail 
Gerrit-Reviewer: Anon. E. Moose #1000171
Gerrit-Reviewer: Ian Maxon 
Gerrit-Reviewer: Jenkins 
Gerrit-Reviewer: Luo Chen 
Gerrit-Reviewer: Michael Blow 
Gerrit-Reviewer: Murtadha Hubail 
Gerrit-Reviewer: Till Westmann 
Gerrit-Reviewer: abdullah alamoudi 
Gerrit-HasComments: No

Change in asterixdb[master]: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back

[Jenkins (Code Review)]

Jenkins has posted comments on this change.

Change subject: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back
..


Patch Set 4:

Build Started 
https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-ensure-ancestor/982/ 
(4/12)

-- 
To view, visit https://asterix-gerrit.ics.uci.edu/2456
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: If8d5df630f1d9119002ef91da5c282da18901acc
Gerrit-PatchSet: 4
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Murtadha Hubail 
Gerrit-Reviewer: Anon. E. Moose #1000171
Gerrit-Reviewer: Ian Maxon 
Gerrit-Reviewer: Jenkins 
Gerrit-Reviewer: Luo Chen 
Gerrit-Reviewer: Michael Blow 
Gerrit-Reviewer: Murtadha Hubail 
Gerrit-Reviewer: Till Westmann 
Gerrit-Reviewer: abdullah alamoudi 
Gerrit-HasComments: No

Change in asterixdb[master]: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back

[Jenkins (Code Review)]

Jenkins has posted comments on this change.

Change subject: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back
..


Patch Set 4:

Build Started 
https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-source-assemblies/3192/ 
(7/12)

-- 
To view, visit https://asterix-gerrit.ics.uci.edu/2456
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: If8d5df630f1d9119002ef91da5c282da18901acc
Gerrit-PatchSet: 4
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Murtadha Hubail 
Gerrit-Reviewer: Anon. E. Moose #1000171
Gerrit-Reviewer: Ian Maxon 
Gerrit-Reviewer: Jenkins 
Gerrit-Reviewer: Luo Chen 
Gerrit-Reviewer: Michael Blow 
Gerrit-Reviewer: Murtadha Hubail 
Gerrit-Reviewer: Till Westmann 
Gerrit-Reviewer: abdullah alamoudi 
Gerrit-HasComments: No

Change in asterixdb[master]: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back

[Jenkins (Code Review)]

Jenkins has posted comments on this change.

Change subject: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back
..


Patch Set 4:

Build Started 
https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-sonar/6925/ (5/12)

-- 
To view, visit https://asterix-gerrit.ics.uci.edu/2456
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: If8d5df630f1d9119002ef91da5c282da18901acc
Gerrit-PatchSet: 4
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Murtadha Hubail 
Gerrit-Reviewer: Anon. E. Moose #1000171
Gerrit-Reviewer: Ian Maxon 
Gerrit-Reviewer: Jenkins 
Gerrit-Reviewer: Luo Chen 
Gerrit-Reviewer: Michael Blow 
Gerrit-Reviewer: Murtadha Hubail 
Gerrit-Reviewer: Till Westmann 
Gerrit-Reviewer: abdullah alamoudi 
Gerrit-HasComments: No

Change in asterixdb[master]: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back

[Jenkins (Code Review)]

Jenkins has posted comments on this change.

Change subject: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back
..


Patch Set 4:

Build Started 
https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-verify-asterix-app/3449/ 
(6/12)

-- 
To view, visit https://asterix-gerrit.ics.uci.edu/2456
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: If8d5df630f1d9119002ef91da5c282da18901acc
Gerrit-PatchSet: 4
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Murtadha Hubail 
Gerrit-Reviewer: Anon. E. Moose #1000171
Gerrit-Reviewer: Ian Maxon 
Gerrit-Reviewer: Jenkins 
Gerrit-Reviewer: Luo Chen 
Gerrit-Reviewer: Michael Blow 
Gerrit-Reviewer: Murtadha Hubail 
Gerrit-Reviewer: Till Westmann 
Gerrit-Reviewer: abdullah alamoudi 
Gerrit-HasComments: No

Change in asterixdb[master]: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back

[Jenkins (Code Review)]

Jenkins has posted comments on this change.

Change subject: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back
..


Patch Set 4:

Build Started 
https://asterix-jenkins.ics.uci.edu/job/asterix-verify-storage/3506/ (11/12)

-- 
To view, visit https://asterix-gerrit.ics.uci.edu/2456
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: If8d5df630f1d9119002ef91da5c282da18901acc
Gerrit-PatchSet: 4
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Murtadha Hubail 
Gerrit-Reviewer: Anon. E. Moose #1000171
Gerrit-Reviewer: Ian Maxon 
Gerrit-Reviewer: Jenkins 
Gerrit-Reviewer: Luo Chen 
Gerrit-Reviewer: Michael Blow 
Gerrit-Reviewer: Murtadha Hubail 
Gerrit-Reviewer: Till Westmann 
Gerrit-Reviewer: abdullah alamoudi 
Gerrit-HasComments: No

Change in asterixdb[master]: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back

[Murtadha Hubail (Code Review)]

Hello Anon. E. Moose #1000171, Jenkins,

I'd like you to reexamine a change.  Please visit

https://asterix-gerrit.ics.uci.edu/2456

to look at the new patch set (#4).

Change subject: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back
..

[NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back

- user model changes: no
- storage format changes: no
- interface changes: yes

Details:
- Ensure rollback of an atomic transaction starts
  from its first LSN.
- Ensure update logs of uncommitted atomic transactions
  are undone during recovery.
- ASTERIXDB-2316: pass correct merging components.
- Add test case for atomic transaction rollback after
  flush.
- Add test cases for atomic transaction recovery after
  flush and merge.

Change-Id: If8d5df630f1d9119002ef91da5c282da18901acc
---
M 
asterixdb/asterix-app/src/main/java/org/apache/asterix/app/nc/RecoveryManager.java
M 
asterixdb/asterix-app/src/test/java/org/apache/asterix/test/metadata/MetadataTxnTest.java
M 
asterixdb/asterix-app/src/test/java/org/apache/asterix/test/txn/RecoveryManagerTest.java
M 
asterixdb/asterix-common/src/main/java/org/apache/asterix/common/transactions/ITransactionContext.java
M 
asterixdb/asterix-metadata/src/main/java/org/apache/asterix/metadata/MetadataNode.java
M 
asterixdb/asterix-metadata/src/main/java/org/apache/asterix/metadata/api/IExtensionMetadataEntity.java
M 
asterixdb/asterix-metadata/src/main/java/org/apache/asterix/metadata/api/IMetadataEntity.java
M 
asterixdb/asterix-metadata/src/main/java/org/apache/asterix/metadata/entities/CompactionPolicy.java
M 
asterixdb/asterix-metadata/src/main/java/org/apache/asterix/metadata/entities/Dataset.java
M 
asterixdb/asterix-metadata/src/main/java/org/apache/asterix/metadata/entities/DatasourceAdapter.java
M 
asterixdb/asterix-metadata/src/main/java/org/apache/asterix/metadata/entities/Datatype.java
M 
asterixdb/asterix-metadata/src/main/java/org/apache/asterix/metadata/entities/Dataverse.java
M 
asterixdb/asterix-metadata/src/main/java/org/apache/asterix/metadata/entities/Feed.java
M 
asterixdb/asterix-metadata/src/main/java/org/apache/asterix/metadata/entities/FeedConnection.java
M 
asterixdb/asterix-metadata/src/main/java/org/apache/asterix/metadata/entities/FeedPolicyEntity.java
M 
asterixdb/asterix-metadata/src/main/java/org/apache/asterix/metadata/entities/Function.java
M 
asterixdb/asterix-metadata/src/main/java/org/apache/asterix/metadata/entities/Index.java
M 
asterixdb/asterix-metadata/src/main/java/org/apache/asterix/metadata/entities/Library.java
M 
asterixdb/asterix-metadata/src/main/java/org/apache/asterix/metadata/entities/NodeGroup.java
A 
asterixdb/asterix-transactions/src/main/java/org/apache/asterix/transaction/management/opcallbacks/MetadataIndexModificationOperationCallback.java
M 
asterixdb/asterix-transactions/src/main/java/org/apache/asterix/transaction/management/service/transaction/AtomicTransactionContext.java
M 
asterixdb/asterix-transactions/src/main/java/org/apache/asterix/transaction/management/service/transaction/EntityLevelTransactionContext.java
M 
hyracks-fullstack/hyracks/hyracks-api/src/main/java/org/apache/hyracks/api/util/InvokeUtil.java
M 
hyracks-fullstack/hyracks/hyracks-storage-am-lsm-common/src/main/java/org/apache/hyracks/storage/am/lsm/common/impls/AbstractLSMIndex.java
24 files changed, 493 insertions(+), 77 deletions(-)


  git pull ssh://asterix-gerrit.ics.uci.edu:29418/asterixdb 
refs/changes/56/2456/4
-- 
To view, visit https://asterix-gerrit.ics.uci.edu/2456
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: newpatchset
Gerrit-Change-Id: If8d5df630f1d9119002ef91da5c282da18901acc
Gerrit-PatchSet: 4
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Murtadha Hubail 
Gerrit-Reviewer: Anon. E. Moose #1000171
Gerrit-Reviewer: Ian Maxon 
Gerrit-Reviewer: Jenkins 
Gerrit-Reviewer: Luo Chen 
Gerrit-Reviewer: Michael Blow 
Gerrit-Reviewer: Murtadha Hubail 
Gerrit-Reviewer: Till Westmann 
Gerrit-Reviewer: abdullah alamoudi 

Change in asterixdb[master]: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back

[Jenkins (Code Review)]

Jenkins has posted comments on this change.

Change subject: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back
..


Patch Set 4:

Build Started https://asterix-jenkins.ics.uci.edu/job/hyracks-gerrit/2887/ 
(9/12)

-- 
To view, visit https://asterix-gerrit.ics.uci.edu/2456
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: If8d5df630f1d9119002ef91da5c282da18901acc
Gerrit-PatchSet: 4
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Murtadha Hubail 
Gerrit-Reviewer: Anon. E. Moose #1000171
Gerrit-Reviewer: Ian Maxon 
Gerrit-Reviewer: Jenkins 
Gerrit-Reviewer: Luo Chen 
Gerrit-Reviewer: Michael Blow 
Gerrit-Reviewer: Murtadha Hubail 
Gerrit-Reviewer: Till Westmann 
Gerrit-Reviewer: abdullah alamoudi 
Gerrit-HasComments: No

Change in asterixdb[master]: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back

[Jenkins (Code Review)]

Jenkins has posted comments on this change.

Change subject: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back
..


Patch Set 4:

Build Started 
https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-asterix-app/3697/ (10/12)

-- 
To view, visit https://asterix-gerrit.ics.uci.edu/2456
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: If8d5df630f1d9119002ef91da5c282da18901acc
Gerrit-PatchSet: 4
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Murtadha Hubail 
Gerrit-Reviewer: Anon. E. Moose #1000171
Gerrit-Reviewer: Ian Maxon 
Gerrit-Reviewer: Jenkins 
Gerrit-Reviewer: Luo Chen 
Gerrit-Reviewer: Michael Blow 
Gerrit-Reviewer: Murtadha Hubail 
Gerrit-Reviewer: Till Westmann 
Gerrit-Reviewer: abdullah alamoudi 
Gerrit-HasComments: No

Change in asterixdb[master]: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back

[Jenkins (Code Review)]

Jenkins has posted comments on this change.

Change subject: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back
..


Patch Set 4:

Build Started 
https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-verify-no-installer-app/3425/
 (3/12)

-- 
To view, visit https://asterix-gerrit.ics.uci.edu/2456
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: If8d5df630f1d9119002ef91da5c282da18901acc
Gerrit-PatchSet: 4
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Murtadha Hubail 
Gerrit-Reviewer: Anon. E. Moose #1000171
Gerrit-Reviewer: Ian Maxon 
Gerrit-Reviewer: Jenkins 
Gerrit-Reviewer: Luo Chen 
Gerrit-Reviewer: Michael Blow 
Gerrit-Reviewer: Murtadha Hubail 
Gerrit-Reviewer: Till Westmann 
Gerrit-Reviewer: abdullah alamoudi 
Gerrit-HasComments: No

Change in asterixdb[master]: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back

[Jenkins (Code Review)]

Jenkins has posted comments on this change.

Change subject: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back
..


Patch Set 4:

Build Started 
https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-source-format/2935/ 
(2/12)

-- 
To view, visit https://asterix-gerrit.ics.uci.edu/2456
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: If8d5df630f1d9119002ef91da5c282da18901acc
Gerrit-PatchSet: 4
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Murtadha Hubail 
Gerrit-Reviewer: Anon. E. Moose #1000171
Gerrit-Reviewer: Ian Maxon 
Gerrit-Reviewer: Jenkins 
Gerrit-Reviewer: Luo Chen 
Gerrit-Reviewer: Michael Blow 
Gerrit-Reviewer: Murtadha Hubail 
Gerrit-Reviewer: Till Westmann 
Gerrit-Reviewer: abdullah alamoudi 
Gerrit-HasComments: No

Change in asterixdb[master]: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back

[Jenkins (Code Review)]

Jenkins has posted comments on this change.

Change subject: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back
..


Patch Set 4:

WARNING: THIS CHANGE CONTAINS CROSS-PRODUCT CHANGES IN:
* asterixdb
* hyracks-fullstack

PLEASE REVIEW CAREFULLY AND LOOK FOR API CHANGES!

-- 
To view, visit https://asterix-gerrit.ics.uci.edu/2456
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: If8d5df630f1d9119002ef91da5c282da18901acc
Gerrit-PatchSet: 4
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Murtadha Hubail 
Gerrit-Reviewer: Anon. E. Moose #1000171
Gerrit-Reviewer: Ian Maxon 
Gerrit-Reviewer: Jenkins 
Gerrit-Reviewer: Luo Chen 
Gerrit-Reviewer: Michael Blow 
Gerrit-Reviewer: Murtadha Hubail 
Gerrit-Reviewer: Till Westmann 
Gerrit-Reviewer: abdullah alamoudi 
Gerrit-HasComments: No

Change in asterixdb[master]: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back

[Anon. E. Moose (Code Review)]

Anon. E. Moose #1000171 has posted comments on this change.

Change subject: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back
..


Patch Set 4: Contrib-2

Analytics Compatibility Compilation Failed
https://goo.gl/2QdTaf : UNSTABLE

-- 
To view, visit https://asterix-gerrit.ics.uci.edu/2456
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: If8d5df630f1d9119002ef91da5c282da18901acc
Gerrit-PatchSet: 4
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Murtadha Hubail 
Gerrit-Reviewer: Anon. E. Moose #1000171
Gerrit-Reviewer: Ian Maxon 
Gerrit-Reviewer: Jenkins 
Gerrit-Reviewer: Luo Chen 
Gerrit-Reviewer: Michael Blow 
Gerrit-Reviewer: Murtadha Hubail 
Gerrit-Reviewer: Till Westmann 
Gerrit-Reviewer: abdullah alamoudi 
Gerrit-HasComments: No

Change in asterixdb[master]: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back

[Anon. E. Moose (Code Review)]

Anon. E. Moose #1000171 has posted comments on this change.

Change subject: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back
..


Patch Set 4: -Contrib

Analytics Compatibility Compilation Successful
https://goo.gl/L8NbqR : SUCCESS

-- 
To view, visit https://asterix-gerrit.ics.uci.edu/2456
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: If8d5df630f1d9119002ef91da5c282da18901acc
Gerrit-PatchSet: 4
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Murtadha Hubail 
Gerrit-Reviewer: Anon. E. Moose #1000171
Gerrit-Reviewer: Ian Maxon 
Gerrit-Reviewer: Jenkins 
Gerrit-Reviewer: Luo Chen 
Gerrit-Reviewer: Michael Blow 
Gerrit-Reviewer: Murtadha Hubail 
Gerrit-Reviewer: Till Westmann 
Gerrit-Reviewer: abdullah alamoudi 
Gerrit-HasComments: No

Change in asterixdb[master]: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back

[Jenkins (Code Review)]

Jenkins has posted comments on this change.

Change subject: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back
..


Patch Set 4:

Integration Tests Started 
https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-integration-tests/5880/

-- 
To view, visit https://asterix-gerrit.ics.uci.edu/2456
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: If8d5df630f1d9119002ef91da5c282da18901acc
Gerrit-PatchSet: 4
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Murtadha Hubail 
Gerrit-Reviewer: Anon. E. Moose #1000171
Gerrit-Reviewer: Ian Maxon 
Gerrit-Reviewer: Jenkins 
Gerrit-Reviewer: Luo Chen 
Gerrit-Reviewer: Michael Blow 
Gerrit-Reviewer: Murtadha Hubail 
Gerrit-Reviewer: Till Westmann 
Gerrit-Reviewer: abdullah alamoudi 
Gerrit-HasComments: No

Change in asterixdb[master]: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back

[Jenkins (Code Review)]

Jenkins has posted comments on this change.

Change subject: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back
..


Patch Set 4:

BAD Compatibility Tests Started 
https://asterix-jenkins.ics.uci.edu/job/asterixbad-compat/2851/

-- 
To view, visit https://asterix-gerrit.ics.uci.edu/2456
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: If8d5df630f1d9119002ef91da5c282da18901acc
Gerrit-PatchSet: 4
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Murtadha Hubail 
Gerrit-Reviewer: Anon. E. Moose #1000171
Gerrit-Reviewer: Ian Maxon 
Gerrit-Reviewer: Jenkins 
Gerrit-Reviewer: Luo Chen 
Gerrit-Reviewer: Michael Blow 
Gerrit-Reviewer: Murtadha Hubail 
Gerrit-Reviewer: Till Westmann 
Gerrit-Reviewer: abdullah alamoudi 
Gerrit-HasComments: No

Change in asterixdb[master]: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back

[Jenkins (Code Review)]

Jenkins has posted comments on this change.

Change subject: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back
..


Patch Set 4: Contrib-2

BAD Compatibility Tests Failed

https://asterix-jenkins.ics.uci.edu/job/asterixbad-compat/2851/ : FAILURE

-- 
To view, visit https://asterix-gerrit.ics.uci.edu/2456
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: If8d5df630f1d9119002ef91da5c282da18901acc
Gerrit-PatchSet: 4
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Murtadha Hubail 
Gerrit-Reviewer: Anon. E. Moose #1000171
Gerrit-Reviewer: Ian Maxon 
Gerrit-Reviewer: Jenkins 
Gerrit-Reviewer: Luo Chen 
Gerrit-Reviewer: Michael Blow 
Gerrit-Reviewer: Murtadha Hubail 
Gerrit-Reviewer: Till Westmann 
Gerrit-Reviewer: abdullah alamoudi 
Gerrit-HasComments: No

Change in asterixdb[master]: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back

[Anon. E. Moose (Code Review)]

Anon. E. Moose #1000171 has posted comments on this change.

Change subject: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back
..


Patch Set 4: Contrib-2

Analytics Compatibility Tests Failed
https://goo.gl/CVR9Xy : UNSTABLE

-- 
To view, visit https://asterix-gerrit.ics.uci.edu/2456
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: If8d5df630f1d9119002ef91da5c282da18901acc
Gerrit-PatchSet: 4
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Murtadha Hubail 
Gerrit-Reviewer: Anon. E. Moose #1000171
Gerrit-Reviewer: Ian Maxon 
Gerrit-Reviewer: Jenkins 
Gerrit-Reviewer: Luo Chen 
Gerrit-Reviewer: Michael Blow 
Gerrit-Reviewer: Murtadha Hubail 
Gerrit-Reviewer: Till Westmann 
Gerrit-Reviewer: abdullah alamoudi 
Gerrit-HasComments: No

Change in asterixdb[master]: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back

[Jenkins (Code Review)]

Jenkins has posted comments on this change.

Change subject: [NO ISSUE][TX] Ensure Uncommitted Atomic Txns Are Rolled back
..


Patch Set 4: Integration-Tests+1

Integration Tests Successful

https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-integration-tests/5880/ 
: SUCCESS

-- 
To view, visit https://asterix-gerrit.ics.uci.edu/2456
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: If8d5df630f1d9119002ef91da5c282da18901acc
Gerrit-PatchSet: 4
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Murtadha Hubail 
Gerrit-Reviewer: Anon. E. Moose #1000171
Gerrit-Reviewer: Ian Maxon 
Gerrit-Reviewer: Jenkins 
Gerrit-Reviewer: Luo Chen 
Gerrit-Reviewer: Michael Blow 
Gerrit-Reviewer: Murtadha Hubail 
Gerrit-Reviewer: Till Westmann 
Gerrit-Reviewer: abdullah alamoudi 
Gerrit-HasComments: No

Change in asterixdb[master]: [ASTERIXDB-1952][TX][IDX] Filter logs pt.2

[abdullah alamoudi (Code Review)]

abdullah alamoudi has posted comments on this change.

Change subject: [ASTERIXDB-1952][TX][IDX] Filter logs pt.2
..


Patch Set 40:

(1 comment)

https://asterix-gerrit.ics.uci.edu/#/c/1857/40/asterixdb/asterix-server/src/test/resources/transactionts/testsuite.xml
File asterixdb/asterix-server/src/test/resources/transactionts/testsuite.xml:

PS40, Line 123: https://asterix-gerrit.ics.uci.edu/1857
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: Ie9e7795d9c8c212e8610dcb9bb5d26ec9fbbee8a
Gerrit-PatchSet: 40
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Ian Maxon 
Gerrit-Reviewer: Anon. E. Moose #1000171
Gerrit-Reviewer: Ian Maxon 
Gerrit-Reviewer: Jenkins 
Gerrit-Reviewer: Murtadha Hubail 
Gerrit-Reviewer: abdullah alamoudi 
Gerrit-HasComments: Yes

Change in asterixdb[master]: [ASTERIXDB-1952][TX][IDX] Filter logs pt.2

[Ian Maxon (Code Review)]

Ian Maxon has posted comments on this change.

Change subject: [ASTERIXDB-1952][TX][IDX] Filter logs pt.2
..


Patch Set 40:

(1 comment)

https://asterix-gerrit.ics.uci.edu/#/c/1857/40/asterixdb/asterix-server/src/test/resources/transactionts/testsuite.xml
File asterixdb/asterix-server/src/test/resources/transactionts/testsuite.xml:

PS40, Line 123:  missing opening of test-case
Yeah I was going to fix this after your pass, I didn't see it until the 
integration tests caught it.


-- 
To view, visit https://asterix-gerrit.ics.uci.edu/1857
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: Ie9e7795d9c8c212e8610dcb9bb5d26ec9fbbee8a
Gerrit-PatchSet: 40
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Ian Maxon 
Gerrit-Reviewer: Anon. E. Moose #1000171
Gerrit-Reviewer: Ian Maxon 
Gerrit-Reviewer: Jenkins 
Gerrit-Reviewer: Murtadha Hubail 
Gerrit-Reviewer: abdullah alamoudi 
Gerrit-HasComments: Yes

[jira] [Created] (ASTERIXDB-2317) Intermittent Failure in Kill CC NCServiceExecutionIT

[Abdullah Alamoudi (JIRA)]

Abdullah Alamoudi created ASTERIXDB-2317:


 Summary: Intermittent Failure in Kill CC NCServiceExecutionIT
 Key: ASTERIXDB-2317
 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2317
 Project: Apache AsterixDB
  Issue Type: Bug
  Components: RT - Runtime
Reporter: Abdullah Alamoudi


java.lang.Exception: Cluster did not become ACTIVE within 30 seconds

Pinned run: 
https://asterix-jenkins.ics.uci.edu/job/asterix-integration-tests/org.apache.asterix$asterix-server/1152/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Change in asterixdb[master]: [NO ISSUE][CLUS] Fail Tasks When NC Not Active

[Michael Blow (Code Review)]

Michael Blow has posted comments on this change.

Change subject: [NO ISSUE][CLUS] Fail Tasks When NC Not Active
..


Patch Set 4:

(1 comment)

https://asterix-gerrit.ics.uci.edu/#/c/2460/4/hyracks-fullstack/hyracks/hyracks-control/hyracks-control-nc/src/main/java/org/apache/hyracks/control/nc/NodeControllerService.java
File 
hyracks-fullstack/hyracks/hyracks-control/hyracks-control-nc/src/main/java/org/apache/hyracks/control/nc/NodeControllerService.java:

PS4, Line 173: ACTIVE
why do we initialize to ACTIVE?


-- 
To view, visit https://asterix-gerrit.ics.uci.edu/2460
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: I447d4f1e255211e9026b68eb9d931f25846ed153
Gerrit-PatchSet: 4
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Murtadha Hubail 
Gerrit-Reviewer: Anon. E. Moose #1000171
Gerrit-Reviewer: Jenkins 
Gerrit-Reviewer: Michael Blow 
Gerrit-Reviewer: Till Westmann 
Gerrit-Reviewer: abdullah alamoudi 
Gerrit-HasComments: Yes

Change in asterixdb[master]: [ASTERIXDB-1280][TEST] JUnit cleanup

[Michael Blow (Code Review)]

Michael Blow has posted comments on this change.

Change subject: [ASTERIXDB-1280][TEST] JUnit cleanup
..


Patch Set 2: Code-Review+2

-- 
To view, visit https://asterix-gerrit.ics.uci.edu/2461
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: I2a57643682d45097ae5ac4adc1fe97fbb3111385
Gerrit-PatchSet: 2
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Till Westmann 
Gerrit-Reviewer: Anon. E. Moose #1000171
Gerrit-Reviewer: Jenkins 
Gerrit-Reviewer: Michael Blow 
Gerrit-HasComments: No

Change in asterixdb[master]: [NO ISSUE][CLUS] Fail Tasks When NC Not Active

[Murtadha Hubail (Code Review)]

Murtadha Hubail has posted comments on this change.

Change subject: [NO ISSUE][CLUS] Fail Tasks When NC Not Active
..


Patch Set 4:

(1 comment)

https://asterix-gerrit.ics.uci.edu/#/c/2460/4/hyracks-fullstack/hyracks/hyracks-control/hyracks-control-nc/src/main/java/org/apache/hyracks/control/nc/NodeControllerService.java
File 
hyracks-fullstack/hyracks/hyracks-control/hyracks-control-nc/src/main/java/org/apache/hyracks/control/nc/NodeControllerService.java:

PS4, Line 173: ACTIVE
> why do we initialize to ACTIVE?
other Hyracks tests and customers wont be able to start any tasks unless they 
change their applications to set this to active. I had it in earlier patches 
initialized to idle and many Hyracks tests failed.


-- 
To view, visit https://asterix-gerrit.ics.uci.edu/2460
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: I447d4f1e255211e9026b68eb9d931f25846ed153
Gerrit-PatchSet: 4
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Murtadha Hubail 
Gerrit-Reviewer: Anon. E. Moose #1000171
Gerrit-Reviewer: Jenkins 
Gerrit-Reviewer: Michael Blow 
Gerrit-Reviewer: Murtadha Hubail 
Gerrit-Reviewer: Till Westmann 
Gerrit-Reviewer: abdullah alamoudi 
Gerrit-HasComments: Yes

Change in asterixdb[master]: [NO ISSUE][CLUS] Fail Tasks When NC Not Active

[Michael Blow (Code Review)]

Michael Blow has posted comments on this change.

Change subject: [NO ISSUE][CLUS] Fail Tasks When NC Not Active
..


Patch Set 4: Code-Review+2

-- 
To view, visit https://asterix-gerrit.ics.uci.edu/2460
To unsubscribe, visit https://asterix-gerrit.ics.uci.edu/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: I447d4f1e255211e9026b68eb9d931f25846ed153
Gerrit-PatchSet: 4
Gerrit-Project: asterixdb
Gerrit-Branch: master
Gerrit-Owner: Murtadha Hubail 
Gerrit-Reviewer: Anon. E. Moose #1000171
Gerrit-Reviewer: Jenkins 
Gerrit-Reviewer: Michael Blow 
Gerrit-Reviewer: Murtadha Hubail 
Gerrit-Reviewer: Till Westmann 
Gerrit-Reviewer: abdullah alamoudi 
Gerrit-HasComments: No

Change in asterixdb[master]: [NO ISSUE][CLUS] Fail Tasks When NC Not Active

[Murtadha Hubail (Code Review)]

Murtadha Hubail has submitted this change and it was merged.

Change subject: [NO ISSUE][CLUS] Fail Tasks When NC Not Active
..


[NO ISSUE][CLUS] Fail Tasks When NC Not Active

- user model changes: no
- storage format changes: no
- interface changes: no

Details:
- Fail StartTasksWork if NC is not in active
  state (i.e. hasn't completed startup tasks).
- Set NC state to active only after completing
  startup tasks.
- Add test case.

Change-Id: I447d4f1e255211e9026b68eb9d931f25846ed153
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2460
Sonar-Qube: Jenkins 
Tested-by: Jenkins 
Contrib: Jenkins 
Integration-Tests: Jenkins 
Reviewed-by: Michael Blow 
---
M 
asterixdb/asterix-app/src/main/java/org/apache/asterix/app/replication/NcLifecycleCoordinator.java
M 
asterixdb/asterix-app/src/main/java/org/apache/asterix/hyracks/bootstrap/NCApplication.java
A 
asterixdb/asterix-app/src/test/java/org/apache/asterix/runtime/NcLifecycleTest.java
M 
hyracks-fullstack/hyracks/hyracks-api/src/main/java/org/apache/hyracks/api/client/NodeStatus.java
M 
hyracks-fullstack/hyracks/hyracks-api/src/main/java/org/apache/hyracks/api/exceptions/ErrorCode.java
M 
hyracks-fullstack/hyracks/hyracks-api/src/main/resources/errormsg/en.properties
M 
hyracks-fullstack/hyracks/hyracks-control/hyracks-control-nc/src/main/java/org/apache/hyracks/control/nc/NodeControllerService.java
M 
hyracks-fullstack/hyracks/hyracks-control/hyracks-control-nc/src/main/java/org/apache/hyracks/control/nc/work/StartTasksWork.java
8 files changed, 83 insertions(+), 8 deletions(-)

Approvals:
  Anon. E. Moose #1000171: 
  Jenkins: Verified; No violations found; ; Verified
  Michael Blow: Looks good to me, approved



diff --git 
a/asterixdb/asterix-app/src/main/java/org/apache/asterix/app/replication/NcLifecycleCoordinator.java
 
b/asterixdb/asterix-app/src/main/java/org/apache/asterix/app/replication/NcLifecycleCoordinator.java
index 844851a..5c497aa 100644
--- 
a/asterixdb/asterix-app/src/main/java/org/apache/asterix/app/replication/NcLifecycleCoordinator.java
+++ 
b/asterixdb/asterix-app/src/main/java/org/apache/asterix/app/replication/NcLifecycleCoordinator.java
@@ -146,7 +146,7 @@
 return buildActiveNCRegTasks(isMetadataNode);
 }
 final List tasks = new ArrayList<>();
-tasks.add(new UpdateNodeStatusTask(NodeStatus.ACTIVE));
+tasks.add(new UpdateNodeStatusTask(NodeStatus.BOOTING));
 if (state == SystemState.CORRUPTED) {
 //need to perform local recovery for node partitions
 LocalRecoveryTask rt = new 
LocalRecoveryTask(Arrays.asList(clusterManager.getNodePartitions(nodeId))
@@ -167,6 +167,7 @@
 tasks.add(new BindMetadataNodeTask());
 }
 tasks.add(new ReportLocalCountersTask());
+tasks.add(new UpdateNodeStatusTask(NodeStatus.ACTIVE));
 return tasks;
 }
 
diff --git 
a/asterixdb/asterix-app/src/main/java/org/apache/asterix/hyracks/bootstrap/NCApplication.java
 
b/asterixdb/asterix-app/src/main/java/org/apache/asterix/hyracks/bootstrap/NCApplication.java
index 0cd01ae..494198b 100644
--- 
a/asterixdb/asterix-app/src/main/java/org/apache/asterix/hyracks/bootstrap/NCApplication.java
+++ 
b/asterixdb/asterix-app/src/main/java/org/apache/asterix/hyracks/bootstrap/NCApplication.java
@@ -89,6 +89,8 @@
 @Override
 public void init(IServiceContext serviceCtx) throws Exception {
 ncServiceCtx = (INCServiceContext) serviceCtx;
+// set the node status initially to idle to indicate that it is 
pending booting
+((NodeControllerService) 
serviceCtx.getControllerService()).setNodeStatus(NodeStatus.IDLE);
 ncServiceCtx.setThreadFactory(
 new AsterixThreadFactory(ncServiceCtx.getThreadFactory(), 
ncServiceCtx.getLifeCycleComponentManager()));
 }
@@ -253,7 +255,7 @@
 }
 
 private boolean isPendingStartupTasks(NodeStatus nodeStatus, CcId 
primaryCc, CcId registeredCc) {
-return nodeStatus == NodeStatus.BOOTING && (primaryCc == null || 
primaryCc.equals(registeredCc));
+return nodeStatus == NodeStatus.IDLE && (primaryCc == null || 
primaryCc.equals(registeredCc));
 }
 
 private SystemState getCurrentSystemState() {
diff --git 
a/asterixdb/asterix-app/src/test/java/org/apache/asterix/runtime/NcLifecycleTest.java
 
b/asterixdb/asterix-app/src/test/java/org/apache/asterix/runtime/NcLifecycleTest.java
new file mode 100644
index 000..df0740b
--- /dev/null
+++ 
b/asterixdb/asterix-app/src/test/java/org/apache/asterix/runtime/NcLifecycleTest.java
@@ -0,0 +1,64 @@
+/*
+ *  Licensed to the Apache Software Foundation (ASF) under one
+ *  or more contributor license agreements.  See the NOTICE file
+ *  distributed with this work for additional information
+ *  regarding copyright ownership.  The ASF licenses this file
+ *  to you under the Apache License, Version 2.0 (the
+ *  "License"); you may not use 

[jira] [Assigned] (ASTERIXDB-2317) Intermittent Failure in Kill CC NCServiceExecutionIT

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till reassigned ASTERIXDB-2317:
---

Assignee: Michael Blow

> Intermittent Failure in Kill CC NCServiceExecutionIT
> 
>
> Key: ASTERIXDB-2317
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2317
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: RT - Runtime
>Reporter: Abdullah Alamoudi
>Assignee: Michael Blow
>Priority: Major
>
> java.lang.Exception: Cluster did not become ACTIVE within 30 seconds
> Pinned run: 
> https://asterix-jenkins.ics.uci.edu/job/asterix-integration-tests/org.apache.asterix$asterix-server/1152/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2317) Intermittent Failure in Kill CC NCServiceExecutionIT

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2317:

Priority: Minor  (was: Major)

> Intermittent Failure in Kill CC NCServiceExecutionIT
> 
>
> Key: ASTERIXDB-2317
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2317
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: RT - Runtime
>Reporter: Abdullah Alamoudi
>Assignee: Michael Blow
>Priority: Minor
>
> java.lang.Exception: Cluster did not become ACTIVE within 30 seconds
> Pinned run: 
> https://asterix-jenkins.ics.uci.edu/job/asterix-integration-tests/org.apache.asterix$asterix-server/1152/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2317) Intermittent Failure in Kill CC NCServiceExecutionIT

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2317:

Labels: intermittent triaged  (was: )

> Intermittent Failure in Kill CC NCServiceExecutionIT
> 
>
> Key: ASTERIXDB-2317
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2317
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: RT - Runtime
>Reporter: Abdullah Alamoudi
>Assignee: Michael Blow
>Priority: Minor
>  Labels: intermittent, triaged
>
> java.lang.Exception: Cluster did not become ACTIVE within 30 seconds
> Pinned run: 
> https://asterix-jenkins.ics.uci.edu/job/asterix-integration-tests/org.apache.asterix$asterix-server/1152/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2316) NPE on Dataset Full Merge

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2316:

Priority: Critical  (was: Major)

> NPE on Dataset Full Merge
> -
>
> Key: ASTERIXDB-2316
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2316
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: STO - Storage
>Reporter: Murtadha Hubail
>Assignee: Murtadha Hubail
>Priority: Critical
>
> To reproduce run:
> {code:java}
> create type a as {id:int};
> compact dataset Metadata.`Datatype`;
> {code}
> Stack trace:
> {code:java}
> java.lang.NullPointerException: null
> at 
> org.apache.hyracks.storage.am.lsm.common.util.LSMComponentIdUtils.persist(LSMComponentIdUtils.java:52)
>  ~[classes/:?]
> at 
> org.apache.asterix.common.ioopcallbacks.AbstractLSMIOOperationCallback.putComponentIdIntoMetadata(AbstractLSMIOOperationCallback.java:198)
>  ~[classes/:?]
> at 
> org.apache.asterix.common.ioopcallbacks.AbstractLSMIOOperationCallback.afterOperation(AbstractLSMIOOperationCallback.java:122)
>  ~[classes/:?]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMHarness.merge(LSMHarness.java:639)
>  [classes/:?]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMTreeIndexAccessor.merge(LSMTreeIndexAccessor.java:128)
>  [classes/:?]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.MergeOperation.call(MergeOperation.java:45)
>  [classes/:?]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.MergeOperation.call(MergeOperation.java:30)
>  [classes/:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_151]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  [?:1.8.0_151]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  [?:1.8.0_151]
> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_151]
> {code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2316) NPE on Dataset Full Merge

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2316:

Labels: triaged  (was: )

> NPE on Dataset Full Merge
> -
>
> Key: ASTERIXDB-2316
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2316
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: STO - Storage
>Reporter: Murtadha Hubail
>Assignee: Murtadha Hubail
>Priority: Critical
>  Labels: triaged
>
> To reproduce run:
> {code:java}
> create type a as {id:int};
> compact dataset Metadata.`Datatype`;
> {code}
> Stack trace:
> {code:java}
> java.lang.NullPointerException: null
> at 
> org.apache.hyracks.storage.am.lsm.common.util.LSMComponentIdUtils.persist(LSMComponentIdUtils.java:52)
>  ~[classes/:?]
> at 
> org.apache.asterix.common.ioopcallbacks.AbstractLSMIOOperationCallback.putComponentIdIntoMetadata(AbstractLSMIOOperationCallback.java:198)
>  ~[classes/:?]
> at 
> org.apache.asterix.common.ioopcallbacks.AbstractLSMIOOperationCallback.afterOperation(AbstractLSMIOOperationCallback.java:122)
>  ~[classes/:?]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMHarness.merge(LSMHarness.java:639)
>  [classes/:?]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMTreeIndexAccessor.merge(LSMTreeIndexAccessor.java:128)
>  [classes/:?]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.MergeOperation.call(MergeOperation.java:45)
>  [classes/:?]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.MergeOperation.call(MergeOperation.java:30)
>  [classes/:?]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_151]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  [?:1.8.0_151]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  [?:1.8.0_151]
> at java.lang.Thread.run(Thread.java:748) [?:1.8.0_151]
> {code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2314) Dataset appears in class names in Hyracks and is confusing

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2314:

Labels: triaged  (was: )

> Dataset appears in class names in Hyracks and is confusing
> --
>
> Key: ASTERIXDB-2314
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2314
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: RT - Runtime
>Reporter: Abdullah Alamoudi
>Assignee: Till
>Priority: Minor
>  Labels: triaged
>
> Dataset appears frequently in Hyracks in the result distribution context.
> They should be renamed as [Dataset] -> [Result]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2315) HttpClient is not closed at the end of each use in TestExecutor

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2315:

Priority: Minor  (was: Major)

> HttpClient is not closed at the end of each use in TestExecutor
> ---
>
> Key: ASTERIXDB-2315
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2315
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: TEST - Test Framework
>Reporter: Abdullah Alamoudi
>Assignee: Abdullah Alamoudi
>Priority: Minor
>  Labels: triaged
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2314) Dataset appears in class names in Hyracks and is confusing

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2314:

Priority: Minor  (was: Major)

> Dataset appears in class names in Hyracks and is confusing
> --
>
> Key: ASTERIXDB-2314
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2314
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: RT - Runtime
>Reporter: Abdullah Alamoudi
>Assignee: Till
>Priority: Minor
>  Labels: triaged
>
> Dataset appears frequently in Hyracks in the result distribution context.
> They should be renamed as [Dataset] -> [Result]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2315) HttpClient is not closed at the end of each use in TestExecutor

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2315:

Labels: triaged  (was: )

> HttpClient is not closed at the end of each use in TestExecutor
> ---
>
> Key: ASTERIXDB-2315
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2315
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: TEST - Test Framework
>Reporter: Abdullah Alamoudi
>Assignee: Abdullah Alamoudi
>Priority: Minor
>  Labels: triaged
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ASTERIXDB-1812) OutofMemoryError when group by on a non-existing field with 300k records (tweets)

[Michael Blow (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Blow reassigned ASTERIXDB-1812:
---

Assignee: (was: Yingyi Bu)

> OutofMemoryError when group by on a non-existing field with 300k records 
> (tweets)
> -
>
> Key: ASTERIXDB-1812
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1812
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: *DB - AsterixDB, HYR - Hyracks
> Environment: Linux 16.04
> Asterix 0.9.0 with 2 nc nodes and 1 cc node. (all using default 
> configurations from 
> https://asterixdb.apache.org/docs/0.9.0/install.html#Section1SingleMachineAsterixDBInstallation)
>Reporter: Chen Luo
>Priority: Major
>
> The dataset is a sample tweet dataset provided by Cloudberry, which contains 
> 324000 tweets (about 300M). When issuing the following query, I always get an 
> OutofMemoryError.
> Query:
> {code}
> select * from twitter.ds_tweet t
> group by t.test;
> {code}
> Stacktrace:
> {code}
> org.apache.hyracks.api.exceptions.HyracksException: Job failed on account of:
> HYR0003: java.lang.OutOfMemoryError: Java heap space
>   at 
> org.apache.hyracks.control.cc.job.JobRun.waitForCompletion(JobRun.java:211)
>   at 
> org.apache.hyracks.control.cc.work.WaitForJobCompletionWork$1.run(WaitForJobCompletionWork.java:48)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: org.apache.hyracks.api.exceptions.HyracksDataException: HYR0003: 
> java.lang.OutOfMemoryError: Java heap space
>   at 
> org.apache.hyracks.control.common.utils.ExceptionUtils.setNodeIds(ExceptionUtils.java:62)
>   at org.apache.hyracks.control.nc.Task.run(Task.java:330)
>   ... 3 more
> Caused by: org.apache.hyracks.api.exceptions.HyracksDataException: 
> java.lang.OutOfMemoryError: Java heap space
>   at 
> org.apache.hyracks.api.rewriter.runtime.SuperActivityOperatorNodePushable.runInParallel(SuperActivityOperatorNodePushable.java:228)
>   at 
> org.apache.hyracks.api.rewriter.runtime.SuperActivityOperatorNodePushable.initialize(SuperActivityOperatorNodePushable.java:84)
>   at org.apache.hyracks.control.nc.Task.run(Task.java:273)
>   ... 3 more
> Caused by: java.util.concurrent.ExecutionException: 
> java.lang.OutOfMemoryError: Java heap space
>   at java.util.concurrent.FutureTask.report(FutureTask.java:122)
>   at java.util.concurrent.FutureTask.get(FutureTask.java:192)
>   at 
> org.apache.hyracks.api.rewriter.runtime.SuperActivityOperatorNodePushable.runInParallel(SuperActivityOperatorNodePushable.java:222)
>   ... 5 more
> Caused by: java.lang.OutOfMemoryError: Java heap space
>   at java.nio.HeapByteBuffer.(HeapByteBuffer.java:57)
>   at java.nio.ByteBuffer.allocate(ByteBuffer.java:335)
>   at 
> org.apache.hyracks.control.nc.resources.memory.FrameManager.allocateFrame(FrameManager.java:57)
>   at 
> org.apache.hyracks.control.nc.resources.memory.FrameManager.reallocateFrame(FrameManager.java:73)
>   at org.apache.hyracks.control.nc.Joblet.reallocateFrame(Joblet.java:242)
>   at org.apache.hyracks.control.nc.Task.reallocateFrame(Task.java:136)
>   at 
> org.apache.hyracks.api.comm.VSizeFrame.ensureFrameSize(VSizeFrame.java:53)
>   at 
> org.apache.hyracks.dataflow.common.comm.io.AbstractFrameAppender.canHoldNewTuple(AbstractFrameAppender.java:104)
>   at 
> org.apache.hyracks.dataflow.common.comm.io.FrameTupleAppender.append(FrameTupleAppender.java:49)
>   at 
> org.apache.hyracks.dataflow.common.comm.util.FrameUtils.appendToWriter(FrameUtils.java:159)
>   at 
> org.apache.hyracks.algebricks.runtime.operators.base.AbstractOneInputOneOutputOneFramePushRuntime.appendToFrameFromTupleBuilder(AbstractOneInputOneOutputOneFramePushRuntime.java:82)
>   at 
> org.apache.hyracks.algebricks.runtime.operators.base.AbstractOneInputOneOutputOneFramePushRuntime.appendToFrameFromTupleBuilder(AbstractOneInputOneOutputOneFramePushRuntime.java:78)
>   at 
> org.apache.hyracks.algebricks.runtime.operators.std.AssignRuntimeFactory$1.nextFrame(AssignRuntimeFactory.java:150)
>   at 
> org.apache.hyracks.algebricks.runtime.operators.meta.AlgebricksMetaOperatorDescriptor$2.nextFrame(AlgebricksMetaOperatorDescriptor.java:134)
>   at 
> org.apache.hyracks.dataflow.common.comm.io.AbstractFrameAppender.write(AbstractFrameAppender.java:92)
>   at 
> org.apache.hyracks.dataflow.common.comm.io.FrameTupleAppenderWrapper.write(FrameTupleAppenderWrapper.java:50)
>   at 
> org.apache.hyracks.dataflow.std.group.preclustered.PreclusteredGro

[jira] [Updated] (ASTERIXDB-2311) After restart, "Failed to redo" exception was generated.

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2311:

Component/s: TX - Transactions

> After restart, "Failed to redo" exception was generated.
> 
>
> Key: ASTERIXDB-2311
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2311
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: TX - Transactions
>Reporter: Taewoo Kim
>Assignee: Ian Maxon
>Priority: Critical
> Attachments: nc-4.log
>
>
> During the realtime tweet ingestion process of Cloudberry, I found an issue 
> on the application that feeds a tweet to AsterixDB, I stopped that process. 
> Also, I stopped the feed itself and started the Cloudberry instance and saw 
> the following error message.
> {code:java}
> 21:58:33.129 [Executor-6:4] ERROR 
> org.apache.asterix.app.replication.message.RegistrationTasksResponseMessage - 
> Failed during startup task
> java.lang.IllegalStateException: Failed to redo
> at org.apache.asterix.app.nc.RecoveryManager.redo(RecoveryManager.java:784) 
> ~[asterix-app-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
> at 
> org.apache.asterix.app.nc.RecoveryManager.startRecoveryRedoPhase(RecoveryManager.java:368)
>  ~[asterix-app-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
> at 
> org.apache.asterix.app.nc.RecoveryManager.replayPartitionsLogs(RecoveryManager.java:178)
>  ~[asterix-app-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
> at 
> org.apache.asterix.app.nc.RecoveryManager.startLocalRecovery(RecoveryManager.java:170)
>  ~[asterix-app-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
> at 
> org.apache.asterix.app.nc.task.LocalRecoveryTask.perform(LocalRecoveryTask.java:45)
>  ~[asterix-app-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
> at 
> org.apache.asterix.app.replication.message.RegistrationTasksResponseMessage.handle(RegistrationTasksResponseMessage.java:62)
>  [asterix-app-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
> at 
> org.apache.asterix.messaging.NCMessageBroker.lambda$receivedMessage$3(NCMessageBroker.java:100)
>  [asterix-app-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
> at 
> org.apache.asterix.messaging.NCMessageBroker$$Lambda$70/727538728.run(Unknown 
> Source) [asterix-app-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [?:1.8.0]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [?:1.8.0]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [?:1.8.0]
> at java.lang.Thread.run(Thread.java:744) [?:1.8.0]
> Caused by: org.apache.hyracks.api.exceptions.HyracksDataException: HYR0033: 
> Inserting duplicate keys into the primary storage
> at 
> org.apache.hyracks.api.exceptions.HyracksDataException.create(HyracksDataException.java:55)
>  ~[hyracks-api-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.btree.impls.LSMBTree.insert(LSMBTree.java:213)
>  ~[hyracks-storage-am-lsm-btree-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.btree.impls.LSMBTree.modify(LSMBTree.java:164)
>  ~[hyracks-storage-am-lsm-btree-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMHarness.modify(LSMHarness.java:482)
>  ~[hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMHarness.forceModify(LSMHarness.java:422)
>  ~[hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMTreeIndexAccessor.forceInsert(LSMTreeIndexAccessor.java:176)
>  ~[hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at org.apache.asterix.app.nc.RecoveryManager.redo(RecoveryManager.java:774) 
> ~[asterix-app-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
> ... 12 more{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2311) After restart, "Failed to redo" exception was generated.

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2311:

Priority: Critical  (was: Major)

> After restart, "Failed to redo" exception was generated.
> 
>
> Key: ASTERIXDB-2311
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2311
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: TX - Transactions
>Reporter: Taewoo Kim
>Assignee: Ian Maxon
>Priority: Critical
> Attachments: nc-4.log
>
>
> During the realtime tweet ingestion process of Cloudberry, I found an issue 
> on the application that feeds a tweet to AsterixDB, I stopped that process. 
> Also, I stopped the feed itself and started the Cloudberry instance and saw 
> the following error message.
> {code:java}
> 21:58:33.129 [Executor-6:4] ERROR 
> org.apache.asterix.app.replication.message.RegistrationTasksResponseMessage - 
> Failed during startup task
> java.lang.IllegalStateException: Failed to redo
> at org.apache.asterix.app.nc.RecoveryManager.redo(RecoveryManager.java:784) 
> ~[asterix-app-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
> at 
> org.apache.asterix.app.nc.RecoveryManager.startRecoveryRedoPhase(RecoveryManager.java:368)
>  ~[asterix-app-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
> at 
> org.apache.asterix.app.nc.RecoveryManager.replayPartitionsLogs(RecoveryManager.java:178)
>  ~[asterix-app-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
> at 
> org.apache.asterix.app.nc.RecoveryManager.startLocalRecovery(RecoveryManager.java:170)
>  ~[asterix-app-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
> at 
> org.apache.asterix.app.nc.task.LocalRecoveryTask.perform(LocalRecoveryTask.java:45)
>  ~[asterix-app-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
> at 
> org.apache.asterix.app.replication.message.RegistrationTasksResponseMessage.handle(RegistrationTasksResponseMessage.java:62)
>  [asterix-app-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
> at 
> org.apache.asterix.messaging.NCMessageBroker.lambda$receivedMessage$3(NCMessageBroker.java:100)
>  [asterix-app-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
> at 
> org.apache.asterix.messaging.NCMessageBroker$$Lambda$70/727538728.run(Unknown 
> Source) [asterix-app-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [?:1.8.0]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [?:1.8.0]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [?:1.8.0]
> at java.lang.Thread.run(Thread.java:744) [?:1.8.0]
> Caused by: org.apache.hyracks.api.exceptions.HyracksDataException: HYR0033: 
> Inserting duplicate keys into the primary storage
> at 
> org.apache.hyracks.api.exceptions.HyracksDataException.create(HyracksDataException.java:55)
>  ~[hyracks-api-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.btree.impls.LSMBTree.insert(LSMBTree.java:213)
>  ~[hyracks-storage-am-lsm-btree-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.btree.impls.LSMBTree.modify(LSMBTree.java:164)
>  ~[hyracks-storage-am-lsm-btree-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMHarness.modify(LSMHarness.java:482)
>  ~[hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMHarness.forceModify(LSMHarness.java:422)
>  ~[hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMTreeIndexAccessor.forceInsert(LSMTreeIndexAccessor.java:176)
>  ~[hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at org.apache.asterix.app.nc.RecoveryManager.redo(RecoveryManager.java:774) 
> ~[asterix-app-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
> ... 12 more{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ASTERIXDB-2312) JsonLogicalPlanPrinter does not handle Upsert properly

[Till (JIRA)]

[ 
https://issues.apache.org/jira/browse/ASTERIXDB-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391972#comment-16391972
 ] 

Till commented on ASTERIXDB-2312:
-

[~luochen01], could you add a description?

> JsonLogicalPlanPrinter does not handle Upsert properly
> --
>
> Key: ASTERIXDB-2312
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2312
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: COMP - Compiler
>Reporter: Chen Luo
>Assignee: Chen Luo
>Priority: Minor
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2311) After restart, "Failed to redo" exception was generated.

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2311:

Labels: triaged  (was: )

> After restart, "Failed to redo" exception was generated.
> 
>
> Key: ASTERIXDB-2311
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2311
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: TX - Transactions
>Reporter: Taewoo Kim
>Assignee: Ian Maxon
>Priority: Critical
>  Labels: triaged
> Attachments: nc-4.log
>
>
> During the realtime tweet ingestion process of Cloudberry, I found an issue 
> on the application that feeds a tweet to AsterixDB, I stopped that process. 
> Also, I stopped the feed itself and started the Cloudberry instance and saw 
> the following error message.
> {code:java}
> 21:58:33.129 [Executor-6:4] ERROR 
> org.apache.asterix.app.replication.message.RegistrationTasksResponseMessage - 
> Failed during startup task
> java.lang.IllegalStateException: Failed to redo
> at org.apache.asterix.app.nc.RecoveryManager.redo(RecoveryManager.java:784) 
> ~[asterix-app-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
> at 
> org.apache.asterix.app.nc.RecoveryManager.startRecoveryRedoPhase(RecoveryManager.java:368)
>  ~[asterix-app-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
> at 
> org.apache.asterix.app.nc.RecoveryManager.replayPartitionsLogs(RecoveryManager.java:178)
>  ~[asterix-app-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
> at 
> org.apache.asterix.app.nc.RecoveryManager.startLocalRecovery(RecoveryManager.java:170)
>  ~[asterix-app-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
> at 
> org.apache.asterix.app.nc.task.LocalRecoveryTask.perform(LocalRecoveryTask.java:45)
>  ~[asterix-app-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
> at 
> org.apache.asterix.app.replication.message.RegistrationTasksResponseMessage.handle(RegistrationTasksResponseMessage.java:62)
>  [asterix-app-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
> at 
> org.apache.asterix.messaging.NCMessageBroker.lambda$receivedMessage$3(NCMessageBroker.java:100)
>  [asterix-app-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
> at 
> org.apache.asterix.messaging.NCMessageBroker$$Lambda$70/727538728.run(Unknown 
> Source) [asterix-app-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
> [?:1.8.0]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [?:1.8.0]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [?:1.8.0]
> at java.lang.Thread.run(Thread.java:744) [?:1.8.0]
> Caused by: org.apache.hyracks.api.exceptions.HyracksDataException: HYR0033: 
> Inserting duplicate keys into the primary storage
> at 
> org.apache.hyracks.api.exceptions.HyracksDataException.create(HyracksDataException.java:55)
>  ~[hyracks-api-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.btree.impls.LSMBTree.insert(LSMBTree.java:213)
>  ~[hyracks-storage-am-lsm-btree-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.btree.impls.LSMBTree.modify(LSMBTree.java:164)
>  ~[hyracks-storage-am-lsm-btree-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMHarness.modify(LSMHarness.java:482)
>  ~[hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMHarness.forceModify(LSMHarness.java:422)
>  ~[hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMTreeIndexAccessor.forceInsert(LSMTreeIndexAccessor.java:176)
>  ~[hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at org.apache.asterix.app.nc.RecoveryManager.redo(RecoveryManager.java:774) 
> ~[asterix-app-0.9.4-SNAPSHOT.jar:0.9.4-SNAPSHOT]
> ... 12 more{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ASTERIXDB-2310) Use Primary Key Index to Enforce Insert Key Uniqueness

[Till (JIRA)]

[ 
https://issues.apache.org/jira/browse/ASTERIXDB-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391986#comment-16391986
 ] 

Till commented on ASTERIXDB-2310:
-

Will this be used only if the user has created a primary key index or should 
the primary key index *always* be created by the system to support this?

> Use Primary Key Index to Enforce Insert Key Uniqueness
> --
>
> Key: ASTERIXDB-2310
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2310
> Project: Apache AsterixDB
>  Issue Type: Improvement
>  Components: ING - Ingestion, STO - Storage
>Reporter: Chen Luo
>Assignee: Chen Luo
>Priority: Major
>
> **Currently when ingesting data using INSERT operations, we always check the 
> primary index to ensure key uniqueness. However, this implies in most cases 
> all ingested records might be accessed, which will slow down the ingestion 
> performance a lot when the records cannot be cached. To handle this, we can 
> enforce key uniqueness by checking the primary key index, which is much 
> smaller and can be more easily cached.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ASTERIXDB-2308) fileMapManager in VirtualBufferCache is not cleared after index drop

[Till (JIRA)]

[ 
https://issues.apache.org/jira/browse/ASTERIXDB-2308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391990#comment-16391990
 ] 

Till commented on ASTERIXDB-2308:
-

[~sjaco002]: Are there logs from your experiments that could help with the 
analysis?

> fileMapManager in VirtualBufferCache is not cleared after index drop
> 
>
> Key: ASTERIXDB-2308
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2308
> Project: Apache AsterixDB
>  Issue Type: Bug
>Reporter: Xikui Wang
>Assignee: Chen Luo
>Priority: Major
>
> This causes duplicated mapping and eventually causes feed hangs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2306) Inverted list file is not deleted after an inverted index component merge operation

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2306:

Labels: triaged  (was: )

> Inverted list file is not deleted after an inverted index component merge 
> operation
> ---
>
> Key: ASTERIXDB-2306
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2306
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: IDX - Indexes, STO - Storage
>Reporter: Taewoo Kim
>Assignee: Taewoo Kim
>Priority: Major
>  Labels: triaged
>
> After the following exception, an inverted list file of an old component was 
> not deleted. This was happened during an ingestion of 1 Billion tweets on a 
> Cloudberry cluster with five nodes.
> {code:java}
> 23:15:15.269 [Executor-6082:5] WARN 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMHarness - Failure 
> scheduling replication or destroying merged component
> java.lang.IllegalStateException: Page 20629:2 is pinned and file is being 
> closed. Pincount is: 1 Page is confiscated: false
> at 
> org.apache.hyracks.storage.common.buffercache.BufferCache.invalidateIfFileIdMatch(BufferCache.java:930)
>  ~[hyracks-storage-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.common.buffercache.BufferCache.sweepAndFlush(BufferCache.java:904)
>  ~[hyracks-storage-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.common.buffercache.BufferCache.deleteFile(BufferCache.java:997)
>  ~[hyracks-storage-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.common.buffercache.BufferCache.deleteFile(BufferCache.java:983)
>  ~[hyracks-storage-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.invertedindex.ondisk.OnDiskInvertedIndex.destroy(OnDiskInvertedIndex.java:170)
>  ~[hyracks-storage-am-lsm-invertedindex-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.AbstractLSMDiskComponent.deactivateAndDestroy(AbstractLSMDiskComponent.java:166)
>  ~[hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.api.AbstractLSMWithBloomFilterDiskComponent.deactivateAndDestroy(AbstractLSMWithBloomFilterDiskComponent.java:63)
>  ~[hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.api.AbstractLSMWithBuddyDiskComponent.deactivateAndDestroy(AbstractLSMWithBuddyDiskComponent.java:56)
>  ~[hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMHarness.doExitComponents(LSMHarness.java:324)
>  [hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMHarness.exitComponents(LSMHarness.java:411)
>  [hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMHarness.merge(LSMHarness.java:639)
>  [hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.invertedindex.impls.LSMInvertedIndexAccessor.merge(LSMInvertedIndexAccessor.java:125)
>  [hyracks-storage-am-lsm-invertedindex-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.MergeOperation.call(MergeOperation.java:45)
>  [hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.MergeOperation.call(MergeOperation.java:30)
>  [hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [?:1.8.0]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [?:1.8.0]
> at java.lang.Thread.run(Thread.java:744) [?:1.8.0]{code}
>  
> The directory:
> {code:java}
> -rw-r--r-- 1 waans11 waans11 262160 Feb 27 13:13 
> 2018-02-27-13-12-52-923_2018-02-27-12-45-21-400_d
> -rw-r--r-- 1 waans11 waans11 0 Feb 27 13:12 
> 2018-02-27-13-12-52-923_2018-02-27-12-45-21-400_f
> -rw-r--r-- 1 waans11 waans11 76288560 Feb 27 13:13 
> 2018-02-27-13-12-52-923_2018-02-27-12-45-21-400_i
> -rw-r--r-- 1 waans11 waans11 262160 Feb 27 13:15 
> 2018-02-27-13-15-21-671_2018-02-27-13-15-21-671_d
> -rw-r--r-- 1 waans11 waans11 0 Feb 27 13:15 
> 2018-02-27-13-15-21-671_2018-02-27-13-15-21-671_f
> -rw-r--r-- 1 waans11 waans11 2097280 Feb 27 13:15 
> 2018-02-27-13-15-21-671_2018-02-27-13-15-21-671_i
> -rw-r--r-- 1 waans11 waans11 43256400 Feb 27 23:15 
> 2018-02-27-23-14-41-965_2018-02-27-12-45-21-400_b
> -rw-r--r-- 1 waans11 waans11 262160 Feb 27 23:15 
> 2018-02-27-23-14-41-

[jira] [Updated] (ASTERIXDB-2306) Inverted list file is not deleted after an inverted index component merge operation

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2306:

Priority: Critical  (was: Major)

> Inverted list file is not deleted after an inverted index component merge 
> operation
> ---
>
> Key: ASTERIXDB-2306
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2306
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: IDX - Indexes, STO - Storage
>Reporter: Taewoo Kim
>Assignee: Taewoo Kim
>Priority: Critical
>  Labels: triaged
>
> After the following exception, an inverted list file of an old component was 
> not deleted. This was happened during an ingestion of 1 Billion tweets on a 
> Cloudberry cluster with five nodes.
> {code:java}
> 23:15:15.269 [Executor-6082:5] WARN 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMHarness - Failure 
> scheduling replication or destroying merged component
> java.lang.IllegalStateException: Page 20629:2 is pinned and file is being 
> closed. Pincount is: 1 Page is confiscated: false
> at 
> org.apache.hyracks.storage.common.buffercache.BufferCache.invalidateIfFileIdMatch(BufferCache.java:930)
>  ~[hyracks-storage-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.common.buffercache.BufferCache.sweepAndFlush(BufferCache.java:904)
>  ~[hyracks-storage-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.common.buffercache.BufferCache.deleteFile(BufferCache.java:997)
>  ~[hyracks-storage-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.common.buffercache.BufferCache.deleteFile(BufferCache.java:983)
>  ~[hyracks-storage-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.invertedindex.ondisk.OnDiskInvertedIndex.destroy(OnDiskInvertedIndex.java:170)
>  ~[hyracks-storage-am-lsm-invertedindex-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.AbstractLSMDiskComponent.deactivateAndDestroy(AbstractLSMDiskComponent.java:166)
>  ~[hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.api.AbstractLSMWithBloomFilterDiskComponent.deactivateAndDestroy(AbstractLSMWithBloomFilterDiskComponent.java:63)
>  ~[hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.api.AbstractLSMWithBuddyDiskComponent.deactivateAndDestroy(AbstractLSMWithBuddyDiskComponent.java:56)
>  ~[hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMHarness.doExitComponents(LSMHarness.java:324)
>  [hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMHarness.exitComponents(LSMHarness.java:411)
>  [hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMHarness.merge(LSMHarness.java:639)
>  [hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.invertedindex.impls.LSMInvertedIndexAccessor.merge(LSMInvertedIndexAccessor.java:125)
>  [hyracks-storage-am-lsm-invertedindex-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.MergeOperation.call(MergeOperation.java:45)
>  [hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.MergeOperation.call(MergeOperation.java:30)
>  [hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [?:1.8.0]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [?:1.8.0]
> at java.lang.Thread.run(Thread.java:744) [?:1.8.0]{code}
>  
> The directory:
> {code:java}
> -rw-r--r-- 1 waans11 waans11 262160 Feb 27 13:13 
> 2018-02-27-13-12-52-923_2018-02-27-12-45-21-400_d
> -rw-r--r-- 1 waans11 waans11 0 Feb 27 13:12 
> 2018-02-27-13-12-52-923_2018-02-27-12-45-21-400_f
> -rw-r--r-- 1 waans11 waans11 76288560 Feb 27 13:13 
> 2018-02-27-13-12-52-923_2018-02-27-12-45-21-400_i
> -rw-r--r-- 1 waans11 waans11 262160 Feb 27 13:15 
> 2018-02-27-13-15-21-671_2018-02-27-13-15-21-671_d
> -rw-r--r-- 1 waans11 waans11 0 Feb 27 13:15 
> 2018-02-27-13-15-21-671_2018-02-27-13-15-21-671_f
> -rw-r--r-- 1 waans11 waans11 2097280 Feb 27 13:15 
> 2018-02-27-13-15-21-671_2018-02-27-13-15-21-671_i
> -rw-r--r-- 1 waans11 waans11 43256400 Feb 27 23:15 
> 2018-02-27-23-14-41-965_2018-02-27-12-45-21-400_b
> -rw-r--r-- 1 waans11 waans11 262160 Feb 27 23:15 
> 2018-02-2

[jira] [Assigned] (ASTERIXDB-2306) Inverted list file is not deleted after an inverted index component merge operation

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till reassigned ASTERIXDB-2306:
---

Assignee: Taewoo Kim

> Inverted list file is not deleted after an inverted index component merge 
> operation
> ---
>
> Key: ASTERIXDB-2306
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2306
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: IDX - Indexes, STO - Storage
>Reporter: Taewoo Kim
>Assignee: Taewoo Kim
>Priority: Major
>  Labels: triaged
>
> After the following exception, an inverted list file of an old component was 
> not deleted. This was happened during an ingestion of 1 Billion tweets on a 
> Cloudberry cluster with five nodes.
> {code:java}
> 23:15:15.269 [Executor-6082:5] WARN 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMHarness - Failure 
> scheduling replication or destroying merged component
> java.lang.IllegalStateException: Page 20629:2 is pinned and file is being 
> closed. Pincount is: 1 Page is confiscated: false
> at 
> org.apache.hyracks.storage.common.buffercache.BufferCache.invalidateIfFileIdMatch(BufferCache.java:930)
>  ~[hyracks-storage-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.common.buffercache.BufferCache.sweepAndFlush(BufferCache.java:904)
>  ~[hyracks-storage-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.common.buffercache.BufferCache.deleteFile(BufferCache.java:997)
>  ~[hyracks-storage-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.common.buffercache.BufferCache.deleteFile(BufferCache.java:983)
>  ~[hyracks-storage-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.invertedindex.ondisk.OnDiskInvertedIndex.destroy(OnDiskInvertedIndex.java:170)
>  ~[hyracks-storage-am-lsm-invertedindex-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.AbstractLSMDiskComponent.deactivateAndDestroy(AbstractLSMDiskComponent.java:166)
>  ~[hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.api.AbstractLSMWithBloomFilterDiskComponent.deactivateAndDestroy(AbstractLSMWithBloomFilterDiskComponent.java:63)
>  ~[hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.api.AbstractLSMWithBuddyDiskComponent.deactivateAndDestroy(AbstractLSMWithBuddyDiskComponent.java:56)
>  ~[hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMHarness.doExitComponents(LSMHarness.java:324)
>  [hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMHarness.exitComponents(LSMHarness.java:411)
>  [hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMHarness.merge(LSMHarness.java:639)
>  [hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.invertedindex.impls.LSMInvertedIndexAccessor.merge(LSMInvertedIndexAccessor.java:125)
>  [hyracks-storage-am-lsm-invertedindex-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.MergeOperation.call(MergeOperation.java:45)
>  [hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.MergeOperation.call(MergeOperation.java:30)
>  [hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [?:1.8.0]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [?:1.8.0]
> at java.lang.Thread.run(Thread.java:744) [?:1.8.0]{code}
>  
> The directory:
> {code:java}
> -rw-r--r-- 1 waans11 waans11 262160 Feb 27 13:13 
> 2018-02-27-13-12-52-923_2018-02-27-12-45-21-400_d
> -rw-r--r-- 1 waans11 waans11 0 Feb 27 13:12 
> 2018-02-27-13-12-52-923_2018-02-27-12-45-21-400_f
> -rw-r--r-- 1 waans11 waans11 76288560 Feb 27 13:13 
> 2018-02-27-13-12-52-923_2018-02-27-12-45-21-400_i
> -rw-r--r-- 1 waans11 waans11 262160 Feb 27 13:15 
> 2018-02-27-13-15-21-671_2018-02-27-13-15-21-671_d
> -rw-r--r-- 1 waans11 waans11 0 Feb 27 13:15 
> 2018-02-27-13-15-21-671_2018-02-27-13-15-21-671_f
> -rw-r--r-- 1 waans11 waans11 2097280 Feb 27 13:15 
> 2018-02-27-13-15-21-671_2018-02-27-13-15-21-671_i
> -rw-r--r-- 1 waans11 waans11 43256400 Feb 27 23:15 
> 2018-02-27-23-14-41-965_2018-02-27-12-45-21-400_b
> -rw-r--r-- 1 waans11 waans11 262160 Feb 27 23:15 
> 2018-02-27-23-14-

[jira] [Updated] (ASTERIXDB-2306) Inverted list file is not deleted after an inverted index component merge operation

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2306:

Component/s: STO - Storage
 IDX - Indexes

> Inverted list file is not deleted after an inverted index component merge 
> operation
> ---
>
> Key: ASTERIXDB-2306
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2306
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: IDX - Indexes, STO - Storage
>Reporter: Taewoo Kim
>Priority: Major
>  Labels: triaged
>
> After the following exception, an inverted list file of an old component was 
> not deleted. This was happened during an ingestion of 1 Billion tweets on a 
> Cloudberry cluster with five nodes.
> {code:java}
> 23:15:15.269 [Executor-6082:5] WARN 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMHarness - Failure 
> scheduling replication or destroying merged component
> java.lang.IllegalStateException: Page 20629:2 is pinned and file is being 
> closed. Pincount is: 1 Page is confiscated: false
> at 
> org.apache.hyracks.storage.common.buffercache.BufferCache.invalidateIfFileIdMatch(BufferCache.java:930)
>  ~[hyracks-storage-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.common.buffercache.BufferCache.sweepAndFlush(BufferCache.java:904)
>  ~[hyracks-storage-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.common.buffercache.BufferCache.deleteFile(BufferCache.java:997)
>  ~[hyracks-storage-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.common.buffercache.BufferCache.deleteFile(BufferCache.java:983)
>  ~[hyracks-storage-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.invertedindex.ondisk.OnDiskInvertedIndex.destroy(OnDiskInvertedIndex.java:170)
>  ~[hyracks-storage-am-lsm-invertedindex-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.AbstractLSMDiskComponent.deactivateAndDestroy(AbstractLSMDiskComponent.java:166)
>  ~[hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.api.AbstractLSMWithBloomFilterDiskComponent.deactivateAndDestroy(AbstractLSMWithBloomFilterDiskComponent.java:63)
>  ~[hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.api.AbstractLSMWithBuddyDiskComponent.deactivateAndDestroy(AbstractLSMWithBuddyDiskComponent.java:56)
>  ~[hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMHarness.doExitComponents(LSMHarness.java:324)
>  [hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMHarness.exitComponents(LSMHarness.java:411)
>  [hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.LSMHarness.merge(LSMHarness.java:639)
>  [hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.invertedindex.impls.LSMInvertedIndexAccessor.merge(LSMInvertedIndexAccessor.java:125)
>  [hyracks-storage-am-lsm-invertedindex-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.MergeOperation.call(MergeOperation.java:45)
>  [hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at 
> org.apache.hyracks.storage.am.lsm.common.impls.MergeOperation.call(MergeOperation.java:30)
>  [hyracks-storage-am-lsm-common-0.3.4-SNAPSHOT.jar:0.3.4-SNAPSHOT]
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [?:1.8.0]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [?:1.8.0]
> at java.lang.Thread.run(Thread.java:744) [?:1.8.0]{code}
>  
> The directory:
> {code:java}
> -rw-r--r-- 1 waans11 waans11 262160 Feb 27 13:13 
> 2018-02-27-13-12-52-923_2018-02-27-12-45-21-400_d
> -rw-r--r-- 1 waans11 waans11 0 Feb 27 13:12 
> 2018-02-27-13-12-52-923_2018-02-27-12-45-21-400_f
> -rw-r--r-- 1 waans11 waans11 76288560 Feb 27 13:13 
> 2018-02-27-13-12-52-923_2018-02-27-12-45-21-400_i
> -rw-r--r-- 1 waans11 waans11 262160 Feb 27 13:15 
> 2018-02-27-13-15-21-671_2018-02-27-13-15-21-671_d
> -rw-r--r-- 1 waans11 waans11 0 Feb 27 13:15 
> 2018-02-27-13-15-21-671_2018-02-27-13-15-21-671_f
> -rw-r--r-- 1 waans11 waans11 2097280 Feb 27 13:15 
> 2018-02-27-13-15-21-671_2018-02-27-13-15-21-671_i
> -rw-r--r-- 1 waans11 waans11 43256400 Feb 27 23:15 
> 2018-02-27-23-14-41-965_2018-02-27-12-45-21-400_b
> -rw-r--r-- 1 waans11 waans11 262160 Feb 27 23:15 
> 2018-02-27-23-14-41-9

[jira] [Commented] (ASTERIXDB-2304) Intermittent failures in LSMFlushRecoveryTest

[Till (JIRA)]

[ 
https://issues.apache.org/jira/browse/ASTERIXDB-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16391998#comment-16391998
 ] 

Till commented on ASTERIXDB-2304:
-

[~luochen01] Can this issue be resolved?

> Intermittent failures in LSMFlushRecoveryTest
> -
>
> Key: ASTERIXDB-2304
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2304
> Project: Apache AsterixDB
>  Issue Type: Bug
>Reporter: Murtadha Hubail
>Assignee: Chen Luo
>Priority: Major
>
> Please see:
> [https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-asterix-app/3603/]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2300) Abort is not handled by feed

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2300:

Priority: Critical  (was: Major)

> Abort is not handled by feed
> 
>
> Key: ASTERIXDB-2300
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2300
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: ING - Ingestion, TX - Transactions
>Reporter: Chen Luo
>Assignee: Xikui Wang
>Priority: Critical
>  Labels: triaged
>
> During feed-based data ingestions, exception may throw by inserting/upserting 
> some records. The current feed simply discard this record and retry with the 
> rest of the records. However, abort is not called to ensure the indexes are 
> still in a consistent state (the abort logic is only called when the job is 
> aborted, however the feed is a long running job which does not terminate 
> normally)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2300) Abort is not handled by feed

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2300:

Labels: triaged  (was: )

> Abort is not handled by feed
> 
>
> Key: ASTERIXDB-2300
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2300
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: ING - Ingestion, TX - Transactions
>Reporter: Chen Luo
>Assignee: Xikui Wang
>Priority: Critical
>  Labels: triaged
>
> During feed-based data ingestions, exception may throw by inserting/upserting 
> some records. The current feed simply discard this record and retry with the 
> rest of the records. However, abort is not called to ensure the indexes are 
> still in a consistent state (the abort logic is only called when the job is 
> aborted, however the feed is a long running job which does not terminate 
> normally)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2298) Deadlock in VirtualPage.acquireWriteLatch

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2298:

Labels: triaged  (was: )

> Deadlock in VirtualPage.acquireWriteLatch
> -
>
> Key: ASTERIXDB-2298
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2298
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: STO - Storage
>Reporter: Murtadha Hubail
>Assignee: Abdullah Alamoudi
>Priority: Major
>  Labels: triaged
>
> Deadlock in VirtualPage.acquireWriteLatch on drop dataverse statement.
> See thread dump at:
> [https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-cancellation-test/2834/#|https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-cancellation-test/2834/]
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2298) Deadlock in VirtualPage.acquireWriteLatch

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2298:

Priority: Critical  (was: Major)

> Deadlock in VirtualPage.acquireWriteLatch
> -
>
> Key: ASTERIXDB-2298
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2298
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: STO - Storage
>Reporter: Murtadha Hubail
>Assignee: Abdullah Alamoudi
>Priority: Critical
>  Labels: triaged
>
> Deadlock in VirtualPage.acquireWriteLatch on drop dataverse statement.
> See thread dump at:
> [https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-cancellation-test/2834/#|https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-cancellation-test/2834/]
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ASTERIXDB-2297) Ansible upgrade script

[Till (JIRA)]

[ 
https://issues.apache.org/jira/browse/ASTERIXDB-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16392002#comment-16392002
 ] 

Till commented on ASTERIXDB-2297:
-

[~imaxon] Could you expand on the description?

 

> Ansible upgrade script
> --
>
> Key: ASTERIXDB-2297
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2297
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: ADM - Admin
>Reporter: Ian Maxon
>Assignee: Ian Maxon
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2295) Intermittent failures in objects/object-add-fields, object-remove-fields

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2295:

Labels: triaged  (was: )

> Intermittent failures in objects/object-add-fields, object-remove-fields  
> -
>
> Key: ASTERIXDB-2295
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2295
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: FUN - Functions
>Reporter: Dmitry Lychagin
>Assignee: Dmitry Lychagin
>Priority: Minor
>  Labels: triaged
>
> objects/object-add-fields, object-remove-fields tests are currently disabled 
> because of intermittent issues. They seem to produce corrupt records. Need to 
> re-enable them and investigate.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ASTERIXDB-2310) Use Primary Key Index to Enforce Insert Key Uniqueness

[Chen Luo (JIRA)]

[ 
https://issues.apache.org/jira/browse/ASTERIXDB-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16392006#comment-16392006
 ] 

Chen Luo commented on ASTERIXDB-2310:
-

[~tillw], right now this feature is used only when the user has created the 
primary key index first. Otherwise, the system's behavior for insert is still 
the same as before. Making the primary key index by default could be easily 
done from a technical perspective, but I think it needs more justifications and 
could be done separately from this patch.

> Use Primary Key Index to Enforce Insert Key Uniqueness
> --
>
> Key: ASTERIXDB-2310
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2310
> Project: Apache AsterixDB
>  Issue Type: Improvement
>  Components: ING - Ingestion, STO - Storage
>Reporter: Chen Luo
>Assignee: Chen Luo
>Priority: Major
>
> **Currently when ingesting data using INSERT operations, we always check the 
> primary index to ensure key uniqueness. However, this implies in most cases 
> all ingested records might be accessed, which will slow down the ingestion 
> performance a lot when the records cannot be cached. To handle this, we can 
> enforce key uniqueness by checking the primary key index, which is much 
> smaller and can be more easily cached.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2312) JsonLogicalPlanPrinter does not handle Upsert properly

[Chen Luo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Luo updated ASTERIXDB-2312:

Description: In case of UPSERT operator, the JsonLogicalPlanPrinter outputs 
a wrong json plan, and 

> JsonLogicalPlanPrinter does not handle Upsert properly
> --
>
> Key: ASTERIXDB-2312
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2312
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: COMP - Compiler
>Reporter: Chen Luo
>Assignee: Chen Luo
>Priority: Minor
>
> In case of UPSERT operator, the JsonLogicalPlanPrinter outputs a wrong json 
> plan, and 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2312) JsonLogicalPlanPrinter does not handle Upsert properly

[Chen Luo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Luo updated ASTERIXDB-2312:

Description: 
In case of UPSERT operator, the JsonLogicalPlanPrinter outputs a wrong json 
plan, and JsonLogicalPlanTest throws 

com.fasterxml.jackson.core.JsonParseException.

 

Failed run: 
https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-asterix-app/3666/org.apache.asterix$asterix-app/testReport/org.apache.asterix.test.jsonplan/JsonOptimizedLogicalPlanTest/test_JsonLogicalPlanTest_11__src_test_resources_optimizerts_queries_primary_key_index_upsert_primary_key_index_with_secondary_sqlpp_/

  was:In case of UPSERT operator, the JsonLogicalPlanPrinter outputs a wrong 
json plan, and 


> JsonLogicalPlanPrinter does not handle Upsert properly
> --
>
> Key: ASTERIXDB-2312
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2312
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: COMP - Compiler
>Reporter: Chen Luo
>Assignee: Chen Luo
>Priority: Minor
>
> In case of UPSERT operator, the JsonLogicalPlanPrinter outputs a wrong json 
> plan, and JsonLogicalPlanTest throws 
> com.fasterxml.jackson.core.JsonParseException.
>  
> Failed run: 
> https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-asterix-app/3666/org.apache.asterix$asterix-app/testReport/org.apache.asterix.test.jsonplan/JsonOptimizedLogicalPlanTest/test_JsonLogicalPlanTest_11__src_test_resources_optimizerts_queries_primary_key_index_upsert_primary_key_index_with_secondary_sqlpp_/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ASTERIXDB-2293) Incorrect results when dividing(affects functions like avg too)

[Till (JIRA)]

[ 
https://issues.apache.org/jira/browse/ASTERIXDB-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16392013#comment-16392013
 ] 

Till commented on ASTERIXDB-2293:
-

Currently all fractional digits in AsterixDB are stored as floating point 
values and the result seems to be correct.

> Incorrect results when dividing(affects functions like avg too)
> ---
>
> Key: ASTERIXDB-2293
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2293
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: FUN - Functions
>Reporter: James Fang
>Priority: Minor
>
> I receive incorrect results when dividing. The following queries give the 
> incorrect result in AsterixDB and Couchbase, but gives the correct result in 
> Postgres.
> For example:
> 1) array_avg( [1.2,2.3,3.4] ); 
> 2.3003
> 2) array_sum( [1.2,2.3,3.4] ) / 3;
> 2.3003
> 3) 6.9 / 3;
> 2.3003
>  
> Using the [1.1,2.2,3.3] for 1 and 2, and 6.6 instead of 6.9 in for number 3 
> gives,
> 2.1997



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2312) JsonLogicalPlanPrinter does not handle Upsert properly

[Chen Luo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Luo updated ASTERIXDB-2312:

Description: 
In case of UPSERT operator, the JsonLogicalPlanPrinter outputs a wrong json 
plan, and JsonLogicalPlanTest throws 
com.fasterxml.jackson.core.JsonParseException.

Failed run: 
https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-asterix-app/3666/org.apache.asterix$asterix-app/testReport/org.apache.asterix.test.jsonplan/JsonOptimizedLogicalPlanTest/test_JsonLogicalPlanTest_11__src_test_resources_optimizerts_queries_primary_key_index_upsert_primary_key_index_with_secondary_sqlpp_/

  was:
In case of UPSERT operator, the JsonLogicalPlanPrinter outputs a wrong json 
plan, and JsonLogicalPlanTest throws 

com.fasterxml.jackson.core.JsonParseException.

 

Failed run: 
https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-asterix-app/3666/org.apache.asterix$asterix-app/testReport/org.apache.asterix.test.jsonplan/JsonOptimizedLogicalPlanTest/test_JsonLogicalPlanTest_11__src_test_resources_optimizerts_queries_primary_key_index_upsert_primary_key_index_with_secondary_sqlpp_/


> JsonLogicalPlanPrinter does not handle Upsert properly
> --
>
> Key: ASTERIXDB-2312
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2312
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: COMP - Compiler
>Reporter: Chen Luo
>Assignee: Chen Luo
>Priority: Minor
>
> In case of UPSERT operator, the JsonLogicalPlanPrinter outputs a wrong json 
> plan, and JsonLogicalPlanTest throws 
> com.fasterxml.jackson.core.JsonParseException.
> Failed run: 
> https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-asterix-app/3666/org.apache.asterix$asterix-app/testReport/org.apache.asterix.test.jsonplan/JsonOptimizedLogicalPlanTest/test_JsonLogicalPlanTest_11__src_test_resources_optimizerts_queries_primary_key_index_upsert_primary_key_index_with_secondary_sqlpp_/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ASTERIXDB-2304) Intermittent failures in LSMFlushRecoveryTest

[Chen Luo (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chen Luo resolved ASTERIXDB-2304.
-
Resolution: Fixed

> Intermittent failures in LSMFlushRecoveryTest
> -
>
> Key: ASTERIXDB-2304
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2304
> Project: Apache AsterixDB
>  Issue Type: Bug
>Reporter: Murtadha Hubail
>Assignee: Chen Luo
>Priority: Major
>
> Please see:
> [https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-asterix-app/3603/]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ASTERIXDB-2292) Selecting the kth element from a subquery with ORDER BY

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till reassigned ASTERIXDB-2292:
---

Assignee: Ali Alsuliman

> Selecting the kth element from a subquery with ORDER BY
> ---
>
> Key: ASTERIXDB-2292
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2292
> Project: Apache AsterixDB
>  Issue Type: Improvement
>  Components: COMP - Compiler
>Reporter: Ali Alsuliman
>Assignee: Ali Alsuliman
>Priority: Major
>  Labels: triaged
>
> (select * from GBU g order by g.name)[k]
> The plan for the above query orders, then listifies the result only to pick 
> the kth element.
> The query should be turned into:
> select * from GBU g order by g.name limit 1 offset k
> This is especially important when k = 0



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2290) Feed doesn't work when the address type is NC.

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2290:

Component/s: ING - Ingestion

> Feed doesn't work when the address type is NC.
> --
>
> Key: ASTERIXDB-2290
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2290
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: ING - Ingestion
>Reporter: Taewoo Kim
>Assignee: Xikui Wang
>Priority: Major
>
> A feed works fine when the given address type is IP. The following feed can 
> be created and works without any issue.
> {code:java}
> create feed TweetFeed with {
> "adapter-name" : "socket_adapter",
> "sockets" : "x.x.x.x:10001",
> "address-type" : "IP",
> "type-name" : "typeTweet",
> "format" : "adm",
> "insert-feed" : "true"
> };{code}
>  
> The same feed doesn't work when the given address type is NC. The following 
> feed can be created. However, nothing happens when trying to ingest a record.
> {code:java}
> create feed TweetFeed with {
> "adapter-name" : "socket_adapter",
> "sockets" : "1:10001",
> "address-type" : "NC",
> "type-name" : "typeTweet",
> "format" : "adm",
> "insert-feed" : "true"
> };{code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2292) Selecting the kth element from a subquery with ORDER BY

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2292:

Labels: triaged  (was: )

> Selecting the kth element from a subquery with ORDER BY
> ---
>
> Key: ASTERIXDB-2292
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2292
> Project: Apache AsterixDB
>  Issue Type: Improvement
>  Components: COMP - Compiler
>Reporter: Ali Alsuliman
>Assignee: Ali Alsuliman
>Priority: Major
>  Labels: triaged
>
> (select * from GBU g order by g.name)[k]
> The plan for the above query orders, then listifies the result only to pick 
> the kth element.
> The query should be turned into:
> select * from GBU g order by g.name limit 1 offset k
> This is especially important when k = 0



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ASTERIXDB-1647) Some logical operators' implementations of isMap doesn't match their behavior

[Abdullah Alamoudi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abdullah Alamoudi reassigned ASTERIXDB-1647:


Assignee: Ali Alsuliman  (was: Abdullah Alamoudi)

> Some logical operators' implementations of isMap doesn't match their behavior
> -
>
> Key: ASTERIXDB-1647
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1647
> Project: Apache AsterixDB
>  Issue Type: Bug
>Reporter: Abdullah Alamoudi
>Assignee: Ali Alsuliman
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2290) Feed doesn't work when the address type is NC.

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2290:

Labels: triaged  (was: )

> Feed doesn't work when the address type is NC.
> --
>
> Key: ASTERIXDB-2290
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2290
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: ING - Ingestion
>Reporter: Taewoo Kim
>Assignee: Xikui Wang
>Priority: Major
>  Labels: triaged
>
> A feed works fine when the given address type is IP. The following feed can 
> be created and works without any issue.
> {code:java}
> create feed TweetFeed with {
> "adapter-name" : "socket_adapter",
> "sockets" : "x.x.x.x:10001",
> "address-type" : "IP",
> "type-name" : "typeTweet",
> "format" : "adm",
> "insert-feed" : "true"
> };{code}
>  
> The same feed doesn't work when the given address type is NC. The following 
> feed can be created. However, nothing happens when trying to ingest a record.
> {code:java}
> create feed TweetFeed with {
> "adapter-name" : "socket_adapter",
> "sockets" : "1:10001",
> "address-type" : "NC",
> "type-name" : "typeTweet",
> "format" : "adm",
> "insert-feed" : "true"
> };{code}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2289) Problem in SQL++ with CASE processing and field access

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2289:

Component/s: SQL - Translator SQL++

> Problem in SQL++ with CASE processing and field access
> --
>
> Key: ASTERIXDB-2289
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2289
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: COMP - Compiler
>Reporter: Michael J. Carey
>Assignee: Dmitry Lychagin
>Priority: Major
>  Labels: triaged
>
> USE TinySocial;
> SELECT
> (CASE WHEN g.id = 6 THEN g ELSE u END).name
> FROM ChirpUsers u JOIN GleambookUsers g ON u.name < g.name WHERE u.screenName 
> = "ChangEwing_573";
> --> This returns a low-level error: 
> Field access switch-case(TRUE, eq($$g.getField("id"), 6), $$g, 
> $$u).getField("name") does not correspond to any input of operator 
> org.apache.hyracks.algebricks.core.algebra.operators.logical.InnerJoinOperator@495bf56a
>  [AlgebricksException]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2289) Problem in SQL++ with CASE processing and field access

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2289:

Labels: triaged  (was: )

> Problem in SQL++ with CASE processing and field access
> --
>
> Key: ASTERIXDB-2289
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2289
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: COMP - Compiler
>Reporter: Michael J. Carey
>Assignee: Dmitry Lychagin
>Priority: Major
>  Labels: triaged
>
> USE TinySocial;
> SELECT
> (CASE WHEN g.id = 6 THEN g ELSE u END).name
> FROM ChirpUsers u JOIN GleambookUsers g ON u.name < g.name WHERE u.screenName 
> = "ChangEwing_573";
> --> This returns a low-level error: 
> Field access switch-case(TRUE, eq($$g.getField("id"), 6), $$g, 
> $$u).getField("name") does not correspond to any input of operator 
> org.apache.hyracks.algebricks.core.algebra.operators.logical.InnerJoinOperator@495bf56a
>  [AlgebricksException]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2289) Problem in SQL++ with CASE processing and field access

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2289:

Component/s: (was: SQL - Translator SQL++)
 COMP - Compiler

> Problem in SQL++ with CASE processing and field access
> --
>
> Key: ASTERIXDB-2289
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2289
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: COMP - Compiler
>Reporter: Michael J. Carey
>Assignee: Dmitry Lychagin
>Priority: Major
>  Labels: triaged
>
> USE TinySocial;
> SELECT
> (CASE WHEN g.id = 6 THEN g ELSE u END).name
> FROM ChirpUsers u JOIN GleambookUsers g ON u.name < g.name WHERE u.screenName 
> = "ChangEwing_573";
> --> This returns a low-level error: 
> Field access switch-case(TRUE, eq($$g.getField("id"), 6), $$g, 
> $$u).getField("name") does not correspond to any input of operator 
> org.apache.hyracks.algebricks.core.algebra.operators.logical.InnerJoinOperator@495bf56a
>  [AlgebricksException]
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2288) Problems in SQL++ compilation when types "open up"

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2288:

Component/s: COMP - Compiler

> Problems in SQL++ compilation when types "open up"
> --
>
> Key: ASTERIXDB-2288
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2288
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: COMP - Compiler
>Reporter: Michael J. Carey
>Assignee: Dmitry Lychagin
>Priority: Major
>
> USE TinySocial;
> -- This works based on the TinySocial tutorial schema
> SELECT VALUE a FROM (SELECT VALUE c FROM ChirpUsers c UNION ALL SELECT VALUE 
> g FROM GleambookUsers g) AS a;
> -- This doesn't work properly (field accesses broken)
> SELECT name FROM (SELECT VALUE c FROM ChirpUsers c UNION ALL SELECT VALUE g 
> FROM GleambookUsers g) AS a;
> -- This one is weird (returns some empty records)
> SELECT alias FROM (SELECT VALUE c FROM ChirpUsers c UNION ALL SELECT VALUE g 
> FROM GleambookUsers g) AS a;



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2288) Problems in SQL++ compilation when types "open up"

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2288:

Labels: triaged  (was: )

> Problems in SQL++ compilation when types "open up"
> --
>
> Key: ASTERIXDB-2288
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2288
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: COMP - Compiler
>Reporter: Michael J. Carey
>Assignee: Dmitry Lychagin
>Priority: Major
>  Labels: triaged
>
> USE TinySocial;
> -- This works based on the TinySocial tutorial schema
> SELECT VALUE a FROM (SELECT VALUE c FROM ChirpUsers c UNION ALL SELECT VALUE 
> g FROM GleambookUsers g) AS a;
> -- This doesn't work properly (field accesses broken)
> SELECT name FROM (SELECT VALUE c FROM ChirpUsers c UNION ALL SELECT VALUE g 
> FROM GleambookUsers g) AS a;
> -- This one is weird (returns some empty records)
> SELECT alias FROM (SELECT VALUE c FROM ChirpUsers c UNION ALL SELECT VALUE g 
> FROM GleambookUsers g) AS a;



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ASTERIXDB-2286) Parallel Sort Optimization

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till reassigned ASTERIXDB-2286:
---

Assignee: Ali Alsuliman

> Parallel Sort Optimization
> --
>
> Key: ASTERIXDB-2286
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2286
> Project: Apache AsterixDB
>  Issue Type: Improvement
>  Components: COMP - Compiler, FUN - Functions, HYR - Hyracks
>Reporter: Ali Alsuliman
>Assignee: Ali Alsuliman
>Priority: Major
>  Labels: triaged
>
> The current plan for queries with ORDER BY clauses consists of two phases; 
> sorting the data locally in each partition and then sort-merging the data in 
> one single partition. Even though the local sort happens in parallel, this 
> effort is wasted by the fact that the merge is happening at one partition. It 
> is desired to remove the merge step and do a true parallel sort where data is 
> range-partitioned across the cluster.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2286) Parallel Sort Optimization

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2286:

Labels: triaged  (was: )

> Parallel Sort Optimization
> --
>
> Key: ASTERIXDB-2286
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2286
> Project: Apache AsterixDB
>  Issue Type: Improvement
>  Components: COMP - Compiler, FUN - Functions, HYR - Hyracks
>Reporter: Ali Alsuliman
>Assignee: Ali Alsuliman
>Priority: Major
>  Labels: triaged
>
> The current plan for queries with ORDER BY clauses consists of two phases; 
> sorting the data locally in each partition and then sort-merging the data in 
> one single partition. Even though the local sort happens in parallel, this 
> effort is wasted by the fact that the merge is happening at one partition. It 
> is desired to remove the merge step and do a true parallel sort where data is 
> range-partitioned across the cluster.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ASTERIXDB-2285) SqlppExecutionWithCancellationTest:flwor:at00 sporadic failure

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till reassigned ASTERIXDB-2285:
---

Assignee: Abdullah Alamoudi

> SqlppExecutionWithCancellationTest:flwor:at00 sporadic failure
> --
>
> Key: ASTERIXDB-2285
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2285
> Project: Apache AsterixDB
>  Issue Type: Bug
>Reporter: Abdullah Alamoudi
>Assignee: Abdullah Alamoudi
>Priority: Major
> Attachments: info (2).log.gz
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2283) Can't start, can't stop, just can't (script bug?)

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2283:

Labels: triaged  (was: )

> Can't start, can't stop, just can't (script bug?)
> -
>
> Key: ASTERIXDB-2283
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2283
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: *DB - AsterixDB, ADM - Admin, CLUS - Cluster management, 
> CONF - Configuration
>Reporter: Michael J. Carey
>Assignee: Ian Maxon
>Priority: Major
>  Labels: triaged
>
> ==> ./start-sample-cluster.sh
> CLUSTERDIR=/Users/mikejcarey/asterix-server-0.9.3-SNAPSHOT-binary-assembly/opt/local
> INSTALLDIR=/Users/mikejcarey/asterix-server-0.9.3-SNAPSHOT-binary-assembly
> LOGSDIR=/Users/mikejcarey/asterix-server-0.9.3-SNAPSHOT-binary-assembly/opt/local/logs
>  
> {color:#FF}*ERROR: AsterixDB processes are already running; 
> aborting*{color}
>  
> Re-run with -f to ignore, or run stop-sample-cluster.sh -f to forcibly 
> terminate all running AsterixDB processes:
> cat: /tmp/pids: No such file or directory
>  
> /Users/mikejcarey/asterix-server-0.9.3-SNAPSHOT-binary-assembly/opt/local/bin
> ==> ./stop-sample-cluster.sh
> {color:#FF}*WARNING: sample cluster does not appear to be running*{color}
> WARNING: AsterixDB processes remain after cluster shutdown; re-run with 
> -f|-force to forcibly terminate all AsterixDB processes:
> cat: /tmp/pids: No such file or directory
>  
> /Users/mikejcarey/asterix-server-0.9.3-SNAPSHOT-binary-assembly/opt/local/bin



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (ASTERIXDB-2282) Http server drops unexpectedly

[Abdullah Alamoudi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abdullah Alamoudi closed ASTERIXDB-2282.

Resolution: Fixed

> Http server drops unexpectedly
> --
>
> Key: ASTERIXDB-2282
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2282
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: OTH - Other
>Reporter: Abdullah Alamoudi
>Assignee: Abdullah Alamoudi
>Priority: Major
>
> In some test runs, the Http server drops unexpectedly and stops accepting 
> requests. No relevant logs are found when that happens.
> The expected behavior is:
>  # log the unexpected channel drop.
>  # Retry forever to revive the server until a stop call is invoked.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2280) RTree on an optional nested field can't be built.

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2280:

Component/s: IDX - Indexes

> RTree on an optional nested field can't be built.
> -
>
> Key: ASTERIXDB-2280
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2280
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: IDX - Indexes
>Reporter: Taewoo Kim
>Priority: Major
>
> If there is an optional nested field, we can't build an RTree index.
>  
> {code:java}
> use twitter;
> create type typePlace if not exists as open{
> country : string,
> country_code : string,
> full_name : string,
> id : string,
> name : string,
> place_type : string,
> bounding_box : rectangle
> };
> create type typeTweet2 if not exists as open {
> create_at : datetime,
> id: int64,
> text: string,
> in_reply_to_status : int64,
> in_reply_to_user : int64,
> favorite_count : int64,
> coordinate: point?,
> retweet_count : int64,
> lang : string,
> is_retweet: boolean,
> hashtags : {{ string }} ?,
> user_mentions : {{ int64 }} ? ,
> place : typePlace?
> };
> create dataset ds_test(typeTweet2) primary key id with filter on create_at;
> // success
> CREATE INDEX dsTwIphoneIdx ON ds_test(create_at) TYPE BTREE;
> // success
> CREATE INDEX dsTwIphoneIdxCo ON ds_test(coordinate) TYPE RTREE;
> // fail
> CREATE INDEX dsTwIphoneIdxBBox ON ds_test(place.bounding_box) TYPE RTREE;
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ASTERIXDB-2280) RTree on an optional nested field can't be built.

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till reassigned ASTERIXDB-2280:
---

Assignee: Chen Luo

> RTree on an optional nested field can't be built.
> -
>
> Key: ASTERIXDB-2280
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2280
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: IDX - Indexes
>Reporter: Taewoo Kim
>Assignee: Chen Luo
>Priority: Major
>
> If there is an optional nested field, we can't build an RTree index.
>  
> {code:java}
> use twitter;
> create type typePlace if not exists as open{
> country : string,
> country_code : string,
> full_name : string,
> id : string,
> name : string,
> place_type : string,
> bounding_box : rectangle
> };
> create type typeTweet2 if not exists as open {
> create_at : datetime,
> id: int64,
> text: string,
> in_reply_to_status : int64,
> in_reply_to_user : int64,
> favorite_count : int64,
> coordinate: point?,
> retweet_count : int64,
> lang : string,
> is_retweet: boolean,
> hashtags : {{ string }} ?,
> user_mentions : {{ int64 }} ? ,
> place : typePlace?
> };
> create dataset ds_test(typeTweet2) primary key id with filter on create_at;
> // success
> CREATE INDEX dsTwIphoneIdx ON ds_test(create_at) TYPE BTREE;
> // success
> CREATE INDEX dsTwIphoneIdxCo ON ds_test(coordinate) TYPE RTREE;
> // fail
> CREATE INDEX dsTwIphoneIdxBBox ON ds_test(place.bounding_box) TYPE RTREE;
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2278) Add documentation for find_binary

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2278:

Labels: triaged  (was: )

> Add documentation for find_binary
> -
>
> Key: ASTERIXDB-2278
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2278
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: DOC - Documentation
>Reporter: Till
>Assignee: Dmitry Lychagin
>Priority: Major
>  Labels: triaged
>
> The find_binary function is missing from the documentation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ASTERIXDB-2280) RTree on an optional nested field can't be built.

[Till (JIRA)]

[ 
https://issues.apache.org/jira/browse/ASTERIXDB-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16392034#comment-16392034
 ] 

Till commented on ASTERIXDB-2280:
-

[~luochen01] Could you take a look? Or should we reassign?

> RTree on an optional nested field can't be built.
> -
>
> Key: ASTERIXDB-2280
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2280
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: IDX - Indexes
>Reporter: Taewoo Kim
>Assignee: Chen Luo
>Priority: Major
>
> If there is an optional nested field, we can't build an RTree index.
>  
> {code:java}
> use twitter;
> create type typePlace if not exists as open{
> country : string,
> country_code : string,
> full_name : string,
> id : string,
> name : string,
> place_type : string,
> bounding_box : rectangle
> };
> create type typeTweet2 if not exists as open {
> create_at : datetime,
> id: int64,
> text: string,
> in_reply_to_status : int64,
> in_reply_to_user : int64,
> favorite_count : int64,
> coordinate: point?,
> retweet_count : int64,
> lang : string,
> is_retweet: boolean,
> hashtags : {{ string }} ?,
> user_mentions : {{ int64 }} ? ,
> place : typePlace?
> };
> create dataset ds_test(typeTweet2) primary key id with filter on create_at;
> // success
> CREATE INDEX dsTwIphoneIdx ON ds_test(create_at) TYPE BTREE;
> // success
> CREATE INDEX dsTwIphoneIdxCo ON ds_test(coordinate) TYPE RTREE;
> // fail
> CREATE INDEX dsTwIphoneIdxBBox ON ds_test(place.bounding_box) TYPE RTREE;
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2277) NCService JRE check doesn't support Java 9

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2277:

Component/s: CLUS - Cluster management

> NCService JRE check doesn't support Java 9
> --
>
> Key: ASTERIXDB-2277
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2277
> Project: Apache AsterixDB
>  Issue Type: Improvement
>  Components: CLUS - Cluster management
>Reporter: Xikui Wang
>Assignee: Michael Blow
>Priority: Major
>
> 9.0 version of Java changed the naming format. It will fail the version 
> checker in NCService.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ASTERIXDB-2277) NCService JRE check doesn't support Java 9

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till reassigned ASTERIXDB-2277:
---

Assignee: Michael Blow

> NCService JRE check doesn't support Java 9
> --
>
> Key: ASTERIXDB-2277
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2277
> Project: Apache AsterixDB
>  Issue Type: Improvement
>  Components: CLUS - Cluster management
>Reporter: Xikui Wang
>Assignee: Michael Blow
>Priority: Major
>
> 9.0 version of Java changed the naming format. It will fail the version 
> checker in NCService.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2277) NCService JRE check doesn't support Java 9

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2277:

Labels: triaged  (was: )

> NCService JRE check doesn't support Java 9
> --
>
> Key: ASTERIXDB-2277
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2277
> Project: Apache AsterixDB
>  Issue Type: Improvement
>  Components: CLUS - Cluster management
>Reporter: Xikui Wang
>Assignee: Michael Blow
>Priority: Major
>  Labels: triaged
>
> 9.0 version of Java changed the naming format. It will fail the version 
> checker in NCService.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2275) Composite keys are slow

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2275:

Component/s: RT - Runtime

> Composite keys are slow
> ---
>
> Key: ASTERIXDB-2275
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2275
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: RT - Runtime
>Reporter: Ian Maxon
>Priority: Major
>
> See desc



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ASTERIXDB-2275) Composite keys are slow

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till reassigned ASTERIXDB-2275:
---

Assignee: Ian Maxon

> Composite keys are slow
> ---
>
> Key: ASTERIXDB-2275
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2275
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: RT - Runtime
>Reporter: Ian Maxon
>Assignee: Ian Maxon
>Priority: Major
>
> See desc



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ASTERIXDB-2275) Composite keys are slow

[Till (JIRA)]

[ 
https://issues.apache.org/jira/browse/ASTERIXDB-2275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16392037#comment-16392037
 ] 

Till commented on ASTERIXDB-2275:
-

[~imaxon] Not sure what to do here. I think that we either need a better 
description or we should close it.

> Composite keys are slow
> ---
>
> Key: ASTERIXDB-2275
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2275
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: RT - Runtime
>Reporter: Ian Maxon
>Assignee: Ian Maxon
>Priority: Major
>
> See desc



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2274) Creating an index statement is executed even "Execute query" option was unchecked.

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2274:

Component/s: UI - Web Interface

> Creating an index statement is executed even "Execute query" option was 
> unchecked.
> --
>
> Key: ASTERIXDB-2274
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2274
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: UI - Web Interface
>Reporter: Taewoo Kim
>Priority: Major
>
> Creating an index statement is executed for the following situation on the 
> current WebUI.
>  
> Only check "Print optimized logical plan". 
> Uncheck "Execute query".



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2274) Creating an index statement is executed even "Execute query" option was unchecked.

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2274:

Priority: Critical  (was: Major)

> Creating an index statement is executed even "Execute query" option was 
> unchecked.
> --
>
> Key: ASTERIXDB-2274
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2274
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: UI - Web Interface
>Reporter: Taewoo Kim
>Priority: Critical
>
> Creating an index statement is executed for the following situation on the 
> current WebUI.
>  
> Only check "Print optimized logical plan". 
> Uncheck "Execute query".



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ASTERIXDB-2274) Creating an index statement is executed even "Execute query" option was unchecked.

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till reassigned ASTERIXDB-2274:
---

Assignee: Xikui Wang

> Creating an index statement is executed even "Execute query" option was 
> unchecked.
> --
>
> Key: ASTERIXDB-2274
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2274
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: UI - Web Interface
>Reporter: Taewoo Kim
>Assignee: Xikui Wang
>Priority: Critical
>
> Creating an index statement is executed for the following situation on the 
> current WebUI.
>  
> Only check "Print optimized logical plan". 
> Uncheck "Execute query".



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2273) Primary key secondary index should be documented

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2273:

Labels: triaged  (was: )

> Primary key secondary index should be documented
> 
>
> Key: ASTERIXDB-2273
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2273
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: DOC - Documentation, STO - Storage
>Reporter: Taewoo Kim
>Assignee: Ali Alsuliman
>Priority: Major
>  Labels: triaged
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (ASTERIXDB-2270) Deadlock on recycling of LSMRTree memory component

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till updated ASTERIXDB-2270:

Labels: triaged  (was: )

> Deadlock on recycling of LSMRTree memory component
> --
>
> Key: ASTERIXDB-2270
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2270
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: STO - Storage
>Reporter: Abdullah Alamoudi
>Assignee: Abdullah Alamoudi
>Priority: Major
>  Labels: triaged
>
> In the build 
> [https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-asterix-app/3222/console]
> The recycling of the memory component of the LSM R-Tree deadlocked because it 
> pinned a free page and tried to get a write latch on it.
> However, a read latch that was acquired at some point was not released.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ASTERIXDB-2270) Deadlock on recycling of LSMRTree memory component

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till reassigned ASTERIXDB-2270:
---

Assignee: Abdullah Alamoudi

> Deadlock on recycling of LSMRTree memory component
> --
>
> Key: ASTERIXDB-2270
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2270
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: STO - Storage
>Reporter: Abdullah Alamoudi
>Assignee: Abdullah Alamoudi
>Priority: Major
>  Labels: triaged
>
> In the build 
> [https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-asterix-app/3222/console]
> The recycling of the memory component of the LSM R-Tree deadlocked because it 
> pinned a free page and tried to get a write latch on it.
> However, a read latch that was acquired at some point was not released.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (ASTERIXDB-2273) Primary key secondary index should be documented

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till reassigned ASTERIXDB-2273:
---

Assignee: Ali Alsuliman

> Primary key secondary index should be documented
> 
>
> Key: ASTERIXDB-2273
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2273
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: DOC - Documentation, STO - Storage
>Reporter: Taewoo Kim
>Assignee: Ali Alsuliman
>Priority: Major
>  Labels: triaged
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ASTERIXDB-2270) Deadlock on recycling of LSMRTree memory component

[Till (JIRA)]

[ 
https://issues.apache.org/jira/browse/ASTERIXDB-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16392042#comment-16392042
 ] 

Till commented on ASTERIXDB-2270:
-

[~amoudi] Can we resolve this?

 

> Deadlock on recycling of LSMRTree memory component
> --
>
> Key: ASTERIXDB-2270
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2270
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: STO - Storage
>Reporter: Abdullah Alamoudi
>Assignee: Abdullah Alamoudi
>Priority: Major
>  Labels: triaged
>
> In the build 
> [https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-asterix-app/3222/console]
> The recycling of the memory component of the LSM R-Tree deadlocked because it 
> pinned a free page and tried to get a write latch on it.
> However, a read latch that was acquired at some point was not released.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (ASTERIXDB-2270) Deadlock on recycling of LSMRTree memory component

[Abdullah Alamoudi (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-2270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abdullah Alamoudi closed ASTERIXDB-2270.

Resolution: Fixed

> Deadlock on recycling of LSMRTree memory component
> --
>
> Key: ASTERIXDB-2270
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2270
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: STO - Storage
>Reporter: Abdullah Alamoudi
>Assignee: Abdullah Alamoudi
>Priority: Major
>  Labels: triaged
>
> In the build 
> [https://asterix-jenkins.ics.uci.edu/job/asterix-gerrit-asterix-app/3222/console]
> The recycling of the memory component of the LSM R-Tree deadlocked because it 
> pinned a free page and tried to get a write latch on it.
> However, a read latch that was acquired at some point was not released.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Change in asterixdb[master]: [ASTERIXDB-1280][TEST] JUnit cleanup

[Till Westmann (Code Review)]

Till Westmann has submitted this change and it was merged.

Change subject: [ASTERIXDB-1280][TEST] JUnit cleanup
..


[ASTERIXDB-1280][TEST] JUnit cleanup

- user model changes: no
- storage format changes: no
- interface changes: no

Change-Id: I2a57643682d45097ae5ac4adc1fe97fbb3111385
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2461
Sonar-Qube: Jenkins 
Tested-by: Jenkins 
Contrib: Jenkins 
Integration-Tests: Jenkins 
Reviewed-by: Michael Blow 
---
M 
hyracks-fullstack/algebricks/algebricks-tests/src/test/java/org/apache/hyracks/algebricks/tests/pushruntime/PushRuntimeTest.java
M 
hyracks-fullstack/hyracks/hyracks-dataflow-common/src/test/java/org/apache/hyracks/dataflow/common/data/normalizers/AbstractNormalizedKeyComputerFactoryTest.java
M 
hyracks-fullstack/hyracks/hyracks-dataflow-common/src/test/java/org/apache/hyracks/dataflow/common/data/normalizers/ByteArrayNormalizedKeyComputerFactoryTest.java
M 
hyracks-fullstack/hyracks/hyracks-dataflow-std/src/test/java/org/apache/hyracks/dataflow/std/buffermanager/FrameFreeSlotBiggestFirstTest.java
M 
hyracks-fullstack/hyracks/hyracks-dataflow-std/src/test/java/org/apache/hyracks/dataflow/std/test/util/SelectionTreeTest.java
M 
hyracks-fullstack/hyracks/hyracks-examples/hyracks-integration-tests/src/test/java/org/apache/hyracks/tests/rewriting/ErrorReportingTest.java
M 
hyracks-fullstack/hyracks/hyracks-hdfs/hyracks-hdfs-core/src/test/java/org/apache/hyracks/hdfs/dataflow/DataflowTest.java
M 
hyracks-fullstack/hyracks/hyracks-hdfs/hyracks-hdfs-core/src/test/java/org/apache/hyracks/hdfs/scheduler/SchedulerTest.java
M 
hyracks-fullstack/hyracks/hyracks-hdfs/hyracks-hdfs-core/src/test/java/org/apache/hyracks/hdfs2/dataflow/DataflowTest.java
M 
hyracks-fullstack/hyracks/hyracks-hdfs/hyracks-hdfs-core/src/test/java/org/apache/hyracks/hdfs2/scheduler/SchedulerTest.java
M 
hyracks-fullstack/hyracks/hyracks-ipc/src/test/java/org/apache/hyracks/ipc/tests/IPCTest.java
M 
hyracks-fullstack/hyracks/hyracks-net/src/test/java/org/apache/hyracks/net/tests/NetTest.java
M 
hyracks-fullstack/hyracks/hyracks-server/src/test/java/org/apache/hyracks/test/server/NCServiceIT.java
M 
hyracks-fullstack/hyracks/hyracks-tests/hyracks-storage-am-lsm-btree-test/src/test/java/org/apache/hyracks/storage/am/lsm/btree/LSMBTreeFilterMergeTestDriver.java
M 
hyracks-fullstack/hyracks/hyracks-tests/hyracks-storage-am-lsm-invertedindex-test/src/test/java/org/apache/hyracks/storage/am/lsm/invertedindex/ondisk/FixedSizeFrameTupleTest.java
M 
hyracks-fullstack/hyracks/hyracks-tests/hyracks-storage-am-lsm-invertedindex-test/src/test/java/org/apache/hyracks/storage/am/lsm/invertedindex/tokenizers/WordTokenizerTest.java
16 files changed, 27 insertions(+), 40 deletions(-)

Approvals:
  Anon. E. Moose #1000171: 
  Jenkins: Verified; No violations found; ; Verified
  Michael Blow: Looks good to me, approved



diff --git 
a/hyracks-fullstack/algebricks/algebricks-tests/src/test/java/org/apache/hyracks/algebricks/tests/pushruntime/PushRuntimeTest.java
 
b/hyracks-fullstack/algebricks/algebricks-tests/src/test/java/org/apache/hyracks/algebricks/tests/pushruntime/PushRuntimeTest.java
index a7621ec..d4944af 100644
--- 
a/hyracks-fullstack/algebricks/algebricks-tests/src/test/java/org/apache/hyracks/algebricks/tests/pushruntime/PushRuntimeTest.java
+++ 
b/hyracks-fullstack/algebricks/algebricks-tests/src/test/java/org/apache/hyracks/algebricks/tests/pushruntime/PushRuntimeTest.java
@@ -93,10 +93,9 @@
 import org.apache.hyracks.dataflow.std.misc.ReplicateOperatorDescriptor;
 import org.apache.hyracks.dataflow.std.sort.InMemorySortOperatorDescriptor;
 import org.junit.AfterClass;
+import org.junit.Assert;
 import org.junit.BeforeClass;
 import org.junit.Test;
-
-import junit.framework.Assert;
 
 public class PushRuntimeTest {
 
diff --git 
a/hyracks-fullstack/hyracks/hyracks-dataflow-common/src/test/java/org/apache/hyracks/dataflow/common/data/normalizers/AbstractNormalizedKeyComputerFactoryTest.java
 
b/hyracks-fullstack/hyracks/hyracks-dataflow-common/src/test/java/org/apache/hyracks/dataflow/common/data/normalizers/AbstractNormalizedKeyComputerFactoryTest.java
index 2107574..c6e2940 100644
--- 
a/hyracks-fullstack/hyracks/hyracks-dataflow-common/src/test/java/org/apache/hyracks/dataflow/common/data/normalizers/AbstractNormalizedKeyComputerFactoryTest.java
+++ 
b/hyracks-fullstack/hyracks/hyracks-dataflow-common/src/test/java/org/apache/hyracks/dataflow/common/data/normalizers/AbstractNormalizedKeyComputerFactoryTest.java
@@ -21,9 +21,8 @@
 
 import org.apache.hyracks.data.std.api.IPointable;
 import org.apache.hyracks.dataflow.common.utils.NormalizedKeyUtils;
+import org.junit.Assert;
 import org.junit.Test;
-
-import junit.framework.Assert;
 
 public abstract class AbstractNormalizedKeyComputerFactoryTest {
 
diff --git 
a/hyracks-fullstack/hyracks/hyracks-dataflow-common/src/test/java/org/apache/hyracks/dataflow/common/data/normalizers

[jira] [Commented] (ASTERIXDB-1280) JUnit cleanup

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/ASTERIXDB-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16392045#comment-16392045
 ] 

ASF subversion and git services commented on ASTERIXDB-1280:


Commit 276ffc9600eb3563e441644496527099b0075580 in asterixdb's branch 
refs/heads/master from [~tillw]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=276ffc9 ]

[ASTERIXDB-1280][TEST] JUnit cleanup

- user model changes: no
- storage format changes: no
- interface changes: no

Change-Id: I2a57643682d45097ae5ac4adc1fe97fbb3111385
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2461
Sonar-Qube: Jenkins 
Tested-by: Jenkins 
Contrib: Jenkins 
Integration-Tests: Jenkins 
Reviewed-by: Michael Blow 


> JUnit cleanup
> -
>
> Key: ASTERIXDB-1280
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1280
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: *DB - AsterixDB, HYR - Hyracks
>Reporter: Till
>Assignee: Till
>Priority: Trivial
>
> Avoid
> junit.framework.Assert in junit.framework has been deprecated
> warnings and use the same JUnit version for Hyracks and AsterixDB



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (ASTERIXDB-1280) JUnit cleanup

[Till (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ASTERIXDB-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Till resolved ASTERIXDB-1280.
-
Resolution: Fixed
  Assignee: Michael Blow  (was: Till)

> JUnit cleanup
> -
>
> Key: ASTERIXDB-1280
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1280
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: *DB - AsterixDB, HYR - Hyracks
>Reporter: Till
>Assignee: Michael Blow
>Priority: Trivial
>
> Avoid
> junit.framework.Assert in junit.framework has been deprecated
> warnings and use the same JUnit version for Hyracks and AsterixDB



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)