[jira] [Created] (ASTERIXDB-1496) Having an ability to put nullable field information when creating an enforced index

Taewoo Kim created ASTERIXDB-1496: - Summary: Having an ability to put nullable field information when creating an enforced index Key: ASTERIXDB-1496 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1496

[jira] [Created] (ASTERIXDB-1495) Secondary Index-only scan without any predicate

Taewoo Kim created ASTERIXDB-1495: - Summary: Secondary Index-only scan without any predicate Key: ASTERIXDB-1495 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1495 Project: Apache AsterixDB

[jira] [Commented] (ASTERIXDB-1544) Omit the fuzzyjoin on inverted index

[ https://issues.apache.org/jira/browse/ASTERIXDB-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15394258#comment-15394258 ] Taewoo Kim commented on ASTERIXDB-1544: --- For the future records, the issue was an indexed

[jira] [Resolved] (ASTERIXDB-1544) Omit the fuzzyjoin on inverted index

[ https://issues.apache.org/jira/browse/ASTERIXDB-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taewoo Kim resolved ASTERIXDB-1544. --- Resolution: Fixed > Omit the fuzzyjoin on inverted index >

[jira] [Commented] (ASTERIXDB-1544) Omit the fuzzyjoin on inverted index

[ https://issues.apache.org/jira/browse/ASTERIXDB-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15393053#comment-15393053 ] Taewoo Kim commented on ASTERIXDB-1544: --- @Chen: this issues will be fixed soon when my patch is

[jira] [Commented] (ASTERIXDB-1529) Query 7 in AsterixDB 101 is broken

[ https://issues.apache.org/jira/browse/ASTERIXDB-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378566#comment-15378566 ] Taewoo Kim commented on ASTERIXDB-1529: --- In addition, we can add ADM 101 examples as the runtime

[jira] [Commented] (ASTERIXDB-1529) Query 7 in AsterixDB 101 is broken

[ https://issues.apache.org/jira/browse/ASTERIXDB-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378581#comment-15378581 ] Taewoo Kim commented on ASTERIXDB-1529: --- Got it. Thanks! > Query 7 in AsterixDB 101 is broken >

[jira] [Commented] (ASTERIXDB-1529) Query 7 in AsterixDB 101 is broken

[ https://issues.apache.org/jira/browse/ASTERIXDB-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378579#comment-15378579 ] Taewoo Kim commented on ASTERIXDB-1529: --- Got it. Thanks! > Query 7 in AsterixDB 101 is broken >

[jira] [Comment Edited] (ASTERIXDB-1529) Query 7 in AsterixDB 101 is broken

[ https://issues.apache.org/jira/browse/ASTERIXDB-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15378579#comment-15378579 ] Taewoo Kim edited comment on ASTERIXDB-1529 at 7/14/16 11:21 PM: - Got

[jira] [Commented] (ASTERIXDB-1544) Omit the fuzzyjoin on inverted index

[ https://issues.apache.org/jira/browse/ASTERIXDB-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15391192#comment-15391192 ] Taewoo Kim commented on ASTERIXDB-1544: --- Can you also post the query that generates this

[jira] [Commented] (ASTERIXDB-1556) Prefix-based multi-way Fuzzy-join generates an exception.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15398204#comment-15398204 ] Taewoo Kim commented on ASTERIXDB-1556: --- >From Chen: Here are my thoughts. - There are two

[jira] [Commented] (ASTERIXDB-1556) Prefix-based multi-way Fuzzy-join generates an exception.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15398207#comment-15398207 ] Taewoo Kim commented on ASTERIXDB-1556: --- I agree that the join cost is more important. However,

[jira] [Commented] (ASTERIXDB-1556) Prefix-based multi-way Fuzzy-join generates an exception.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15398206#comment-15398206 ] Taewoo Kim commented on ASTERIXDB-1556: --- >From Wenhai: Also agree with the major opinion. We

[jira] [Commented] (ASTERIXDB-1556) Prefix-based multi-way Fuzzy-join generates an exception.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15398198#comment-15398198 ] Taewoo Kim commented on ASTERIXDB-1556: --- I have gone through the logic (3 stages) in AQL level.

[jira] [Commented] (ASTERIXDB-1556) Prefix-based multi-way Fuzzy-join generates an exception.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15398201#comment-15398201 ] Taewoo Kim commented on ASTERIXDB-1556: --- >From Wenhai: Yep, to be honest, I also think so. As

[jira] [Commented] (ASTERIXDB-1556) Prefix-based multi-way Fuzzy-join generates an exception.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15398341#comment-15398341 ] Taewoo Kim commented on ASTERIXDB-1556: ---

[jira] [Commented] (ASTERIXDB-1556) Hash Table used by External hash group-by doesn't conform to the budget.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15415632#comment-15415632 ] Taewoo Kim commented on ASTERIXDB-1556: --- Sure. We can have a F2F discussion. The reasoning

[jira] [Commented] (ASTERIXDB-1556) Prefix-based multi-way Fuzzy-join generates an exception.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15403898#comment-15403898 ] Taewoo Kim commented on ASTERIXDB-1556: --- It seems that the compiler doesn't set the hash table

[jira] [Commented] (ASTERIXDB-1556) Prefix-based multi-way Fuzzy-join generates an exception.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15405183#comment-15405183 ] Taewoo Kim commented on ASTERIXDB-1556: --- At this moment, I'm wondered how [~javierjia]

[jira] [Comment Edited] (ASTERIXDB-1556) Prefix-based multi-way Fuzzy-join generates an exception.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15405183#comment-15405183 ] Taewoo Kim edited comment on ASTERIXDB-1556 at 8/3/16 2:17 AM: --- At this

[jira] [Commented] (ASTERIXDB-1556) Prefix-based multi-way Fuzzy-join generates an exception.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15405354#comment-15405354 ] Taewoo Kim commented on ASTERIXDB-1556: --- Thanks! > Prefix-based multi-way Fuzzy-join generates

[jira] [Commented] (ASTERIXDB-1556) Prefix-based multi-way Fuzzy-join generates an exception.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15405353#comment-15405353 ] Taewoo Kim commented on ASTERIXDB-1556: --- It makes sense. > Prefix-based multi-way Fuzzy-join

[jira] [Commented] (ASTERIXDB-1556) Prefix-based multi-way Fuzzy-join generates an exception.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15405350#comment-15405350 ] Taewoo Kim commented on ASTERIXDB-1556: --- [~javierjia]]: thanks! I will see the design doc. >

[jira] [Commented] (ASTERIXDB-1556) Prefix-based multi-way Fuzzy-join generates an exception.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15404313#comment-15404313 ] Taewoo Kim commented on ASTERIXDB-1556: --- As far as I checked, yes. This is not related to a

[jira] [Commented] (ASTERIXDB-1556) Prefix-based multi-way Fuzzy-join generates an exception.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15404391#comment-15404391 ] Taewoo Kim commented on ASTERIXDB-1556: --- A more readable format Applied. > Prefix-based

[jira] [Commented] (ASTERIXDB-1556) Hash Table used by External hash group-by doesn't conform to the budget.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418007#comment-15418007 ] Taewoo Kim commented on ASTERIXDB-1556: --- I see. We can keep the current scheme (just setting the

[jira] [Commented] (ASTERIXDB-1556) Hash Table used by External hash group-by doesn't conform to the budget.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15414598#comment-15414598 ] Taewoo Kim commented on ASTERIXDB-1556: --- The summary of a Skype call with [~dtabass], [~tillw],

[jira] [Comment Edited] (ASTERIXDB-1556) Prefix-based multi-way Fuzzy-join generates an exception.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15406254#comment-15406254 ] Taewoo Kim edited comment on ASTERIXDB-1556 at 8/3/16 5:21 PM: --- (2)

[jira] [Commented] (ASTERIXDB-1556) Prefix-based multi-way Fuzzy-join generates an exception.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15406254#comment-15406254 ] Taewoo Kim commented on ASTERIXDB-1556: --- (2) spilling the data frame is already implemented. We

[jira] [Resolved] (ASTERIXDB-1569) The configuration file should support byte units (KB, MB, GB ...).

[ https://issues.apache.org/jira/browse/ASTERIXDB-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taewoo Kim resolved ASTERIXDB-1569. --- Resolution: Fixed > The configuration file should support byte units (KB, MB, GB ...). >

[jira] [Commented] (ASTERIXDB-1556) Hash Table used by External hash group-by doesn't conform to the budget.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15418031#comment-15418031 ] Taewoo Kim commented on ASTERIXDB-1556: --- Actually, we can think of the garbage collection

[jira] [Commented] (ASTERIXDB-1556) Hash Table used by External hash group-by doesn't conform to the budget.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420138#comment-15420138 ] Taewoo Kim commented on ASTERIXDB-1556: --- Regarding garbage collection of Hash Table, [~dtabass]

[jira] [Commented] (ASTERIXDB-1556) Hash Table used by External hash group-by doesn't conform to the budget.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420199#comment-15420199 ] Taewoo Kim commented on ASTERIXDB-1556: --- This is a good idea. But, the problem of generating

[jira] [Commented] (ASTERIXDB-1556) Hash Table used by External hash group-by doesn't conform to the budget.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15420486#comment-15420486 ] Taewoo Kim commented on ASTERIXDB-1556: --- Agreed. "separate hash table" in the bucket list! >

[jira] [Commented] (ASTERIXDB-1442) Global memory management is required

[ https://issues.apache.org/jira/browse/ASTERIXDB-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416128#comment-15416128 ] Taewoo Kim commented on ASTERIXDB-1442: --- Additional comment from ASTERIXDB-1566 discussion:

[jira] [Comment Edited] (ASTERIXDB-1442) Global memory management is required

[ https://issues.apache.org/jira/browse/ASTERIXDB-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15416128#comment-15416128 ] Taewoo Kim edited comment on ASTERIXDB-1442 at 8/10/16 10:22 PM: -

[jira] [Assigned] (ASTERIXDB-1569) The configuration file should support byte units (KB, MB, GB ...).

[ https://issues.apache.org/jira/browse/ASTERIXDB-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taewoo Kim reassigned ASTERIXDB-1569: - Assignee: Taewoo Kim > The configuration file should support byte units (KB, MB, GB

[jira] [Created] (ASTERIXDB-1569) The configuration file should support byte units (KB, MB, GB ...).

Taewoo Kim created ASTERIXDB-1569: - Summary: The configuration file should support byte units (KB, MB, GB ...). Key: ASTERIXDB-1569 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1569 Project:

[jira] [Commented] (ASTERIXDB-1513) Error in POM file after importing to eclipse

[ https://issues.apache.org/jira/browse/ASTERIXDB-1513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15364858#comment-15364858 ] Taewoo Kim commented on ASTERIXDB-1513: --- OK. Looks like I need to repeat the steps by myself. I

[jira] [Commented] (ASTERIXDB-1513) Error in POM file after importing to eclipse

[ https://issues.apache.org/jira/browse/ASTERIXDB-1513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15364694#comment-15364694 ] Taewoo Kim commented on ASTERIXDB-1513: --- Step 6 will solve your first issue. For the second

[jira] [Comment Edited] (ASTERIXDB-1513) Error in POM file after importing to eclipse

[ https://issues.apache.org/jira/browse/ASTERIXDB-1513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15364858#comment-15364858 ] Taewoo Kim edited comment on ASTERIXDB-1513 at 7/6/16 11:04 PM: OK.

[jira] [Resolved] (ASTERIXDB-1513) Error in POM file after importing to eclipse

[ https://issues.apache.org/jira/browse/ASTERIXDB-1513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taewoo Kim resolved ASTERIXDB-1513. --- Resolution: Fixed > Error in POM file after importing to eclipse >

[jira] [Commented] (ASTERIXDB-1513) Error in POM file after importing to eclipse

[ https://issues.apache.org/jira/browse/ASTERIXDB-1513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15368905#comment-15368905 ] Taewoo Kim commented on ASTERIXDB-1513: --- https://asterixdb.apache.org/dev-setup.html is updated.

[jira] [Commented] (ASTERIXDB-1513) Error in POM file after importing to eclipse

[ https://issues.apache.org/jira/browse/ASTERIXDB-1513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15362782#comment-15362782 ] Taewoo Kim commented on ASTERIXDB-1513: --- Sure. > Error in POM file after importing to eclipse >

[jira] [Commented] (ASTERIXDB-1513) Error in POM file after importing to eclipse

[ https://issues.apache.org/jira/browse/ASTERIXDB-1513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15362737#comment-15362737 ] Taewoo Kim commented on ASTERIXDB-1513: --- Till, I think Mike B's answer is correct. So, I posted

[jira] [Commented] (ASTERIXDB-1556) Prefix-based multi-way Fuzzy-join generates an exception.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15408840#comment-15408840 ] Taewoo Kim commented on ASTERIXDB-1556: --- My analysis so far on external-groupby: The hash table

[jira] [Commented] (ASTERIXDB-1556) Prefix-based multi-way Fuzzy-join generates an exception.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15408865#comment-15408865 ] Taewoo Kim commented on ASTERIXDB-1556: --- The number of possible hash values (= the number of

[jira] [Commented] (ASTERIXDB-1556) Prefix-based multi-way Fuzzy-join generates an exception.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15408966#comment-15408966 ] Taewoo Kim commented on ASTERIXDB-1556: --- Here, what does N (1 ... N) mean? The number of unique

[jira] [Commented] (ASTERIXDB-1556) Prefix-based multi-way Fuzzy-join generates an exception.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15408159#comment-15408159 ] Taewoo Kim commented on ASTERIXDB-1556: --- I actually copied that capitalized part from the board.

[jira] [Commented] (ASTERIXDB-1556) Prefix-based multi-way Fuzzy-join generates an exception.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15410337#comment-15410337 ] Taewoo Kim commented on ASTERIXDB-1556: --- A discussion summary with [~che...@gmail.com] and

[jira] [Commented] (ASTERIXDB-1556) Hash Table used by External hash group-by doesn't conform to the budget.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412200#comment-15412200 ] Taewoo Kim commented on ASTERIXDB-1556: --- One more thing regarding the hash table size (the

[jira] [Commented] (ASTERIXDB-1556) Hash Table used by External hash group-by doesn't conform to the budget.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15412348#comment-15412348 ] Taewoo Kim commented on ASTERIXDB-1556: --- The purpose of (4) is trying to prevent Hash Table

[jira] [Updated] (ASTERIXDB-1556) Hash Table used by External hash group-by doesn't conform to the budget.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taewoo Kim updated ASTERIXDB-1556: -- Summary: Hash Table used by External hash group-by doesn't conform to the budget. (was:

[jira] [Commented] (ASTERIXDB-1556) Prefix-based multi-way Fuzzy-join generates an exception.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15410513#comment-15410513 ] Taewoo Kim commented on ASTERIXDB-1556: --- For (4), we were concerned that hash table itself can

[jira] [Commented] (ASTERIXDB-1556) Hash Table used by External hash group-by doesn't conform to the budget.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15411087#comment-15411087 ] Taewoo Kim commented on ASTERIXDB-1556: --- The structure of SpillableTale used in external hash

[jira] [Commented] (ASTERIXDB-1556) Prefix-based multi-way Fuzzy-join generates an exception.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15403446#comment-15403446 ] Taewoo Kim commented on ASTERIXDB-1556: --- @Chen: thanks for the suggestion. > Prefix-based

[jira] [Commented] (ASTERIXDB-1556) Prefix-based multi-way Fuzzy-join generates an exception.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15403409#comment-15403409 ] Taewoo Kim commented on ASTERIXDB-1556: --- I have organized the flow of the hyracks job plan for a

[jira] [Commented] (ASTERIXDB-1779) Processing the certain function predicates after a simple predicates

[ https://issues.apache.org/jira/browse/ASTERIXDB-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849082#comment-15849082 ] Taewoo Kim commented on ASTERIXDB-1779: --- [~tillw]: I just had a short conversation with

[jira] [Commented] (ASTERIXDB-1779) Processing the certain function predicates after a simple predicates

[ https://issues.apache.org/jira/browse/ASTERIXDB-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849171#comment-15849171 ] Taewoo Kim commented on ASTERIXDB-1779: --- Regarding the description, I agree. But, we never

[jira] [Commented] (ASTERIXDB-1778) Calculating the edit-distance in SimilarityMetricEditDistance class can be improved.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849528#comment-15849528 ] Taewoo Kim commented on ASTERIXDB-1778: --- Actually, I was wrong about the output. Currently, if

[jira] [Commented] (ASTERIXDB-1779) Processing the certain function predicates after a simple predicates

[ https://issues.apache.org/jira/browse/ASTERIXDB-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849197#comment-15849197 ] Taewoo Kim commented on ASTERIXDB-1779: --- I just had an another short conversation with

[jira] [Commented] (ASTERIXDB-1779) Processing the certain function predicates after a simple predicates

[ https://issues.apache.org/jira/browse/ASTERIXDB-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15849529#comment-15849529 ] Taewoo Kim commented on ASTERIXDB-1779: --- [~dtabass]: will check those papers. > Processing the

[jira] [Assigned] (ASTERIXDB-1778) Calculating the edit-distance in SimilarityMetricEditDistance class can be improved.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taewoo Kim reassigned ASTERIXDB-1778: - Assignee: Taewoo Kim > Calculating the edit-distance in SimilarityMetricEditDistance

[jira] [Comment Edited] (ASTERIXDB-1778) Calculating the edit-distance in SimilarityMetricEditDistance class can be improved.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15848036#comment-15848036 ] Taewoo Kim edited comment on ASTERIXDB-1778 at 2/1/17 6:09 AM: --- Got a

[jira] [Comment Edited] (ASTERIXDB-1778) Calculating the edit-distance in SimilarityMetricEditDistance class can be improved.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15848048#comment-15848048 ] Taewoo Kim edited comment on ASTERIXDB-1778 at 2/1/17 5:59 AM: --- Agreed.

[jira] [Commented] (ASTERIXDB-1778) Calculating the edit-distance in SimilarityMetricEditDistance class can be improved.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15848048#comment-15848048 ] Taewoo Kim commented on ASTERIXDB-1778: --- Agreed. Checked the code and it reflects both

[jira] [Updated] (ASTERIXDB-1778) Calculating the edit-distance in SimilarityMetricEditDistance class can be improved.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taewoo Kim updated ASTERIXDB-1778: -- Description: Local optimization of the current edit-distance handling code in AsterixDB:

[jira] [Commented] (ASTERIXDB-1778) Calculating the edit-distance in SimilarityMetricEditDistance class can be improved.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15848036#comment-15848036 ] Taewoo Kim commented on ASTERIXDB-1778: --- Got a hint from

[jira] [Commented] (ASTERIXDB-1778) Calculating the edit-distance in SimilarityMetricEditDistance class can be improved.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15848037#comment-15848037 ] Taewoo Kim commented on ASTERIXDB-1778: --- >From [~che...@gmail.com]: Earlier we had two released

[jira] [Created] (ASTERIXDB-1778) Calculating the edit-distance in SimilarityMetricEditDistance class can be improved.

Taewoo Kim created ASTERIXDB-1778: - Summary: Calculating the edit-distance in SimilarityMetricEditDistance class can be improved. Key: ASTERIXDB-1778 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1778

[jira] [Created] (ASTERIXDB-1779) Processing the certain function predicates after a simple predicates

Taewoo Kim created ASTERIXDB-1779: - Summary: Processing the certain function predicates after a simple predicates Key: ASTERIXDB-1779 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1779

[jira] [Updated] (ASTERIXDB-1779) Processing the certain function predicates after a simple predicates

[ https://issues.apache.org/jira/browse/ASTERIXDB-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taewoo Kim updated ASTERIXDB-1779: -- Description: For example, if we have the following AQL query, {code} for $i in dataset

[jira] [Closed] (ASTERIXDB-1778) Calculating the edit-distance in SimilarityMetricEditDistance class can be improved.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taewoo Kim closed ASTERIXDB-1778. - Resolution: Fixed > Calculating the edit-distance in SimilarityMetricEditDistance class can

[jira] [Commented] (ASTERIXDB-1779) Processing the certain function predicates after a simple predicates

[ https://issues.apache.org/jira/browse/ASTERIXDB-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15848741#comment-15848741 ] Taewoo Kim commented on ASTERIXDB-1779: --- [~tillw]: Actually, my example is wrong. I need to

[jira] [Comment Edited] (ASTERIXDB-1779) Processing the certain function predicates after a simple predicates

[ https://issues.apache.org/jira/browse/ASTERIXDB-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15848791#comment-15848791 ] Taewoo Kim edited comment on ASTERIXDB-1779 at 2/1/17 7:04 PM: --- Certain

[jira] [Commented] (ASTERIXDB-1779) Processing the certain function predicates after a simple predicates

[ https://issues.apache.org/jira/browse/ASTERIXDB-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15848809#comment-15848809 ] Taewoo Kim commented on ASTERIXDB-1779: --- More info: why the original orders are changed in the

[jira] [Comment Edited] (ASTERIXDB-1779) Processing the certain function predicates after a simple predicates

[ https://issues.apache.org/jira/browse/ASTERIXDB-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15848741#comment-15848741 ] Taewoo Kim edited comment on ASTERIXDB-1779 at 2/1/17 6:24 PM: ---

[jira] [Comment Edited] (ASTERIXDB-1779) Processing the certain function predicates after a simple predicates

[ https://issues.apache.org/jira/browse/ASTERIXDB-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15848791#comment-15848791 ] Taewoo Kim edited comment on ASTERIXDB-1779 at 2/1/17 7:05 PM: --- Certain

[jira] [Commented] (ASTERIXDB-1778) Calculating the edit-distance in SimilarityMetricEditDistance class can be improved.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15848753#comment-15848753 ] Taewoo Kim commented on ASTERIXDB-1778: --- Actually, if we apply the early termination logic, we

[jira] [Commented] (ASTERIXDB-1779) Processing the certain function predicates after a simple predicates

[ https://issues.apache.org/jira/browse/ASTERIXDB-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15848791#comment-15848791 ] Taewoo Kim commented on ASTERIXDB-1779: --- Certain functions - especially text functions and

[jira] [Created] (ASTERIXDB-1802) Add a download functionality to the WebUI

Taewoo Kim created ASTERIXDB-1802: - Summary: Add a download functionality to the WebUI Key: ASTERIXDB-1802 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1802 Project: Apache AsterixDB

[jira] [Commented] (ASTERIXDB-1791) HyracksDataException: Premature file in Join operator

[ https://issues.apache.org/jira/browse/ASTERIXDB-1791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15864152#comment-15864152 ] Taewoo Kim commented on ASTERIXDB-1791: --- The truncated file (partition) is re-read to do an

[jira] [Commented] (ASTERIXDB-1762) AQL+ needs to be revised.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15829372#comment-15829372 ] Taewoo Kim commented on ASTERIXDB-1762: --- Step 1 of 2 done: Add a new rule controller.

[jira] [Closed] (ASTERIXDB-1766) Address comments in full-text implementation step 3

[ https://issues.apache.org/jira/browse/ASTERIXDB-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taewoo Kim closed ASTERIXDB-1766. - Resolution: Fixed https://asterix-gerrit.ics.uci.edu/#/c/1422/ > Address comments in

[jira] [Closed] (ASTERIXDB-1663) The memory consumption of Hash Table used in Hash-Join is not controlled.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taewoo Kim closed ASTERIXDB-1663. - Resolution: Fixed https://asterix-gerrit.ics.uci.edu/#/c/1056/ > The memory consumption of

[jira] [Closed] (ASTERIXDB-1435) Massive operators will induce a heap error that should not be.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taewoo Kim closed ASTERIXDB-1435. - Resolution: Fixed https://asterix-gerrit.ics.uci.edu/#/c/1056/ > Massive operators will

[jira] [Closed] (ASTERIXDB-1208) ngram tokenizer failure with negative length

[ https://issues.apache.org/jira/browse/ASTERIXDB-1208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taewoo Kim closed ASTERIXDB-1208. - Resolution: Fixed https://asterix-gerrit.ics.uci.edu/#/c/1448/ > ngram tokenizer failure

[jira] [Commented] (ASTERIXDB-1234) Currently allowing (and botching) non-atomic field comparisons

[ https://issues.apache.org/jira/browse/ASTERIXDB-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427279#comment-15427279 ] Taewoo Kim commented on ASTERIXDB-1234: --- Got it. Thanks. > Currently allowing (and botching)

[jira] [Commented] (ASTERIXDB-1086) IntroduceProjectsRule creates a wrong PROJECT operator when there are multiple paths.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427229#comment-15427229 ] Taewoo Kim commented on ASTERIXDB-1086: --- This is part of index-only change and is uploaded as a

[jira] [Commented] (ASTERIXDB-866) Incorrect query results possible when accessing secondary indexes

[ https://issues.apache.org/jira/browse/ASTERIXDB-866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427211#comment-15427211 ] Taewoo Kim commented on ASTERIXDB-866: -- We may need to apply this approach - apply DISTINCT after

[jira] [Commented] (ASTERIXDB-1234) Currently allowing (and botching) non-atomic field comparisons

[ https://issues.apache.org/jira/browse/ASTERIXDB-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427252#comment-15427252 ] Taewoo Kim commented on ASTERIXDB-1234: --- I vaguely remember [~buyingyi] did some work on null

[jira] [Commented] (ASTERIXDB-1246) Unnecessary decor variables of a group-by are not removed until PushProjectDownRule is fired.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427256#comment-15427256 ] Taewoo Kim commented on ASTERIXDB-1246: --- This is part of index-only change and is uploaded as a

[jira] [Commented] (ASTERIXDB-1186) Index Join Hint on an index with composite keys causes query to return incorrect results

[ https://issues.apache.org/jira/browse/ASTERIXDB-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427237#comment-15427237 ] Taewoo Kim commented on ASTERIXDB-1186: --- https://issues.apache.org/jira/browse/ASTERIXDB-920 and

[jira] [Commented] (ASTERIXDB-1186) Index Join Hint on an index with composite keys causes query to return incorrect results

[ https://issues.apache.org/jira/browse/ASTERIXDB-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427581#comment-15427581 ] Taewoo Kim commented on ASTERIXDB-1186: --- Sure. The common part is "composite PK". But, this is

[jira] [Commented] (ASTERIXDB-920) Wrong results for a primary index with composite keys

[ https://issues.apache.org/jira/browse/ASTERIXDB-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427573#comment-15427573 ] Taewoo Kim commented on ASTERIXDB-920: -- 1186 is about exchange. This is about false positive

[jira] [Commented] (ASTERIXDB-1186) Index Join Hint on an index with composite keys causes query to return incorrect results

[ https://issues.apache.org/jira/browse/ASTERIXDB-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15427356#comment-15427356 ] Taewoo Kim commented on ASTERIXDB-1186: --- The result on the current master is Interesting: the

[jira] [Commented] (ASTERIXDB-1556) Hash Table used by External hash group-by doesn't conform to the budget.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15421927#comment-15421927 ] Taewoo Kim commented on ASTERIXDB-1556: --- I just uploaded a patch set that solves the priority #1

[jira] [Commented] (ASTERIXDB-1556) Hash Table used by External hash group-by doesn't conform to the budget.

[ https://issues.apache.org/jira/browse/ASTERIXDB-1556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15422073#comment-15422073 ] Taewoo Kim commented on ASTERIXDB-1556: --- I like that idea. However, for the compatibility

[jira] [Commented] (ASTERIXDB-1186) Index Join Hint on an index with composite keys causes query to return incorrect results

[ https://issues.apache.org/jira/browse/ASTERIXDB-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15429157#comment-15429157 ] Taewoo Kim commented on ASTERIXDB-1186: --- I have uploaded a patch set:

[jira] [Closed] (ASTERIXDB-1077) Inverted index tests are slow compared to others

[ https://issues.apache.org/jira/browse/ASTERIXDB-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Taewoo Kim closed ASTERIXDB-1077. - Resolution: Fixed Assignee: Taewoo Kim (was: Chen Li) > Inverted index tests are slow

  1   2   3   4   >