[jira] [Commented] (ASTERIXDB-1012) About correlated-prefix merge policy behavior

[Chen Luo (JIRA)]

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

Chen Luo commented on ASTERIXDB-1012:
-

[~buyingyi] I think so. If there is merge operation going on for some secondary 
index, it would be ignored for this round of merge. But that secondary index 
would be considered as lagged during the next flush, thus forcing the data 
ingestion to stop.

> About correlated-prefix merge policy behavior
> -
>
> Key: ASTERIXDB-1012
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1012
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: *DB - AsterixDB, STO - Storage
>Reporter: asterixdb-importer
>Assignee: Chen Luo
>Priority: Minor
>  Labels: soon
>
> About correlated-prefix merge policy behavior



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

[jira] [Commented] (ASTERIXDB-1012) About correlated-prefix merge policy behavior

[Yingyi Bu (JIRA)]

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

Yingyi Bu commented on ASTERIXDB-1012:
--

[~luochen01], this issue should have been fixed already?

> About correlated-prefix merge policy behavior
> -
>
> Key: ASTERIXDB-1012
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1012
> Project: Apache AsterixDB
>  Issue Type: Bug
>  Components: *DB - AsterixDB, STO - Storage
>Reporter: asterixdb-importer
>Assignee: Chen Luo
>Priority: Minor
>  Labels: soon
>
> About correlated-prefix merge policy behavior



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