[
https://issues.apache.org/jira/browse/PHOENIX-5156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16779083#comment-16779083
]
Kadir OZDEMIR commented on PHOENIX-5156:
----------------------------------------
[~lhofhansl], I was thinking more about your comment on the scan operations on
the client side versus server side (i.e., coprocessor). The proposed solution
suggests the following:
"For reads, the Indexer coprocessor will implement the preScannerNext hook to
check if the VERIFIED column value is false. If so, it retrieves the scanned
columns from the data table. A scan attribute should specify if VERIFIED column
should be checked. If so, another scan attribute should include the physical
data table name and some metadata so that the coprocessor can retrieve the
columns from the data table."
Regardless if the scan is issued on the client side or server side, would not
the Indexer coprocessor intercept the scan operation ? if so, does not this
cover both client and server side scan operations?
> Consistent Global Indexes for Non-Transactional Tables
> ------------------------------------------------------
>
> Key: PHOENIX-5156
> URL: https://issues.apache.org/jira/browse/PHOENIX-5156
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.13.0, 4.14.0, 5.0.0, 4.14.1
> Reporter: Kadir OZDEMIR
> Assignee: Kadir OZDEMIR
> Priority: Major
>
> Without transactional tables, the global indexes can get easily out of sync
> with their data tables in Phoenix. Transactional tables require a separate
> transaction manager, have some restrictions and performance penalties. This
> issue is to have consistent global indexes without the need for using
> transactional tables.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
