Yes , I can see src/it in eclipse(Mars Release (4.5.0)) with no additional
steps or tricks(just import maven project).
May be you can try mvn eclipse:eclipse or check source in Java Build Path
whether src/it is there or not.
On Thu, Jul 7, 2016 at 11:15 PM, Mujtaba Chohan
+1 for patch releases on a more frequent cadence. I volunteered to do a
4.7.x line in support of my own requirements. I think folks are settling on
a Phoenix minor release for longer periods, and they'll benefit from
receiving bug fixes along the way. Defining and enforcing compatibility is
a part
[
https://issues.apache.org/jira/browse/PHOENIX-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366904#comment-15366904
]
NIDHI GAMBHIR commented on PHOENIX-2265:
If no body is working on this one, is it fine if I pick
[
https://issues.apache.org/jira/browse/PHOENIX-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366900#comment-15366900
]
Enis Soztutar commented on PHOENIX-3057:
+1.
> Set incremental=false for sqlline-thin.py like
[
https://issues.apache.org/jira/browse/PHOENIX-3057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated PHOENIX-3057:
Attachment: PHOENIX-3057.patch
Trivial change.
> Set incremental=false for sqlline-thin.py like
Josh Elser created PHOENIX-3057:
---
Summary: Set incremental=false for sqlline-thin.py like sqlline.py
Key: PHOENIX-3057
URL: https://issues.apache.org/jira/browse/PHOENIX-3057
Project: Phoenix
[
https://issues.apache.org/jira/browse/PHOENIX-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366684#comment-15366684
]
James Taylor commented on PHOENIX-3056:
---
Good point, [~lhofhansl]. That's a general problem for
[
https://issues.apache.org/jira/browse/PHOENIX-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-3056:
--
Summary: Rows cannot be deleted from immutable table when in building state
(was: Incorrect
[
https://issues.apache.org/jira/browse/PHOENIX-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366556#comment-15366556
]
Enis Soztutar commented on PHOENIX-3055:
bq. Though seemingly innocuous, changes like this can
As a consumer of Phoenix, moving to where we have regular patch releases on
a predicable cadence that contain bug fixes would be incredibly beneficial.
For the most recent few releases we have only needed bug fixes and were not
dependent on any of the new features. Therefore having to wait until a
[
https://issues.apache.org/jira/browse/PHOENIX-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kevin Liew reopened PHOENIX-3051:
-
> IN predicate cannot compare CHAR columns of differing length
>
[
https://issues.apache.org/jira/browse/PHOENIX-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366495#comment-15366495
]
Lars Hofhansl commented on PHOENIX-3056:
bq. Issuing delete markers will work, though, as when
[
https://issues.apache.org/jira/browse/PHOENIX-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366484#comment-15366484
]
Lars Hofhansl commented on PHOENIX-3056:
Thanks for explaining [~giacomotaylor] (and yes, we're
src/it show up fine without any additional step with Eclipse Luna 4.4.2.
m2e connector 0.14.
On Thu, Jul 7, 2016 at 10:35 AM, James Taylor
wrote:
> You can or cannot, Ankit see src/it dirs? Looks like both Maryann and I are
> having this issue. If you can see src/it
[
https://issues.apache.org/jira/browse/PHOENIX-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-3056:
--
Attachment: PHOENIX-3056_wip.patch
Here's a patch that fill fix the issue, but needs a bit
You can or cannot, Ankit see src/it dirs? Looks like both Maryann and I are
having this issue. If you can see src/it directories, can you let us know
your Eclipse version and any tricks/steps?
Thanks!
On Thu, Jul 7, 2016 at 9:40 AM, Ankit Singhal
wrote:
> I can see
Was with Brian yesterday, PHOENIX-3056 is not a 4.8 blocker for them but
good to have if a fix is easy.
On Thu, Jul 7, 2016 at 2:54 AM, wrote:
> I assigned PHOENIX-3056 to 4.8.0, just so we won't lose track of it. If
> it's not an issue we can move to 4.9.
>
>
>
I can see src/it directories in eclipse with fresh imports as well.
On Thu, Jul 7, 2016 at 9:50 PM, Maryann Xue wrote:
> Same here.
>
> On Thu, Jul 7, 2016 at 10:47 AM, James Taylor
> wrote:
>
> > Anyone else seeing this issue? When I import the
[
https://issues.apache.org/jira/browse/PHOENIX-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366354#comment-15366354
]
Josh Elser commented on PHOENIX-3044:
-
No, I haven't had the time to look at your code.
> Whenever
Same here.
On Thu, Jul 7, 2016 at 10:47 AM, James Taylor
wrote:
> Anyone else seeing this issue? When I import the projects into Eclipse, I
> no longer see the src/it directories for any of the projects.
>
> James
>
[
https://issues.apache.org/jira/browse/PHOENIX-3044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366331#comment-15366331
]
Cheyenne commented on PHOENIX-3044:
---
Hi [~elserj],
Just checking to see if you found whats causing
[
https://issues.apache.org/jira/browse/PHOENIX-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366306#comment-15366306
]
Thomas D'Silva commented on PHOENIX-3056:
-
Sure [~jamestaylor]
> Incorrect error message when
[
https://issues.apache.org/jira/browse/PHOENIX-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas D'Silva updated PHOENIX-3056:
Assignee: James Taylor (was: Thomas D'Silva)
> Incorrect error message when deleting a
[
https://issues.apache.org/jira/browse/PHOENIX-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366284#comment-15366284
]
James Taylor commented on PHOENIX-3056:
---
I've investigated this a bit and found the cause. It has
Anyone else seeing this issue? When I import the projects into Eclipse, I
no longer see the src/it directories for any of the projects.
James
[
https://issues.apache.org/jira/browse/PHOENIX-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas D'Silva reassigned PHOENIX-3056:
---
Assignee: Thomas D'Silva
> Incorrect error message when deleting a record from
[
https://issues.apache.org/jira/browse/PHOENIX-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15366028#comment-15366028
]
Hudson commented on PHOENIX-2999:
-
SUCCESS: Integrated in Phoenix-master #1311 (See
[
https://issues.apache.org/jira/browse/PHOENIX-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15365917#comment-15365917
]
James Taylor commented on PHOENIX-2999:
---
+1 [~an...@apache.org]. Thanks for the revisions.
>
[
https://issues.apache.org/jira/browse/PHOENIX-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15365909#comment-15365909
]
James Taylor commented on PHOENIX-3056:
---
[~lhofhansl] - I see we're both on the same timezone. :-)
[
https://issues.apache.org/jira/browse/PHOENIX-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15365891#comment-15365891
]
Lars Hofhansl commented on PHOENIX-3056:
If this really is a minor only, let's move it to 4.9.
I assigned PHOENIX-3056 to 4.8.0, just so we won't lose track of it. If it's
not an issue we can move to 4.9.
From: James Taylor
To: "dev@phoenix.apache.org" ; Mujtaba Chohan
Sent: Thursday, July 7, 2016 1:24 AM
[
https://issues.apache.org/jira/browse/PHOENIX-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Hofhansl updated PHOENIX-3056:
---
Fix Version/s: 4.8.0
> Incorrect error message when deleting a record from table with async
Yes, all unresolved JIRAs except blocker for 4.8 are moved to 4.9.
Here, is the filter to track blocker for 4.8 now
[
https://issues.apache.org/jira/browse/PHOENIX-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15365887#comment-15365887
]
Lars Hofhansl commented on PHOENIX-3056:
bq. deletes are blocked until that completes
How
Agreed. On all counts.
There are some bigger changes in the pipeline (column remapping and "dense"
column storage).Those are powerful and combine the power of SQL and HBase quite
nicely. I propose we get those soon after 4.8 and then spin a 4.9 from those.
A 4.8.1 would be of great value as
[
https://issues.apache.org/jira/browse/PHOENIX-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankit Singhal updated PHOENIX-2508:
---
Labels: verify (was: )
> Phoenix Connections Stopped Working
>
[
https://issues.apache.org/jira/browse/PHOENIX-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankit Singhal updated PHOENIX-2508:
---
Priority: Major (was: Blocker)
> Phoenix Connections Stopped Working
>
[
https://issues.apache.org/jira/browse/PHOENIX-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ankit Singhal updated PHOENIX-2999:
---
Priority: Blocker (was: Critical)
> Upgrading Multi-tenant table to map with namespace
[
https://issues.apache.org/jira/browse/PHOENIX-3045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15365862#comment-15365862
]
Ankit Singhal commented on PHOENIX-3045:
Workaround could be that the user can create a ASYNC
If we were to launch a long term stable release expected to produce monthly
maintenance releases for, potentially, years, I would sign up for maintaining
that branch-set. This is what I have been doing over in HBase with 0.98.
> On Jul 7, 2016, at 1:50 AM, James Taylor
@Ankit - Can we move all non blocking issues marked for 4.8 to 4.9 too?
Here's a link to the 97 open JIRAs for 4.8:
https://issues.apache.org/jira/browse/PHOENIX-2508?jql=fixVersion%20%3D%204.8.0%20AND%20project%20%3D%20PHOENIX%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC
It's good we're having this discussion. I think the crux of the issue is
lack of people to step up as RM for branch. Each minor release, we create
the branch, so everything is in place to do it. A secondary, related issue
is the number of branches that need to be kept up to date: 4 branches (1
per
@Ankit, @Mujtaba - where are at now with the release? Would it be possible
to get a list of the handful of remaining JIRAs being targeted for
4.8? Is PHOENIX-3056
a blocker?
Thanks,
James
On Tue, Jul 5, 2016 at 4:21 PM, Josh Elser wrote:
> Just an FYI: I re-opened
[
https://issues.apache.org/jira/browse/PHOENIX-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-3055:
--
Fix Version/s: (was: 4.8.0)
> Fix a few resource leaks and null dereferences reported by
[
https://issues.apache.org/jira/browse/PHOENIX-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15365793#comment-15365793
]
James Taylor commented on PHOENIX-3056:
---
[~tdsilva] - would it be possible for you to take a look
[
https://issues.apache.org/jira/browse/PHOENIX-3055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15365787#comment-15365787
]
James Taylor commented on PHOENIX-3055:
---
Though seemingly innocuous, changes like this can lead to
That'd be great, William. I'd recommend adding all necessary secondary
indexes. I remember there's an academic paper that describes the optimal
indexes to add for each benchmark, but I can't seem to find it.
Thanks,
James
On Thu, Jul 7, 2016 at 4:02 AM, William wrote:
> Hi
47 matches
Mail list logo