[jira] [Created] (PHOENIX-3871) Incremental stats collection

Eli Levine created PHOENIX-3871: --- Summary: Incremental stats collection Key: PHOENIX-3871 URL: https://issues.apache.org/jira/browse/PHOENIX-3871 Project: Phoenix Issue Type: Improvement

[jira] [Commented] (PHOENIX-3744) Support snapshot scanners for MR-based queries

[ https://issues.apache.org/jira/browse/PHOENIX-3744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15935579#comment-15935579 ] Eli Levine commented on PHOENIX-3744: - Thanks for the @-mention, [~giacomotay...@gmail.com

Re: [ANNOUNCE] New Apache Phoenix committer - Geoffrey Jacoby

Congrats and welcome! On Tue, Feb 28, 2017 at 1:08 PM Mujtaba Chohan wrote: > Congrats Geoffrey! > > On Tue, Feb 28, 2017 at 1:05 PM, Josh Elser wrote: > > > Congrats, Geoffrey! Well deserved! > > > > > > James Taylor wrote: > > > >> On behalf of the

Re: [ANNOUNCE] Ankit Singhal added as Apache Phoenix committer

Congrats! > On Feb 2, 2016, at 3:46 PM, Jesse Yates wrote: > > Congrats and welcome! > >> On Tue, Feb 2, 2016 at 3:44 PM Mujtaba Chohan wrote: >> >> Congrats!! :) >> >> On Tue, Feb 2, 2016 at 3:41 PM, Thomas D'Silva >>

Re: [ANNOUNCE] Thomas D'Silva added to Apache Phoenix PMC

Well done, Thomas. Congrats! > On Nov 22, 2015, at 4:37 PM, Andrew Purtell wrote: > > Congratulations Thomas. > >> On Nov 22, 2015, at 11:39 AM, Nick Dimiduk wrote: >> >> Congrats Thomas! >> >> On Sunday, November 22, 2015,

Re: [ANNOUNCE] Thomas D'Silva added to Apache Phoenix PMC

> On Nov 22, 2015, at 11:39 AM, Nick Dimiduk wrote: > > Congrats Thomas! > > On Sunday, November 22, 2015, rajeshb...@apache.org < > chrajeshbab...@gmail.com> wrote: > >> Great job. Congratulations Thomas!!! >> >> On Sun, Nov 22, 2015 at 10:21 AM, James Taylor

[jira] [Commented] (PHOENIX-2429) PhoenixConfigurationUtil.CURRENT_SCN_VALUE for phoenix-spark plugin does not work

