[jira] [Created] (ASTERIXDB-2813) Limit the number of flush/merge threads

Chen Luo created ASTERIXDB-2813: --- Summary: Limit the number of flush/merge threads Key: ASTERIXDB-2813 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2813 Project: Apache AsterixDB Issue

[jira] [Resolved] (ASTERIXDB-2540) Optimize Performance Stability of Storage

[ https://issues.apache.org/jira/browse/ASTERIXDB-2540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo resolved ASTERIXDB-2540. - Resolution: Implemented > Optimize Performance Stability of Storage >

[jira] [Resolved] (ASTERIXDB-2708) Optimize Primary Point Searches Via Batching and Stateful Cursors

[ https://issues.apache.org/jira/browse/ASTERIXDB-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo resolved ASTERIXDB-2708. - Resolution: Implemented > Optimize Primary Point Searches Via Batching and Stateful Cursors

[jira] [Resolved] (ASTERIXDB-2715) Dynamic Memory Component Architecture

[ https://issues.apache.org/jira/browse/ASTERIXDB-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo resolved ASTERIXDB-2715. - Resolution: Implemented > Dynamic Memory Component Architecture >

[jira] [Resolved] (ASTERIXDB-2755) Test failure in MultiPartitionLSMIndexTest.testAllocateWhileFlushIsScheduled_0

[ https://issues.apache.org/jira/browse/ASTERIXDB-2755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo resolved ASTERIXDB-2755. - Resolution: Fixed > Test failure in

[jira] [Resolved] (ASTERIXDB-2786) Intermittent failure in GlobalVirtualBufferCacheTest.testFlushes

[ https://issues.apache.org/jira/browse/ASTERIXDB-2786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo resolved ASTERIXDB-2786. - Resolution: Fixed > Intermittent failure in GlobalVirtualBufferCacheTest.testFlushes >

[jira] [Assigned] (ASTERIXDB-2784) Join memory requirement for large objects

[ https://issues.apache.org/jira/browse/ASTERIXDB-2784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo reassigned ASTERIXDB-2784: --- Assignee: Shiva Jahangiri > Join memory requirement for large objects >

[jira] [Resolved] (ASTERIXDB-2783) Serious Hash Collision in Hash Join/Groupby

[ https://issues.apache.org/jira/browse/ASTERIXDB-2783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo resolved ASTERIXDB-2783. - Resolution: Fixed > Serious Hash Collision in Hash Join/Groupby >

[jira] [Created] (ASTERIXDB-2784) Join memory requirement for large objects

Chen Luo created ASTERIXDB-2784: --- Summary: Join memory requirement for large objects Key: ASTERIXDB-2784 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2784 Project: Apache AsterixDB

[jira] [Created] (ASTERIXDB-2783) Serious Hash Collision in Hash Join/Groupby

Chen Luo created ASTERIXDB-2783: --- Summary: Serious Hash Collision in Hash Join/Groupby Key: ASTERIXDB-2783 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2783 Project: Apache AsterixDB

[jira] [Commented] (ASTERIXDB-2779) Join Condition Is Not Identified for TPC-H Q18

[ https://issues.apache.org/jira/browse/ASTERIXDB-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17193962#comment-17193962 ] Chen Luo commented on ASTERIXDB-2779: - [~shivaj] This issue may be of your interest if you're

[jira] [Created] (ASTERIXDB-2779) Join Condition Is Not Identified for TPC-H Q18

Chen Luo created ASTERIXDB-2779: --- Summary: Join Condition Is Not Identified for TPC-H Q18 Key: ASTERIXDB-2779 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2779 Project: Apache AsterixDB

[jira] [Updated] (ASTERIXDB-2776) Transaction logs not truncated during rebalancing

[ https://issues.apache.org/jira/browse/ASTERIXDB-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo updated ASTERIXDB-2776: Issue Type: Bug (was: Wish) > Transaction logs not truncated during rebalancing >

[jira] [Updated] (ASTERIXDB-2776) Transaction logs not truncated during rebalancing

[ https://issues.apache.org/jira/browse/ASTERIXDB-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo updated ASTERIXDB-2776: Description: During rebalancing, we upsert a lot of records into the new dataset, which also

[jira] [Created] (ASTERIXDB-2776) Transaction logs not truncated during rebalancing

Chen Luo created ASTERIXDB-2776: --- Summary: Transaction logs not truncated during rebalancing Key: ASTERIXDB-2776 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2776 Project: Apache AsterixDB

[jira] [Commented] (ASTERIXDB-2766) fulltext index issues a bug.

[ https://issues.apache.org/jira/browse/ASTERIXDB-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17164593#comment-17164593 ] Chen Luo commented on ASTERIXDB-2766: - We do not support building inverted index on

[jira] [Created] (ASTERIXDB-2765) Indentify Secondary Index-Only Plans without WHERE conditions

Chen Luo created ASTERIXDB-2765: --- Summary: Indentify Secondary Index-Only Plans without WHERE conditions Key: ASTERIXDB-2765 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2765 Project: Apache

[jira] [Created] (ASTERIXDB-2764) Support Secondary Index Compression

Chen Luo created ASTERIXDB-2764: --- Summary: Support Secondary Index Compression Key: ASTERIXDB-2764 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2764 Project: Apache AsterixDB Issue

[jira] [Created] (ASTERIXDB-2763) Support Included Fields in Secondary Indexes

Chen Luo created ASTERIXDB-2763: --- Summary: Support Included Fields in Secondary Indexes Key: ASTERIXDB-2763 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2763 Project: Apache AsterixDB

[jira] [Updated] (ASTERIXDB-2761) Join keys not sorted in index nested loop join

[ https://issues.apache.org/jira/browse/ASTERIXDB-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo updated ASTERIXDB-2761: Attachment: plan > Join keys not sorted in index nested loop join >

[jira] [Updated] (ASTERIXDB-2761) Join keys not sorted in index nested loop join

[ https://issues.apache.org/jira/browse/ASTERIXDB-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo updated ASTERIXDB-2761: Description: When testing a query (TPC-H Q3), I found out that sometimes the join keys are

[jira] [Updated] (ASTERIXDB-2761) Join keys not sorted in index nested loop join

[ https://issues.apache.org/jira/browse/ASTERIXDB-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo updated ASTERIXDB-2761: Description: When testing a query (TPC-H Q3), I found out that sometimes the join keys are

[jira] [Updated] (ASTERIXDB-2761) Join keys not sorted in index nested loop join

[ https://issues.apache.org/jira/browse/ASTERIXDB-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo updated ASTERIXDB-2761: Description: When testing a query (TPC-H Q3), I found out that sometimes the join keys are

[jira] [Updated] (ASTERIXDB-2761) Join keys not sorted in index nested loop join

[ https://issues.apache.org/jira/browse/ASTERIXDB-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo updated ASTERIXDB-2761: Description: When testing a query (TPC-H Q3), I found out that sometimes the join keys are

[jira] [Updated] (ASTERIXDB-2761) Join keys not sorted in index nested loop join

[ https://issues.apache.org/jira/browse/ASTERIXDB-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo updated ASTERIXDB-2761: Description: When testing a query (TPC-H Q3), I found out that sometimes the join keys are

[jira] [Updated] (ASTERIXDB-2761) Join keys not sorted in index nested loop join

[ https://issues.apache.org/jira/browse/ASTERIXDB-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo updated ASTERIXDB-2761: Description: When testing a query (TPC-H Q3), I found out that sometimes the join keys are

[jira] [Updated] (ASTERIXDB-2761) Join keys not sorted in index nested loop join

[ https://issues.apache.org/jira/browse/ASTERIXDB-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo updated ASTERIXDB-2761: Description: When testing a query (TPC-H Q3), I found out that sometimes the join keys are

[jira] [Created] (ASTERIXDB-2761) Join keys not sorted in index nested loop join

Chen Luo created ASTERIXDB-2761: --- Summary: Join keys not sorted in index nested loop join Key: ASTERIXDB-2761 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2761 Project: Apache AsterixDB

[jira] [Commented] (ASTERIXDB-2756) NullPointerException in DatasetResourceReference.parse()

[ https://issues.apache.org/jira/browse/ASTERIXDB-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152930#comment-17152930 ] Chen Luo commented on ASTERIXDB-2756: - Thanks! I think we should simply skip replicaiton, if the

[jira] [Assigned] (ASTERIXDB-2756) NullPointerException in DatasetResourceReference.parse()

[ https://issues.apache.org/jira/browse/ASTERIXDB-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo reassigned ASTERIXDB-2756: --- Assignee: Murtadha Makki Al Hubail (was: Chen Luo) > NullPointerException in

[jira] [Commented] (ASTERIXDB-2756) NullPointerException in DatasetResourceReference.parse()

[ https://issues.apache.org/jira/browse/ASTERIXDB-2756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17152864#comment-17152864 ] Chen Luo commented on ASTERIXDB-2756: - I checked the code but I don't think the recent LSM

[jira] [Created] (ASTERIXDB-2715) Dynamic Memory Component Architecture

Chen Luo created ASTERIXDB-2715: --- Summary: Dynamic Memory Component Architecture Key: ASTERIXDB-2715 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2715 Project: Apache AsterixDB Issue

[jira] [Created] (ASTERIXDB-2708) Optimize Primary Point Searches Via Batching and Stateful Cursors

Chen Luo created ASTERIXDB-2708: --- Summary: Optimize Primary Point Searches Via Batching and Stateful Cursors Key: ASTERIXDB-2708 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2708 Project:

[jira] [Assigned] (ASTERIXDB-2493) In-memory LSM filter is not thread safe

[ https://issues.apache.org/jira/browse/ASTERIXDB-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo reassigned ASTERIXDB-2493: --- Assignee: Chen Luo > In-memory LSM filter is not thread safe >

[jira] [Resolved] (ASTERIXDB-2493) In-memory LSM filter is not thread safe

[ https://issues.apache.org/jira/browse/ASTERIXDB-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo resolved ASTERIXDB-2493. - Resolution: Fixed Fixed by https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/5363 >

[jira] [Created] (ASTERIXDB-2666) One-Phase Log Replay Approach

Chen Luo created ASTERIXDB-2666: --- Summary: One-Phase Log Replay Approach Key: ASTERIXDB-2666 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2666 Project: Apache AsterixDB Issue Type:

[jira] [Resolved] (ASTERIXDB-2654) Potential LSM failure related to max file size

[ https://issues.apache.org/jira/browse/ASTERIXDB-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo resolved ASTERIXDB-2654. - Resolution: Not A Bug This is not a bug because the OS file size limit should be increased.

[jira] [Commented] (ASTERIXDB-2654) Potential LSM failure related to max file size

[ https://issues.apache.org/jira/browse/ASTERIXDB-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16948081#comment-16948081 ] Chen Luo commented on ASTERIXDB-2654: - It's not a good idea to limit to the maximum disk

[jira] [Resolved] (ASTERIXDB-2600) Introduce ConcurrentMergePolicy

[ https://issues.apache.org/jira/browse/ASTERIXDB-2600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo resolved ASTERIXDB-2600. - Resolution: Implemented > Introduce ConcurrentMergePolicy > ---

[jira] [Resolved] (ASTERIXDB-2541) Introduce GreedyScheduler

[ https://issues.apache.org/jira/browse/ASTERIXDB-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo resolved ASTERIXDB-2541. - Resolution: Implemented > Introduce GreedyScheduler > - > >

[jira] [Resolved] (ASTERIXDB-2522) Skip logging WAIT record during lock conflicts

[ https://issues.apache.org/jira/browse/ASTERIXDB-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo resolved ASTERIXDB-2522. - Resolution: Implemented > Skip logging WAIT record during lock conflicts >

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

[ https://issues.apache.org/jira/browse/ASTERIXDB-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo resolved ASTERIXDB-2310. - Resolution: Implemented > Use Primary Key Index to Enforce Insert Key Uniqueness >

[jira] [Created] (ASTERIXDB-2600) Introduce ConcurrentMergePolicy

Chen Luo created ASTERIXDB-2600: --- Summary: Introduce ConcurrentMergePolicy Key: ASTERIXDB-2600 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2600 Project: Apache AsterixDB Issue Type:

[jira] [Updated] (ASTERIXDB-2543) Curl HTTP API Usages for multi-statements

[ https://issues.apache.org/jira/browse/ASTERIXDB-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo updated ASTERIXDB-2543: Attachment: create_insert.sh > Curl HTTP API Usages for multi-statements >

[jira] [Updated] (ASTERIXDB-2543) Curl HTTP API Usages for multi-statements

[ https://issues.apache.org/jira/browse/ASTERIXDB-2543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo updated ASTERIXDB-2543: Attachment: (was: create_insert.sh) > Curl HTTP API Usages for multi-statements >

[jira] [Created] (ASTERIXDB-2543) Curl HTTP API Usages for multi-statements

Chen Luo created ASTERIXDB-2543: --- Summary: Curl HTTP API Usages for multi-statements Key: ASTERIXDB-2543 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2543 Project: Apache AsterixDB

[jira] [Closed] (ASTERIXDB-2542) Insert duplicate check is not atomic

[ https://issues.apache.org/jira/browse/ASTERIXDB-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo closed ASTERIXDB-2542. --- Resolution: Not A Problem The conflict is resolved when writers insert into the (same) memory

[jira] [Created] (ASTERIXDB-2542) Insert duplicate check is not atomic

Chen Luo created ASTERIXDB-2542: --- Summary: Insert duplicate check is not atomic Key: ASTERIXDB-2542 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2542 Project: Apache AsterixDB Issue

[jira] [Updated] (ASTERIXDB-2541) Introduce GreedyScheduler

[ https://issues.apache.org/jira/browse/ASTERIXDB-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo updated ASTERIXDB-2541: Description: Our currently AsynchronousScheduler tries to schedule all merge operations at

[jira] [Created] (ASTERIXDB-2541) Introduce GreedyScheduler

Chen Luo created ASTERIXDB-2541: --- Summary: Introduce GreedyScheduler Key: ASTERIXDB-2541 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2541 Project: Apache AsterixDB Issue Type:

[jira] [Created] (ASTERIXDB-2540) Optimize Performance Stability of Storage

Chen Luo created ASTERIXDB-2540: --- Summary: Optimize Performance Stability of Storage Key: ASTERIXDB-2540 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2540 Project: Apache AsterixDB

[jira] [Created] (ASTERIXDB-2522) Skip logging WAIT record during lock conflicts

Chen Luo created ASTERIXDB-2522: --- Summary: Skip logging WAIT record during lock conflicts Key: ASTERIXDB-2522 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2522 Project: Apache AsterixDB

[jira] [Resolved] (ASTERIXDB-2468) Projection pushdown is not performed correctly for COUNT()

[ https://issues.apache.org/jira/browse/ASTERIXDB-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo resolved ASTERIXDB-2468. - Resolution: Implemented Assignee: Chen Luo > Projection pushdown is not performed

[jira] [Commented] (ASTERIXDB-2468) Projection pushdown is not performed correctly for COUNT()

[ https://issues.apache.org/jira/browse/ASTERIXDB-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16664366#comment-16664366 ] Chen Luo commented on ASTERIXDB-2468: - [~dlychagin-cb] Can you confirm this is a correct behavior

[jira] [Created] (ASTERIXDB-2468) Projection pushdown is not performed correctly for COUNT()

Chen Luo created ASTERIXDB-2468: --- Summary: Projection pushdown is not performed correctly for COUNT() Key: ASTERIXDB-2468 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2468 Project: Apache

[jira] [Resolved] (ASTERIXDB-2467) Concurrency control protocol is not correct when there are bad tuples

[ https://issues.apache.org/jira/browse/ASTERIXDB-2467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo resolved ASTERIXDB-2467. - Resolution: Fixed Assignee: Chen Luo > Concurrency control protocol is not correct

[jira] [Created] (ASTERIXDB-2467) Concurrency control protocol is not correct when there are bad tuples

Chen Luo created ASTERIXDB-2467: --- Summary: Concurrency control protocol is not correct when there are bad tuples Key: ASTERIXDB-2467 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2467 Project:

[jira] [Comment Edited] (ASTERIXDB-2464) createFile() followed by deleteFile() will not unregister the file

[ https://issues.apache.org/jira/browse/ASTERIXDB-2464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16649510#comment-16649510 ] Chen Luo edited comment on ASTERIXDB-2464 at 10/14/18 7:47 PM: --- -Why

[jira] [Commented] (ASTERIXDB-2464) createFile() followed by deleteFile() will not unregister the file

[ https://issues.apache.org/jira/browse/ASTERIXDB-2464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16649510#comment-16649510 ] Chen Luo commented on ASTERIXDB-2464: - Why this would cause problems? Line 1026 is mainly for

[jira] [Resolved] (ASTERIXDB-2452) ListifyUnnestingFunctionRule didn't recompute type environment properly after firing

[ https://issues.apache.org/jira/browse/ASTERIXDB-2452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo resolved ASTERIXDB-2452. - Resolution: Fixed > ListifyUnnestingFunctionRule didn't recompute type environment properly

[jira] [Resolved] (ASTERIXDB-2453) Improve the Constant Merge Policy

[ https://issues.apache.org/jira/browse/ASTERIXDB-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo resolved ASTERIXDB-2453. - Resolution: Fixed > Improve the Constant Merge Policy > - >

[jira] [Updated] (ASTERIXDB-2453) Improve the Constant Merge Policy

[ https://issues.apache.org/jira/browse/ASTERIXDB-2453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo updated ASTERIXDB-2453: Description: The current constant merge policy has a very high merge cost (O(n*n), where n is

[jira] [Created] (ASTERIXDB-2453) Improve the Constant Merge Policy

Chen Luo created ASTERIXDB-2453: --- Summary: Improve the Constant Merge Policy Key: ASTERIXDB-2453 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2453 Project: Apache AsterixDB Issue Type:

[jira] [Created] (ASTERIXDB-2452) ListifyUnnestingFunctionRule didn't recompute type environment properly after firing

Chen Luo created ASTERIXDB-2452: --- Summary: ListifyUnnestingFunctionRule didn't recompute type environment properly after firing Key: ASTERIXDB-2452 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2452

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

[ https://issues.apache.org/jira/browse/ASTERIXDB-2312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo resolved ASTERIXDB-2312. - Resolution: Fixed > JsonLogicalPlanPrinter does not handle Upsert properly >

[jira] [Resolved] (ASTERIXDB-2367) Reduce Blocking when Create/Open/Delete Files from BufferCache

[ https://issues.apache.org/jira/browse/ASTERIXDB-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo resolved ASTERIXDB-2367. - Resolution: Fixed > Reduce Blocking when Create/Open/Delete Files from BufferCache >

[jira] [Resolved] (ASTERIXDB-2334) A range-search on a composite index doesn't work as expected.

[ https://issues.apache.org/jira/browse/ASTERIXDB-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo resolved ASTERIXDB-2334. - Resolution: Fixed > A range-search on a composite index doesn't work as expected. >

[jira] [Resolved] (ASTERIXDB-2344) Predicate/LIMIT pushdown for primary scans

[ https://issues.apache.org/jira/browse/ASTERIXDB-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo resolved ASTERIXDB-2344. - Resolution: Implemented > Predicate/LIMIT pushdown for primary scans >

[jira] [Resolved] (ASTERIXDB-2429) Primary Key Index is not properly maintained by upsert feeds

[ https://issues.apache.org/jira/browse/ASTERIXDB-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo resolved ASTERIXDB-2429. - Resolution: Fixed > Primary Key Index is not properly maintained by upsert feeds >

[jira] [Created] (ASTERIXDB-2432) HTTP server hangs with lot of threads waiting for completion

Chen Luo created ASTERIXDB-2432: --- Summary: HTTP server hangs with lot of threads waiting for completion Key: ASTERIXDB-2432 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2432 Project: Apache

[jira] [Assigned] (ASTERIXDB-2429) Primary Key Index is not properly maintained by upsert feeds

[ https://issues.apache.org/jira/browse/ASTERIXDB-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo reassigned ASTERIXDB-2429: --- Assignee: Chen Luo > Primary Key Index is not properly maintained by upsert feeds >

[jira] [Created] (ASTERIXDB-2429) Primary Key Index is not properly maintained by upsert feeds

Chen Luo created ASTERIXDB-2429: --- Summary: Primary Key Index is not properly maintained by upsert feeds Key: ASTERIXDB-2429 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2429 Project: Apache

[jira] [Resolved] (ASTERIXDB-2421) Recovery fails with component ID mismatch

[ https://issues.apache.org/jira/browse/ASTERIXDB-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo resolved ASTERIXDB-2421. - Resolution: Duplicate > Recovery fails with component ID mismatch >

[jira] [Commented] (ASTERIXDB-2421) Recovery fails with component ID mismatch

[ https://issues.apache.org/jira/browse/ASTERIXDB-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16554710#comment-16554710 ] Chen Luo commented on ASTERIXDB-2421: - This bug should have been fixed by a later patch, but

[jira] [Assigned] (ASTERIXDB-2421) Recovery fails with component ID mismatch

[ https://issues.apache.org/jira/browse/ASTERIXDB-2421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo reassigned ASTERIXDB-2421: --- Assignee: Chen Luo (was: Ian Maxon) > Recovery fails with component ID mismatch >

[jira] [Created] (ASTERIXDB-2392) Improve Key Comparison During LSM Merge

Chen Luo created ASTERIXDB-2392: --- Summary: Improve Key Comparison During LSM Merge Key: ASTERIXDB-2392 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2392 Project: Apache AsterixDB Issue

[jira] [Closed] (ASTERIXDB-2379) Inconsistent naming for LSM Component timestamps

[ https://issues.apache.org/jira/browse/ASTERIXDB-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo closed ASTERIXDB-2379. --- Resolution: Not A Problem > Inconsistent naming for LSM Component timestamps >

[jira] [Updated] (ASTERIXDB-2379) Inconsistent naming for LSM Component timestamps

[ https://issues.apache.org/jira/browse/ASTERIXDB-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo updated ASTERIXDB-2379: Description: The current naming of LSM components are inconsistent.

[jira] [Created] (ASTERIXDB-2379) Inconsistent naming for LSM Component timestamps

Chen Luo created ASTERIXDB-2379: --- Summary: Inconsistent naming for LSM Component timestamps Key: ASTERIXDB-2379 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2379 Project: Apache AsterixDB

[jira] [Created] (ASTERIXDB-2367) Reduce Blocking when Create/Open/Delete Files from BufferCache

Chen Luo created ASTERIXDB-2367: --- Summary: Reduce Blocking when Create/Open/Delete Files from BufferCache Key: ASTERIXDB-2367 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2367 Project: Apache

[jira] [Resolved] (ASTERIXDB-2357) ADMParser String Creation Improvements

[ https://issues.apache.org/jira/browse/ASTERIXDB-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo resolved ASTERIXDB-2357. - Resolution: Fixed > ADMParser String Creation Improvements >

[jira] [Commented] (ASTERIXDB-2364) Insert statement doesn't recognize the dataverse in full dataset name

[ https://issues.apache.org/jira/browse/ASTERIXDB-2364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16436725#comment-16436725 ] Chen Luo commented on ASTERIXDB-2364: - I think the correct grammar should be `test`.`employee`

[jira] [Created] (ASTERIXDB-2365) Various LSM IO Operations Shouldn't Simply Share the Same Write Queue

Chen Luo created ASTERIXDB-2365: --- Summary: Various LSM IO Operations Shouldn't Simply Share the Same Write Queue Key: ASTERIXDB-2365 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2365 Project:

[jira] [Created] (ASTERIXDB-2357) ADMParser String Creation Improvements

Chen Luo created ASTERIXDB-2357: --- Summary: ADMParser String Creation Improvements Key: ASTERIXDB-2357 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2357 Project: Apache AsterixDB Issue

[jira] [Updated] (ASTERIXDB-2350) Improve IN subquery

[ https://issues.apache.org/jira/browse/ASTERIXDB-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo updated ASTERIXDB-2350: Summary: Improve IN subquery (was: Improvement of IN subquery) > Improve IN subquery >

[jira] [Created] (ASTERIXDB-2350) Improvement of IN subquery

Chen Luo created ASTERIXDB-2350: --- Summary: Improvement of IN subquery Key: ASTERIXDB-2350 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2350 Project: Apache AsterixDB Issue Type:

[jira] [Resolved] (ASTERIXDB-2339) Improve Inverted Index Merge Performance

[ https://issues.apache.org/jira/browse/ASTERIXDB-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo resolved ASTERIXDB-2339. - Resolution: Implemented > Improve Inverted Index Merge Performance >

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

[ https://issues.apache.org/jira/browse/ASTERIXDB-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo resolved ASTERIXDB-2280. - Resolution: Fixed > RTree on an optional nested field can't be built. >

[jira] [Created] (ASTERIXDB-2347) Documentation is missing for "storage.max.active.writable.datasets"

Chen Luo created ASTERIXDB-2347: --- Summary: Documentation is missing for "storage.max.active.writable.datasets" Key: ASTERIXDB-2347 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2347 Project:

[jira] [Updated] (ASTERIXDB-2344) Predicate/LIMIT pushdown for primary scans

[ https://issues.apache.org/jira/browse/ASTERIXDB-2344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo updated ASTERIXDB-2344: Description: Currently we don't have limit/predicate pushdown for simple select queries, e.g.,

[jira] [Created] (ASTERIXDB-2344) Predicate/LIMIT pushdown for primary scans

Chen Luo created ASTERIXDB-2344: --- Summary: Predicate/LIMIT pushdown for primary scans Key: ASTERIXDB-2344 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2344 Project: Apache AsterixDB

[jira] [Closed] (ASTERIXDB-2342) Inconsistent Configuration with NCService

[ https://issues.apache.org/jira/browse/ASTERIXDB-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo closed ASTERIXDB-2342. --- Resolution: Not A Bug > Inconsistent Configuration with NCService >

[jira] [Created] (ASTERIXDB-2342) Inconsistent Configuration with NCService

Chen Luo created ASTERIXDB-2342: --- Summary: Inconsistent Configuration with NCService Key: ASTERIXDB-2342 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2342 Project: Apache AsterixDB

[jira] [Resolved] (ASTERIXDB-2341) RSSRecordReaderTest Failure

[ https://issues.apache.org/jira/browse/ASTERIXDB-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo resolved ASTERIXDB-2341. - Resolution: Duplicate Duplicate with ASTERIXDB-2216 > RSSRecordReaderTest Failure >

[jira] [Created] (ASTERIXDB-2341) RSSRecordReaderTest Failure

Chen Luo created ASTERIXDB-2341: --- Summary: RSSRecordReaderTest Failure Key: ASTERIXDB-2341 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2341 Project: Apache AsterixDB Issue Type: Bug

[jira] [Assigned] (ASTERIXDB-2334) A range-search on a composite index doesn't work as expected.

[ https://issues.apache.org/jira/browse/ASTERIXDB-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chen Luo reassigned ASTERIXDB-2334: --- Assignee: Chen Luo (was: Dmitry Lychagin) > A range-search on a composite index doesn't

[jira] [Created] (ASTERIXDB-2339) Improve Inverted Index Merge Performance

Chen Luo created ASTERIXDB-2339: --- Summary: Improve Inverted Index Merge Performance Key: ASTERIXDB-2339 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2339 Project: Apache AsterixDB

[jira] [Commented] (ASTERIXDB-2334) A range-search on a composite index doesn't work as expected.

[ https://issues.apache.org/jira/browse/ASTERIXDB-2334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16411711#comment-16411711 ] Chen Luo commented on ASTERIXDB-2334: - In this case, the SELECT operator should not be needed

[jira] [Commented] (ASTERIXDB-2336) Sorting big tuples fails due to memory budget

[ https://issues.apache.org/jira/browse/ASTERIXDB-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16409857#comment-16409857 ] Chen Luo commented on ASTERIXDB-2336: - I think this is designed intentionally to enforce memory

[jira] [Commented] (ASTERIXDB-2331) Plan branch repeated

[ https://issues.apache.org/jira/browse/ASTERIXDB-2331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16398060#comment-16398060 ] Chen Luo commented on ASTERIXDB-2331: - I think this is the intended behavior of index-only plan,

  1   2   3   >