[jira] [Created] (OMID-109) Change repo URL

2018-08-10 Thread James Taylor (JIRA)
James Taylor created OMID-109:
-

 Summary: Change repo URL
 Key: OMID-109
 URL: https://issues.apache.org/jira/browse/OMID-109
 Project: Apache Omid
  Issue Type: Bug
Reporter: James Taylor


Based on Jenkins job failures 
(https://builds.apache.org/job/Phoenix-omid2/81/), the repo URL in the pom 
needs to be updated to 
https://raw.githubusercontent.com/synergian/wagon-git/releases.



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


[jira] [Updated] (OMID-109) Change repo URL

2018-08-10 Thread James Taylor (JIRA)


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

James Taylor updated OMID-109:
--
Attachment: OMID-109.patch

> Change repo URL
> ---
>
> Key: OMID-109
> URL: https://issues.apache.org/jira/browse/OMID-109
> Project: Apache Omid
>  Issue Type: Bug
>Reporter: James Taylor
>Priority: Major
> Attachments: OMID-109.patch
>
>
> Based on Jenkins job failures 
> (https://builds.apache.org/job/Phoenix-omid2/81/), the repo URL in the pom 
> needs to be updated to 
> https://raw.githubusercontent.com/synergian/wagon-git/releases.



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


[jira] [Commented] (OMID-109) Change repo URL

2018-08-10 Thread James Taylor (JIRA)


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

James Taylor commented on OMID-109:
---

[~ohads] - please review and commit if it looks good. This should fix our 
Jenkins build failures.

> Change repo URL
> ---
>
> Key: OMID-109
> URL: https://issues.apache.org/jira/browse/OMID-109
> Project: Apache Omid
>  Issue Type: Bug
>Reporter: James Taylor
>Priority: Major
> Attachments: OMID-109.patch
>
>
> Based on Jenkins job failures 
> (https://builds.apache.org/job/Phoenix-omid2/81/), the repo URL in the pom 
> needs to be updated to 
> https://raw.githubusercontent.com/synergian/wagon-git/releases.



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


[jira] [Commented] (OMID-102) Implement visibility filter as pure HBase Filter

2018-08-10 Thread James Taylor (JIRA)


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

James Taylor commented on OMID-102:
---

Thanks, [~mujtabachohan]. FYI, [~ohads] & [~yonigo] - I've filed OMID-109 and 
included a patch there to fix this.

> Implement visibility filter as pure HBase Filter
> 
>
> Key: OMID-102
> URL: https://issues.apache.org/jira/browse/OMID-102
> Project: Apache Omid
>  Issue Type: Sub-task
>Reporter: James Taylor
>Assignee: Yonatan Gottesman
>Priority: Major
>
> The way Omid currently filters through it's own RegionScanner won't work the 
> way it's implemented (i.e. the way the filtering is done *after* the next 
> call). The reason is that the state of HBase filters get messed up since 
> these filters will start to see cells that it shouldn't (i.e. cells that 
> would be filtered based on snapshot isolation). It cannot be worked around by 
> manually running filters afterwards because filters may issue seek calls 
> which are handled during the running of scans by HBase.
>  
> Instead, the filtering needs to be implemented as a pure HBase filter and 
> that filter needs to delegate to the other, delegate filter once it's 
> determined that the cell is visible. See Tephra's TransactionVisibilityFilter 
> and they way it calls the delegate filter (cellFilters) only after it's 
> determined that the cell is visible. You may run into TEPHRA-169 without 
> including the CellSkipFilter too. 
> Because it'll be easier if you see shadow cells *before* their corresponding 
> real cells you can prefix instead of suffix the column qualifiers to 
> guarantee that you'd see the shadow cells prior to the actual cells. Or you 
> could buffer cells in your filter prior to omitting them. Another issue would 
> be if the shadow cells aren't found and you need to consult the commit table 
> - I suppose if the shadow cells are first, this logic would be easier to know 
> when it needs to be called.
>  
> To reproduce, see the Phoenix unit tests 
> FlappingTransactionIT.testInflightUpdateNotSeen() and 
> testInflightDeleteNotSeen().



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