clear query| facets| time Search criteria: .   Results from 1 to 10 from 38 (0.0s).
Loading phrases to help you
refine your search...
[PHOENIX-4953] DefaultStatisticsCollector fails to capture the last guidepost of every region - Phoenix - [issue]
...The issue was found during a sanity test run when the count of all rows from all the guideposts didn't match the actual number of rows in the table. DefaultStatisticsCollector#collectStatist...    Author: Karan Mehta , 2018-10-08, 17:15
[PHOENIX-4954] RowCounter logic for DefaultStatisticsCollector is incorrect for tables with multiple CF - Phoenix - [issue]
...DefaultStatisticsCollector#collectStatistics() method increments a counter to keep track of unique rows that has been read. However, currently we increment the counter twice for a table with...    Author: Karan Mehta , 2018-10-05, 00:08
[PHOENIX-4950] SYSTEM.STATS table should include the stopKey of guide posts - Phoenix - [issue]
...SYSTEM.STATS table should include stop key for each guidepost along with start key. This helps in determining if there are any gaps/holes in the statistics. UPDATE STATISTICS creates separat...    Author: Karan Mehta , 2018-10-04, 18:47
[PHOENIX-4851] Update branch names in for 4.14-HBase-1.4 for Hadoop QA run - Phoenix - [issue]    Author: Karan Mehta , 2018-09-28, 18:32
[PHOENIX-4805] Move Avatica version to 1.12 for PQS - Phoenix - [issue]
...CALCITE-2330 is now resolved. We can use the new version for supporting new features such as MTLS authentication and server customization in PQS....    Author: Karan Mehta , 2018-09-28, 18:29
[PHOENIX-4755] Provide an option to plugin custom avatica server config in PQS - Phoenix - [issue]
...CALCITE-2294 Allow customization for AvaticaServerConfiguration for plugging new authentication mechanismsAdd a new Phoenix level property and provide resolve the class using InstanceResolve...    Author: Karan Mehta , 2018-09-24, 15:30
[PHOENIX-4854] Make LoggingPhoenixResultSet idempotent when logging metrics - Phoenix - [issue]
...ResultSet close method can be called multiple times and LoggingResultSet object tries to call PhoenixMetricsLog methods every single time. These per query metrics don't get cleared up, rathe...    Author: Karan Mehta , 2018-09-24, 15:30
[PHOENIX-4853] Add sql statement to PhoenixMetricsLog interface for query level metrics logging - Phoenix - [issue]
...We get query level metrics when we try to close the LoggingPhoenixResultSet object. It is better to add the SQL statement to the PhoenixMetricsLog interface so that we can attach the metrics...    Author: Karan Mehta , 2018-09-24, 15:30
[PHOENIX-4835] LoggingPhoenixConnection should log metrics upon connection close - Phoenix - [issue]
...LoggingPhoenixConnection currently logs metrics upon commit(), which may miss the logging of metrics sometimes if commit is never called. We should move it to close() method instead....    Author: Karan Mehta , 2018-09-24, 15:30
[PHOENIX-4834] PhoenixMetricsLog interface methods should not depend on specific logger - Phoenix - [issue]
...PhoenixMetricsLog is an interface that provides a wrapper around various JDBC objects with logging functionality upon close/commit. The methods take in Logger as an input, which is org.slf4j...    Author: Karan Mehta , 2018-09-24, 15:29