[ https://issues.apache.org/jira/browse/PHOENIX-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15014226#comment-15014226 ] Eli Levine commented on PHOENIX-2429: - [~prkommireddi], FYI. Looks like there might be an issue

[jira] [Commented] (PHOENIX-2431) Make SYSTEM.CATALOG table transactional

[ https://issues.apache.org/jira/browse/PHOENIX-2431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15014219#comment-15014219 ] Eli Levine commented on PHOENIX-2431: - There is code that allows add/drop columns on tables

Re: [ANNOUNCE] Josh Mahonin added to Apache Phoenix PMC

Congrats, Josh! On Mon, Nov 9, 2015 at 10:03 AM, Ravi Kiran wrote: > Congratulations Josh!! > > On Sun, Nov 8, 2015 at 12:35 PM, Andrew Purtell > wrote: > > > Congratulations Josh! > > > > On Sat, Nov 7, 2015 at 5:25 PM, James Taylor

Re: [VOTE] Release of Apache Phoenix 4.6.0-HBase-0.98 RC0

+1 Tested for regressions using internal Salesforce use-cases. Looks good! On Mon, Oct 19, 2015 at 4:33 PM, Samarth Jain wrote: > Hi Everyone, > > This is a call for a vote on Apache Phoenix 4.6.0-HBase-0.98 RC0. This is a > patch release of Phoenix 4, compatible with the

[ANNOUNCE] New Apache Phoenix committer - Jan Fernando

visibility into Phoenix internals. Look forward to continuing working with Jan on Apache Phoenix! Thanks, Eli Levine elilev...@apache.org

Re: [ANNOUNCE] Welcome our newest Committer Dumindu Buddhika

Welcome, Dumindu! On Fri, Sep 18, 2015 at 9:33 AM, Thomas D'Silva wrote: > Congrats Dumindu! > > On Fri, Sep 18, 2015 at 8:56 AM, Jesse Yates > wrote: > > Welcome and congrats! > > > > On Fri, Sep 18, 2015 at 8:27 AM rajeshb...@apache.org < > >

[jira] [Commented] (PHOENIX-2214) ORDER BY optimization incorrect for queries over views containing WHERE clause

[ https://issues.apache.org/jira/browse/PHOENIX-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14717149#comment-14717149 ] Eli Levine commented on PHOENIX-2214: - Come to think of it, ORDER BY can

[jira] [Updated] (PHOENIX-2214) ORDER BY optimization incorrect for queries over views containing WHERE clause

[ https://issues.apache.org/jira/browse/PHOENIX-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Levine updated PHOENIX-2214: Attachment: 0001-Test-case-to-outline-issue-with-view-ORDER-BY-optimi.patch ORDER

[jira] [Created] (PHOENIX-2214) ORDER BY optimization incorrect for queries over views containing WHERE clause

Eli Levine created PHOENIX-2214: --- Summary: ORDER BY optimization incorrect for queries over views containing WHERE clause Key: PHOENIX-2214 URL: https://issues.apache.org/jira/browse/PHOENIX-2214

[jira] [Updated] (PHOENIX-2214) ORDER BY optimization incorrect for queries over views containing WHERE clause

[ https://issues.apache.org/jira/browse/PHOENIX-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Levine updated PHOENIX-2214: Affects Version/s: 4.5.1 ORDER BY optimization incorrect for queries over views containing WHERE

Re: [VOTE] Release of Apache Phoenix 4.5.1-HBase-0.98 RC1

+1 on the release. - Tried 4.5.1-HBase-0.98 RC1 using binary artifacts. Ran the jars through a bunch of internal Salesforce tests, everything checks out. - Verified that PHOENIX-2177 is fixed in this release. Admin.modifyTable() is no longer invoked on column creation for views. No more

[jira] [Commented] (PHOENIX-2177) Adding a column to the view shouldn't call admin.modifyTable() for the base table.

[ https://issues.apache.org/jira/browse/PHOENIX-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14700108#comment-14700108 ] Eli Levine commented on PHOENIX-2177: - Makes sense, thanks. Adding a column

[jira] [Commented] (PHOENIX-2177) Adding a column to the view shouldn't call admin.modifyTable() for the base table.

[ https://issues.apache.org/jira/browse/PHOENIX-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14700071#comment-14700071 ] Eli Levine commented on PHOENIX-2177: - Curious, what's the reason to call

[jira] [Commented] (PHOENIX-2177) Adding a column to the view shouldn't call admin.modifyTable() for the base table.

[ https://issues.apache.org/jira/browse/PHOENIX-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14694540#comment-14694540 ] Eli Levine commented on PHOENIX-2177: - Looks good, [~samarthjain]. Thanks

[jira] [Commented] (PHOENIX-1673) Allow tenant ID to be of any integral data type

[ https://issues.apache.org/jira/browse/PHOENIX-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14680632#comment-14680632 ] Eli Levine commented on PHOENIX-1673: - [~neverendingqs], there is a discussion

[jira] [Commented] (PHOENIX-1779) Parallelize fetching of next batch of records for scans corresponding to queries with no order by

[ https://issues.apache.org/jira/browse/PHOENIX-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14622640#comment-14622640 ] Eli Levine commented on PHOENIX-1779: - I think you are right. If RVCs are used

[jira] [Commented] (PHOENIX-1779) Parallelize fetching of next batch of records for scans corresponding to queries with no order by

[ https://issues.apache.org/jira/browse/PHOENIX-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14622586#comment-14622586 ] Eli Levine commented on PHOENIX-1779: - Going through some code that uses row-value

[jira] [Commented] (PHOENIX-978) Allow views to extend base table's PK (only if last PK column is fixed length)

[ https://issues.apache.org/jira/browse/PHOENIX-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14620929#comment-14620929 ] Eli Levine commented on PHOENIX-978: Thanks for the comments, [~jamestaylor

[jira] [Commented] (PHOENIX-978) Allow views to extend base table's PK (only if last PK column is fixed length)

[ https://issues.apache.org/jira/browse/PHOENIX-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14619770#comment-14619770 ] Eli Levine commented on PHOENIX-978: [~tdsilva], can you take a look at the pull

[jira] [Updated] (PHOENIX-978) Allow views to extend base table's PK (only if last PK column is fixed length)

[ https://issues.apache.org/jira/browse/PHOENIX-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Levine updated PHOENIX-978: --- Summary: Allow views to extend base table's PK (only if last PK column is fixed length) (was: Allow

[jira] [Commented] (PHOENIX-978) Allow views to extend base table's PK

[ https://issues.apache.org/jira/browse/PHOENIX-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14619693#comment-14619693 ] Eli Levine commented on PHOENIX-978: [~tdsilva], many thanks for finding the issue

[jira] [Commented] (PHOENIX-978) Allow views to extend base table's PK (only if last PK column is fixed length)

[ https://issues.apache.org/jira/browse/PHOENIX-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14619730#comment-14619730 ] Eli Levine commented on PHOENIX-978: Working on fixing AlterTableIT now... Allow

[jira] [Commented] (PHOENIX-1673) Allow tenant ID to be of any integral data type

[ https://issues.apache.org/jira/browse/PHOENIX-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14615655#comment-14615655 ] Eli Levine commented on PHOENIX-1673: - Appreciate the help, [~Jeffrey.Lyons]. I

[jira] [Commented] (PHOENIX-978) Allow views to extend base table's PK

[ https://issues.apache.org/jira/browse/PHOENIX-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14604386#comment-14604386 ] Eli Levine commented on PHOENIX-978: [~jamestaylor], mind taking a look at the pull

[jira] [Commented] (PHOENIX-978) Allow views to extend base table's PK

[ https://issues.apache.org/jira/browse/PHOENIX-978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14604414#comment-14604414 ] Eli Levine commented on PHOENIX-978: Ah, thanks for pointing out PHOENIX-2058. I'll

[jira] [Updated] (PHOENIX-2058) Check for existence and compatibility of columns being added in view

[ https://issues.apache.org/jira/browse/PHOENIX-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Levine updated PHOENIX-2058: Description: One check I realized we're not doing, but need to do, is ensuring that the column

[jira] [Updated] (PHOENIX-978) Allow views to extend base table's PK

[ https://issues.apache.org/jira/browse/PHOENIX-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Levine updated PHOENIX-978: --- Attachment: PHOENIX-978.diff Allow views to extend base table's PK

[jira] [Assigned] (PHOENIX-978) Allow views to extend base table's PK

[ https://issues.apache.org/jira/browse/PHOENIX-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Levine reassigned PHOENIX-978: -- Assignee: Eli Levine Allow views to extend base table's PK

[jira] [Updated] (PHOENIX-978) Allow views to extend base table's PK

[ https://issues.apache.org/jira/browse/PHOENIX-978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Levine updated PHOENIX-978: --- Fix Version/s: 4.5.0 5.0.0 Allow views to extend base table's PK

Re: thinking about cutting an RC for 4.5.0 soon

I'll pick PHOENIX-978 up. Shooting for getting it in early next week. Thanks, Eli On Mon, Jun 22, 2015 at 10:36 AM, James Taylor jamestay...@apache.org wrote: We'd like to cut the RC and start the vote next week. Thanks, James On Mon, Jun 22, 2015 at 10:29 AM, Eli Levine elilev

Re: [ANNOUNCE] Josh Mahonin added as Apache Phoenix committer

Welcome, Josh! On Tue, Jun 23, 2015 at 1:03 PM, Thomas D'Silva tdsi...@salesforce.com wrote: Welcome Josh! On Tue, Jun 23, 2015 at 10:24 AM, Samarth Jain sama...@apache.org wrote: Congratulations and welcome, Josh. On Tuesday, June 23, 2015, Gabriel Reid gabriel.r...@gmail.com wrote:

Re: thinking about cutting an RC for 4.5.0 soon

I was hoping to get https://issues.apache.org/jira/browse/PHOENIX-978 into 4.5, which Jan Fernando (CC'd) is planning to tackle. James, what is your time-frame for getting 4.5 out? Thanks, Eli On Sun, Jun 21, 2015 at 2:11 PM, James Taylor jamestay...@apache.org wrote: Please let me know if

[jira] [Commented] (PHOENIX-1981) PhoenixHBase Load and Store Funcs should handle all Pig data types

[ https://issues.apache.org/jira/browse/PHOENIX-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14588200#comment-14588200 ] Eli Levine commented on PHOENIX-1981: - This is now in master. Will do the rest later

[jira] [Created] (PHOENIX-1961) Tenant-specific View TTLs

Eli Levine created PHOENIX-1961: --- Summary: Tenant-specific View TTLs Key: PHOENIX-1961 URL: https://issues.apache.org/jira/browse/PHOENIX-1961 Project: Phoenix Issue Type: Bug

[jira] [Resolved] (PHOENIX-900) Partial results for mutations

[ https://issues.apache.org/jira/browse/PHOENIX-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Levine resolved PHOENIX-900. Resolution: Fixed Partial results for mutations

[jira] [Commented] (PHOENIX-900) Partial results for mutations

[ https://issues.apache.org/jira/browse/PHOENIX-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14507415#comment-14507415 ] Eli Levine commented on PHOENIX-900: [~samarthjain] Sorry about that. Fixing it now

[jira] [Commented] (PHOENIX-1682) PhoenixRuntime.getTable() does not work with case-sensitive table names

[ https://issues.apache.org/jira/browse/PHOENIX-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14508047#comment-14508047 ] Eli Levine commented on PHOENIX-1682: - Just pushed fixes from [~ivanweiss] to master

[jira] [Commented] (PHOENIX-900) Partial results for mutations

[ https://issues.apache.org/jira/browse/PHOENIX-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14506141#comment-14506141 ] Eli Levine commented on PHOENIX-900: It was a bug in my original PR that caused

[jira] [Commented] (PHOENIX-1834) Collect row counts per tenant view

[ https://issues.apache.org/jira/browse/PHOENIX-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14493627#comment-14493627 ] Eli Levine commented on PHOENIX-1834: - This is a great first step. +1 on making

[jira] [Commented] (PHOENIX-1682) PhoenixRuntime.getTable() does not work with case-sensitive table names

[ https://issues.apache.org/jira/browse/PHOENIX-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14494985#comment-14494985 ] Eli Levine commented on PHOENIX-1682: - I think that's the fix, yeah

Re: PHOENIX-1452 in 4.3.1 ?

There was a long thread a few months ago on private@ on the semantics of different types of branches in Phoenix and there seemed to be consensus (or at least no disagreement) that point releases (e.g. 4.3.1 - 4.3.2) should only contain bug fixes with this exception: Possibly minor features that

[jira] [Commented] (PHOENIX-900) Partial results for mutations

[ https://issues.apache.org/jira/browse/PHOENIX-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340650#comment-14340650 ] Eli Levine commented on PHOENIX-900: Just reverted both main and 4.0. Will take

[jira] [Commented] (PHOENIX-900) Partial results for mutations

[ https://issues.apache.org/jira/browse/PHOENIX-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14340631#comment-14340631 ] Eli Levine commented on PHOENIX-900: Looking at it now. Will fix or revert today

[jira] [Reopened] (PHOENIX-900) Partial results for mutations

[ https://issues.apache.org/jira/browse/PHOENIX-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Levine reopened PHOENIX-900: Partial results for mutations - Key: PHOENIX-900

[jira] [Resolved] (PHOENIX-900) Partial results for mutations

[ https://issues.apache.org/jira/browse/PHOENIX-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Levine resolved PHOENIX-900. Resolution: Fixed Pushed to 4.0 and main. [~jamestaylor], thanks for the review! Do we need

[jira] [Updated] (PHOENIX-900) Partial results for mutations

[ https://issues.apache.org/jira/browse/PHOENIX-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Levine updated PHOENIX-900: --- Fix Version/s: 5.0.0 4.0.0 Partial results for mutations

[jira] [Created] (PHOENIX-1671) Add CommitException.getBindParametersAtIndex(int index)

Eli Levine created PHOENIX-1671: --- Summary: Add CommitException.getBindParametersAtIndex(int index) Key: PHOENIX-1671 URL: https://issues.apache.org/jira/browse/PHOENIX-1671 Project: Phoenix

[jira] [Commented] (PHOENIX-900) Partial results for mutations

[ https://issues.apache.org/jira/browse/PHOENIX-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14323324#comment-14323324 ] Eli Levine commented on PHOENIX-900: Done. This is a good checkpoint. Because

[jira] [Commented] (PHOENIX-900) Partial results for mutations

[ https://issues.apache.org/jira/browse/PHOENIX-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14323373#comment-14323373 ] Eli Levine commented on PHOENIX-900: Musings on properly handling partial save

Re: [VOTE] Release of Apache Phoenix 4.3.0 RC0

+1 Tested for regressions using a test suite for internal Salesforce use cases with Phoenix binary artifacts from https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.3.0-rc0/bin/ On Tue, Feb 10, 2015 at 7:25 PM, James Taylor jamestay...@apache.org wrote: Hello everyone, This is a call

Simulating HBase write failures in Phoenix tests

Greetings Phoenix devs, I'm working on https://issues.apache.org/jira/browse/PHOENIX-900 (Partial results for mutations). In order to test this functionality properly, I need to write one or more tests that simulate write failures in HBase. I think this will involve having a test deploy a custom

Re: Simulating HBase write failures in Phoenix tests

a little more - and it was notably uncomfortable to mess with; we just ended up copying out what we needed. Something to look at in the future On Mon Feb 09 2015 at 11:01:39 AM Eli Levine elilev...@gmail.com wrote: Greetings Phoenix devs, I'm working on https://issues.apache.org/jira

[jira] [Updated] (PHOENIX-900) Partial results for mutations

[ https://issues.apache.org/jira/browse/PHOENIX-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Levine updated PHOENIX-900: --- Attachment: PHOENIX-900.patch Initial attempt. No tests yet. Need to figure out how to simulate

[jira] [Created] (PHOENIX-1640) Remove PhoenixConnection.executeStatements()

Eli Levine created PHOENIX-1640: --- Summary: Remove PhoenixConnection.executeStatements() Key: PHOENIX-1640 URL: https://issues.apache.org/jira/browse/PHOENIX-1640 Project: Phoenix Issue Type

[jira] [Commented] (PHOENIX-1640) Remove PhoenixConnection.executeStatements()

[ https://issues.apache.org/jira/browse/PHOENIX-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14306373#comment-14306373 ] Eli Levine commented on PHOENIX-1640: - Ah cool, thanks. What about moving that code

[jira] [Commented] (PHOENIX-900) Partial results for mutations

[ https://issues.apache.org/jira/browse/PHOENIX-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14303946#comment-14303946 ] Eli Levine commented on PHOENIX-900: Some notes: - In MutationState need to use

[jira] [Commented] (PHOENIX-900) Partial results for mutations

[ https://issues.apache.org/jira/browse/PHOENIX-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14299472#comment-14299472 ] Eli Levine commented on PHOENIX-900: FYI, shooting for starting this next week

Re: cut an RC for 4.3 release next week?

I'd like to start working on PHOENIX-900 (Partial results for mutations) and PHOENIX-978 (Allow views to extend base table's PK) soon. These are likely 2-3 weeks out. Any chance we delay 4.3 until PHOENIX-900 and PHOENIX-978 are in? Meanwhile we can cut 4.2.3 with the bug fixes. Thanks, Eli

[jira] [Commented] (PHOENIX-1496) Further reduce work in StatsCollector

[ https://issues.apache.org/jira/browse/PHOENIX-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14253781#comment-14253781 ] Eli Levine commented on PHOENIX-1496: - Sounds like this is a bug fix so +1 for 4.2

[jira] [Commented] (PHOENIX-1469) Binary columns do not work correctly for indexing

[ https://issues.apache.org/jira/browse/PHOENIX-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14254397#comment-14254397 ] Eli Levine commented on PHOENIX-1469: - +1 on getting this into 4.2. Thanks

[jira] [Commented] (PHOENIX-1469) Binary columns do not work correctly for indexing

[ https://issues.apache.org/jira/browse/PHOENIX-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14254401#comment-14254401 ] Eli Levine commented on PHOENIX-1469: - Thanks for the fix, [~dhacker1341]. Binary

[jira] [Updated] (PHOENIX-1469) Binary columns do not work correctly for indexing

[ https://issues.apache.org/jira/browse/PHOENIX-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Levine updated PHOENIX-1469: Fix Version/s: 4.2.3 4.3 5.0.0 Binary columns do not work

[jira] [Created] (PHOENIX-1542) Remove language about upgrading from 2.2 from /upgrading.html

Eli Levine created PHOENIX-1542: --- Summary: Remove language about upgrading from 2.2 from /upgrading.html Key: PHOENIX-1542 URL: https://issues.apache.org/jira/browse/PHOENIX-1542 Project: Phoenix

[jira] [Commented] (PHOENIX-1514) Break up PDataType Enum

[ https://issues.apache.org/jira/browse/PHOENIX-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14252026#comment-14252026 ] Eli Levine commented on PHOENIX-1514: - Sounds good, [~ndimiduk]. +1 for this to go

[jira] [Commented] (PHOENIX-1514) Break up PDataType Enum

[ https://issues.apache.org/jira/browse/PHOENIX-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14250457#comment-14250457 ] Eli Levine commented on PHOENIX-1514: - Thanks for the work, Nick! IMHO we might

[jira] [Comment Edited] (PHOENIX-1514) Break up PDataType Enum

[ https://issues.apache.org/jira/browse/PHOENIX-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14250457#comment-14250457 ] Eli Levine edited comment on PHOENIX-1514 at 12/17/14 8:21 PM

[jira] [Commented] (PHOENIX-1514) Break up PDataType Enum

[ https://issues.apache.org/jira/browse/PHOENIX-1514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14251189#comment-14251189 ] Eli Levine commented on PHOENIX-1514: - bq. Or by main and 5.0 branch you just mean

[jira] [Commented] (PHOENIX-1520) Provide a means of tracking progress of secondary index population

[ https://issues.apache.org/jira/browse/PHOENIX-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14247259#comment-14247259 ] Eli Levine commented on PHOENIX-1520: - Another question that needs working though

Re: [ANNOUNCE] Samarth Jain added as Apache Phoenix committer

Well deserved. Congrats and welcome, Samarth! On Sat, Dec 6, 2014 at 12:10 PM, James Taylor jamestay...@apache.org wrote: On behalf of the Apache Phoenix PMC, I'm pleased to announce that Samarth Jain has accepted our invitation to become a committer on the Apache Phoenix project. He's been a

Re: [VOTE] Release of Apache Phoenix 4.2.2 RC0

+1 approve. Ran though internal Salesforce integration tests. On Fri, Dec 5, 2014 at 10:19 AM, James Taylor jamestay...@apache.org wrote: Hello everyone, This is a call for a vote on Apache Phoenix 4.2.2 RC0. This is a bug fix/patch release of Phoenix 4.2, compatible with the 0.98 branch of

Re: cut 3.2.2/4.2.2 patch release this week

PHOENIX-1498 shouldn't go into 4.2 IMHO because (1) it has dependencies on other, still unresolved, jiras and (2) a workaround exists via the ALTER HBase shell command. Thanks, Eli On Tue, Dec 2, 2014 at 1:11 PM, lars hofhansl la...@apache.org wrote: Should we have PHOENIX-1498? Or is that

[jira] [Commented] (PHOENIX-1496) Further reduce work in StatsCollector

[ https://issues.apache.org/jira/browse/PHOENIX-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14231043#comment-14231043 ] Eli Levine commented on PHOENIX-1496: - Feels like a non-essential enhancement to me

Re: Next Phoenix release

Hi Flavio, The next bug fix release will be 4.2.2. No set date yet but likely within a week or so. WRT the Maven issues, is there a specific Jira you are interested in? Transaction support is on the roadmap but is further out. Eli On Tue, Nov 25, 2014 at 12:57 AM, Flavio Pompermaier

[jira] [Commented] (PHOENIX-1467) Upgrade to 4.12 Junit and update tests by removing @Category annotation

[ https://issues.apache.org/jira/browse/PHOENIX-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14224968#comment-14224968 ] Eli Levine commented on PHOENIX-1467: - +1 on committing test- and POM-only changes

Re: why syntax Error LPAREN?

Try without the outermost parenthesis like this: select Records.Operation, Records.status, Records.timestamp from History where Records.timestamp=(SELECT MAX(Records.timestamp) FROM History where rowId like 'xyz'); Eli On Wed, Nov 19, 2014 at 1:29 AM, Ahmed Hussien aahussi...@gmail.com wrote:

Re: why syntax Error LPAREN?

a double quote at the end of History in the nested query's from. -chris On Nov 19, 2014, at 1:11 PM, Ahmed Hussien aahussi...@gmail.com wrote: The same problem!! On 19 نوف, 2014 م 06:55, Eli Levine wrote: Try without the outermost parenthesis like this: select Records.Operation

[jira] [Updated] (PHOENIX-1463) phoenix.query.timeoutMs doesn't work as expected

[ https://issues.apache.org/jira/browse/PHOENIX-1463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Levine updated PHOENIX-1463: Fix Version/s: 4.3 5.0.0 phoenix.query.timeoutMs doesn't work as expected

[jira] [Commented] (PHOENIX-1463) phoenix.query.timeoutMs doesn't work as expected

[ https://issues.apache.org/jira/browse/PHOENIX-1463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14217162#comment-14217162 ] Eli Levine commented on PHOENIX-1463: - Thanks for taking care of this, [~samarth.j

[jira] [Comment Edited] (PHOENIX-1463) phoenix.query.timeoutMs doesn't work as expected

[ https://issues.apache.org/jira/browse/PHOENIX-1463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14217162#comment-14217162 ] Eli Levine edited comment on PHOENIX-1463 at 11/19/14 12:45 AM

[jira] [Updated] (PHOENIX-1463) phoenix.query.timeoutMs doesn't work as expected

[ https://issues.apache.org/jira/browse/PHOENIX-1463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Levine updated PHOENIX-1463: Fix Version/s: 4.2 phoenix.query.timeoutMs doesn't work as expected

[jira] [Commented] (PHOENIX-1463) phoenix.query.timeoutMs doesn't work as expected

[ https://issues.apache.org/jira/browse/PHOENIX-1463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14217210#comment-14217210 ] Eli Levine commented on PHOENIX-1463: - You are right, James. The name

[jira] [Commented] (PHOENIX-1456) Incorrect query results caused by reusing buffers in SpoolingResultIterator

[ https://issues.apache.org/jira/browse/PHOENIX-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14213720#comment-14213720 ] Eli Levine commented on PHOENIX-1456: - Thanks for reporting, Maryann. Are 4.1

[jira] [Commented] (PHOENIX-1429) Cancel queued threads when limit reached

[ https://issues.apache.org/jira/browse/PHOENIX-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14208564#comment-14208564 ] Eli Levine commented on PHOENIX-1429: - Looking over the patch

[jira] [Commented] (PHOENIX-1429) Cancel queued threads when limit reached

[ https://issues.apache.org/jira/browse/PHOENIX-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14208566#comment-14208566 ] Eli Levine commented on PHOENIX-1429: - Otherwise, looks good! Cancel queued

[jira] [Commented] (PHOENIX-1437) java.lang.OutOfMemoryError: unable to create new native thread

[ https://issues.apache.org/jira/browse/PHOENIX-1437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14206607#comment-14206607 ] Eli Levine commented on PHOENIX-1437: - Taylor, can you add the following to get

Re: [VOTE] Release of Apache Phoenix 4.2.1 RC0

Mujtaba, is this a new issue or is it there in 4.2.0? If it's in 4.2.0 not sure it's enough to sink this RC, since it's not a regression. Thanks, Eli On Mon, Nov 10, 2014 at 12:11 PM, Mujtaba Chohan mujt...@apache.org wrote: -1. Drop table doesn't work with Phoenix 4.1 client with 4.2.1-RC0

Re: [VOTE] Release of Apache Phoenix 4.2.1 RC0

correctly is important https://issues.apache.org/jira/browse/PHOENIX-1434 and also good if we get fix for PHOENIX-1428 and PHOENIX-1429. -mujtaba . On Tue, Nov 11, 2014 at 1:43 PM, Eli Levine elilev...@gmail.com wrote: Mujtaba, is this a new issue or is it there in 4.2.0? If it's in 4.2.0

Re: [VOTE] Release of Apache Phoenix 4.2.1 RC0

+1 Grabbed binaries and ran them through Salesforce's internal tests. Looks good. Thanks! On Fri, Nov 7, 2014 at 11:54 AM, James Taylor jamestay...@apache.org wrote: Hello everyone, This is a call for a vote on Apache Phoenix 4.2.1 RC0. This is a bug fix/patch release of Phoenix 4.2,

Re: [VOTE] Release of Apache Phoenix 4.2.0 RC0

+1 for 4.2 RC0. Ran extensive functional testing using code that uses Phoenix over 2M rows, concurrent queries, with and without stats, multiple region splits. Thanks, Eli On Wed, Oct 22, 2014 at 9:21 AM, James Taylor jamestay...@apache.org wrote: Hi everyone, This is a call for a vote on

Re: Hbase namespaces

feature maybe I could take a strike if there are other ways I would love to know. Hope this is clearer On Mon, Sep 29, 2014 at 5:22 PM, Eli Levine elilev...@gmail.com wrote: I thought you wanted to have a single physical Phoenix table (backed by a single HBase table) be shared for multiple

Re: Hbase namespaces

and using an Hbase table like mydb:mytable so either creatng it directly through Phoenix or creating a view on top of the hbase table to access my phoenix semantics. Hope this makes sense On Fri, Sep 26, 2014 at 4:22 PM, Eli Levine elilev...@gmail.com wrote: Views are a good way to reuse

Re: Hbase namespaces

Views are a good way to reuse a single physical table in Phoenix for multiple purposes. They can be used to essentially partition a Phoenix table. http://phoenix.apache.org/views.html Is that something like what you have in mind? Thanks, Eli On Sep 25, 2014, at 11:44 PM, Nicolas Maillard

[jira] [Resolved] (PHOENIX-1198) Add ability to pass custom annotations to be added to log lines

[ https://issues.apache.org/jira/browse/PHOENIX-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Levine resolved PHOENIX-1198. - Resolution: Fixed I have made a pass and added annotations to all log lines that are within

[jira] [Updated] (PHOENIX-1198) Add ability to pass custom annotations to be added to log lines

[ https://issues.apache.org/jira/browse/PHOENIX-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Levine updated PHOENIX-1198: Summary: Add ability to pass custom annotations to be added to log lines (was: Add ability

  1   2   >