[
https://issues.apache.org/jira/browse/PHOENIX-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349443#comment-14349443
]
James Taylor commented on PHOENIX-1691:
---
[~samarthjain] - would you mind reviewing
[
https://issues.apache.org/jira/browse/PHOENIX-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349297#comment-14349297
]
Nick Dimiduk commented on PHOENIX-1702:
---
I should mention, this patch comes out of
[
https://issues.apache.org/jira/browse/PHOENIX-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajeshbabu Chintaguntla updated PHOENIX-1691:
-
Attachment: PHOENIX-1691.patch
Here is the patch to set sampling
It worked ! That's awesome ! Thanks so much Andrew ! Any time in Paris, I
offer you a beer :-)
On Thu, Mar 5, 2015 at 7:47 PM, Andrew Purtell apurt...@apache.org wrote:
Hi Thibaut,
You will need to upgrade to HBase 0.98.10.1 to resolve this issue. Or, you
can recompile Phoenix from source
[
https://issues.apache.org/jira/browse/PHOENIX-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349380#comment-14349380
]
Gabriel Reid commented on PHOENIX-1653:
---
Thanks for the patch [~gjacoby]!
A few
[
https://issues.apache.org/jira/browse/PHOENIX-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349445#comment-14349445
]
lisztomania Phoenix commented on PHOENIX-1697:
--
It worked !
Thank you to
Gabriel, Nick, thanks for your inputs. My comments below.
Although it may look as though data is being written over the wire to
Phoenix, the execution of an upsert executor and retrieval of the
uncommitted KeyValues is all local (in memory). The code is implemented in
this way because JDBC is
[
https://issues.apache.org/jira/browse/PHOENIX-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349317#comment-14349317
]
James Taylor commented on PHOENIX-1674:
---
Based on help from an internal
[
https://issues.apache.org/jira/browse/PHOENIX-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349321#comment-14349321
]
Carter Shanklin commented on PHOENIX-1702:
--
I'm not sure if a band-aid fix like
[
https://issues.apache.org/jira/browse/PHOENIX-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349393#comment-14349393
]
James Taylor commented on PHOENIX-1702:
---
Not crazy about the fix, but there are a
[
https://issues.apache.org/jira/browse/PHOENIX-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samarth Jain updated PHOENIX-1452:
--
Attachment: PHOENIX-1452_v4.patch
Thanks for the reviews [~jamestaylor] and
[
https://issues.apache.org/jira/browse/PHOENIX-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349660#comment-14349660
]
Samarth Jain commented on PHOENIX-1452:
---
Thanks. I will make the change before I
You need to update the phoenix jar on the servers to match the client
version. Both client and server should be the same versions for now, at
least until our backward compatibility story is more reliable.
Basically, the new client wrote new metadata to hbase schema and the old
server jars don't
I don't know of any benchmarks vs. HBase bulk loader. Would be interesting,
if you could come up with an apples-to-apples test.
100TB binary file cannot be partitioned at all? You're always bound to a
single process. Bummer. I guess plan B could be pre-processing the binary
file into something
Thanks for pursuing this, Tulasi. I'm sure there's room for
improvement, but I think we need to get to the next level of detail to
know where. Of the 40% execution time you mentioned, how much is spent
in the CSV parse? For that, we rely on Apache Commons CSV, so probably
not much we can do about
Hi All,
I am using HDP2.1.5, Phoenix4-0.0 was installed on RS. I was running
Phoenix4.1 client because i could not find tar file for
Phoenix4-0.0-incubating.
I tried to create a view on existing table and then my entire cluster went
down(all the RS went down. MAster is still up).
This is the
[
https://issues.apache.org/jira/browse/PHOENIX-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-1703:
--
Summary: Fail connection when server minor version is less than client
minor version (was:
Is HDP2.1.5 compatible with Phoenix4.1? If yes, i'll go ahead and put 4.1
on all RS. Thanks everyone for quick response.
On Thu, Mar 5, 2015 at 3:47 PM, Nick Dimiduk ndimi...@gmail.com wrote:
You need to update the phoenix jar on the servers to match the client
version. Both client and server
[
https://issues.apache.org/jira/browse/PHOENIX-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349656#comment-14349656
]
James Taylor commented on PHOENIX-1452:
---
LGTM. +1 with one extremely minor nit,
[
https://issues.apache.org/jira/browse/PHOENIX-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samarth Jain updated PHOENIX-1452:
--
Issue Type: New Feature (was: Improvement)
Add Phoenix client-side logging and capture
James Taylor created PHOENIX-1703:
-
Summary: Disallow new minor client Phoenix jar against older minor
server jar
Key: PHOENIX-1703
URL: https://issues.apache.org/jira/browse/PHOENIX-1703
Project:
[
https://issues.apache.org/jira/browse/PHOENIX-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-953:
-
Issue Type: Sub-task (was: Bug)
Parent: PHOENIX-1665
Support UNNEST for ARRAY
[
https://issues.apache.org/jira/browse/PHOENIX-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349688#comment-14349688
]
James Taylor commented on PHOENIX-1665:
---
I've moved PHOENIX-953 under this epic
[
https://issues.apache.org/jira/browse/PHOENIX-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349698#comment-14349698
]
James Taylor commented on PHOENIX-1703:
---
That's orthogonal, as it's the way the
I have tried to disable the table but since none of the RS are coming up. I
am unable to do it. Am i missing something?
On the server side, we were using the 4.0.0-incubating. It seems like my
only option is to upgrade the server to 4.1. At-least, the HBase cluster
to be UP. I just want my
[
https://issues.apache.org/jira/browse/PHOENIX-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alicia Ying Shu reassigned PHOENIX-1704:
Assignee: Alicia Ying Shu
Add year() built-in function
[
https://issues.apache.org/jira/browse/PHOENIX-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alicia Ying Shu updated PHOENIX-1704:
-
Description:
SELECT YEAR('2014-12-13 10:13:18', '-MM-dd hh:mm:ss') FROM YEARFUNC
[
https://issues.apache.org/jira/browse/PHOENIX-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14350025#comment-14350025
]
James Taylor commented on PHOENIX-1241:
---
[~rajeshbabu] - interested in this one,
Github user ayingshu commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/39#discussion_r25928252
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/compile/QueryCompiler.java ---
@@ -147,21 +169,146 @@ public QueryCompiler(PhoenixStatement
Github user ayingshu commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/39#discussion_r25928196
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/compile/QueryCompiler.java ---
@@ -147,21 +169,146 @@ public QueryCompiler(PhoenixStatement
Github user ayingshu commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/39#discussion_r25928403
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/compile/QueryCompiler.java ---
@@ -147,21 +169,146 @@ public QueryCompiler(PhoenixStatement
Github user ayingshu commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/39#discussion_r25928427
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/compile/QueryCompiler.java ---
@@ -147,21 +169,146 @@ public QueryCompiler(PhoenixStatement
Hi all
I keep banging my head against the wall and kind of out of ideas at this
point so I hope someone can give me little helping hand.
It safe to say that I am using almost 4.3 (build just before it released)
Here is what I having problem with
CREATE TABLE IF NOT EXISTS dev.t1
(
f_int
Hello Phoenix devs,
I am planning on checking in PHOENIX-1452 to our 4.3 branch so that it can
be part of our next 4.3.1 release. The feature doesn't break any backward
compatibility and doesn't put any restrictions on which side of jar, client
or server, should be upgraded first.
PHOENIX-1452
[
https://issues.apache.org/jira/browse/PHOENIX-953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-953:
-
Description:
The UNNEST built-in function converts an array into a set of rows. This is more
Github user maryannxue commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/39#discussion_r25923422
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/compile/QueryCompiler.java ---
@@ -147,21 +169,146 @@ public QueryCompiler(PhoenixStatement
[
https://issues.apache.org/jira/browse/PHOENIX-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14347350#comment-14347350
]
James Taylor edited comment on PHOENIX-1665 at 3/6/15 12:33 AM:
Unfortunately, we ran out of luck on this one because we are not running
the latest version of HBase. This property was introduced recently:
https://issues.apache.org/jira/browse/HBASE-13044 :(
Thanks, Vladimir.
On Thu, Mar 5, 2015 at 3:44 PM, Vladimir Rodionov vladrodio...@gmail.com
wrote:
Try
[
https://issues.apache.org/jira/browse/PHOENIX-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349686#comment-14349686
]
Gary Helmling commented on PHOENIX-1674:
{quote}
1. What are the options for the
Hi Anil,
HDP-2.1.5 ships with Phoenix [0]. Are you using the version shipped, or
trying out a newer version? As James says, the upgrade must be servers
first, then client. Also, Phoenix versions tend to be picky about their
underlying HBase version.
You can also try altering the now-broken
As a terrible hack, you may be able to create a jar containing a noop
coprocessor called org.apache.hadoop.hbase.regionserver.LocalIndexSplitter
(make sure it extends BaseRegionObserver) and drop it into the RS lib
directory, restart the process. That should satisfy this table descriptor
death
[
https://issues.apache.org/jira/browse/PHOENIX-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajeshbabu Chintaguntla reassigned PHOENIX-538:
---
Assignee: Rajeshbabu Chintaguntla
Support UDFs
[
https://issues.apache.org/jira/browse/PHOENIX-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349681#comment-14349681
]
Lars Hofhansl commented on PHOENIX-1703:
+1
Maybe another option is to let the
Alicia Ying Shu created PHOENIX-1704:
Summary: Add year() built-in function
Key: PHOENIX-1704
URL: https://issues.apache.org/jira/browse/PHOENIX-1704
Project: Phoenix
Issue Type: Bug
[
https://issues.apache.org/jira/browse/PHOENIX-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samarth Jain updated PHOENIX-1452:
--
Attachment: PHOENIX-1452_v3.patch
Thanks for the comments [~jamestaylor] and
[
https://issues.apache.org/jira/browse/PHOENIX-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349136#comment-14349136
]
Jan Fernando commented on PHOENIX-1452:
---
[~samarthjain] Looks really great to me!
Also: how large is your cluster? You can make things go faster by
increasing the number of mappers. What changes did you make to the map()
method? Increased logging, performance enhancements, plugging in custom
logic, something else?
On Thursday, March 5, 2015, Gabriel Reid gabriel.r...@gmail.com
[
https://issues.apache.org/jira/browse/PHOENIX-938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349091#comment-14349091
]
Jesse Yates commented on PHOENIX-938:
-
Yup, that's a bug.
Over on PHOENIX-1676 we
[
https://issues.apache.org/jira/browse/PHOENIX-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14348717#comment-14348717
]
Dumindu Buddhika edited comment on PHOENIX-1665 at 3/5/15 2:00 PM:
Hi Tulasi,
Answers (and questions) inlined below:
On Thu, Mar 5, 2015 at 2:41 AM Tulasi Paradarami tulasi.krishn...@gmail.com
wrote:
Hi,
Here are the details of our environment:
Phoenix 4.3
HBase 0.98.6
I'm loading data to a Phoenix table using the csv bulk-loader (after making
some
[
https://issues.apache.org/jira/browse/PHOENIX-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mujtaba Chohan updated PHOENIX-1672:
Fix Version/s: 4.3.1
RegionScanner.nextRaw contract not implemented correctly
[
https://issues.apache.org/jira/browse/PHOENIX-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mujtaba Chohan updated PHOENIX-1078:
Fix Version/s: 4.3.1
Unable to run pig script with Phoenix in a secure HBase cluster
Hi Thibaut,
You will need to upgrade to HBase 0.98.10.1 to resolve this issue. Or, you
can recompile Phoenix from source with -Dhbase.version=0.98.10 (or
0.98.10.1)
On Wed, Mar 4, 2015 at 8:50 AM, Thibaut de Broca tdeb...@tessarine.com
wrote:
I try to run Phoenix in localhost and can't resolve
Nick Dimiduk created PHOENIX-1702:
-
Summary: Allow Phoenix to be used from JMeter
Key: PHOENIX-1702
URL: https://issues.apache.org/jira/browse/PHOENIX-1702
Project: Phoenix
Issue Type:
[
https://issues.apache.org/jira/browse/PHOENIX-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated PHOENIX-1702:
--
Attachment: PHOENIX-1702.00.patch
Allow Phoenix to be used from JMeter
[
https://issues.apache.org/jira/browse/PHOENIX-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk updated PHOENIX-1702:
--
Fix Version/s: 4.3.1
4.2.3
Allow Phoenix to be used from JMeter
[
https://issues.apache.org/jira/browse/PHOENIX-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349300#comment-14349300
]
Nick Dimiduk commented on PHOENIX-1702:
---
It seems I lack JIRA credentials to
[
https://issues.apache.org/jira/browse/PHOENIX-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349293#comment-14349293
]
Nick Dimiduk commented on PHOENIX-1702:
---
Patch also applies cleanly to branches
[
https://issues.apache.org/jira/browse/PHOENIX-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lavrenty Eskin updated PHOENIX-1698:
Description:
any function implementation, f.e. TRUNC or TO_CHAR for NULL value in
[
https://issues.apache.org/jira/browse/PHOENIX-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lavrenty Eskin updated PHOENIX-1698:
Description:
any function implementation, f.e. TRUNC or TO_CHAR for NULL value in
[
https://issues.apache.org/jira/browse/PHOENIX-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lavrenty Eskin updated PHOENIX-1698:
Summary: NULL in UNSIGNED_TIMESTAMP column raises Illegal data/ (was: NULL
in
[
https://issues.apache.org/jira/browse/PHOENIX-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lavrenty Eskin updated PHOENIX-1698:
Summary: NULL in UNSIGNED_TIMESTAMP raises Illegal
data/IllegalArgumentException (was:
[
https://issues.apache.org/jira/browse/PHOENIX-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lavrenty Eskin updated PHOENIX-1698:
Summary: NULL in UNSIGNED_TIMESTAMP column raises java.sql.SQLException
(was:
[
https://issues.apache.org/jira/browse/PHOENIX-1698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lavrenty Eskin updated PHOENIX-1698:
Summary: NULL in UNSIGNED_TIMESTAMP column raises Illegal
data/IllegalArgumentException
Hi,
I am Nisala Niroshana Nanayakkara, an undergraduate from Department of
Computer Science and Engineering, University of Moratuwa .Currently I am
following internship program at WSO2(PVT) Ltd, Srilanka. I have
successfully completed 3 years of 4 year degree program with higher GPA.
I went
[
https://issues.apache.org/jira/browse/PHOENIX-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14348717#comment-14348717
]
Dumindu Buddhika commented on PHOENIX-1665:
---
Hi,
I am a student from
[
https://issues.apache.org/jira/browse/PHOENIX-1674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349982#comment-14349982
]
James Taylor commented on PHOENIX-1674:
---
Thanks, [~ghelmling] - agree, this is a
[
https://issues.apache.org/jira/browse/PHOENIX-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-1705:
--
Assignee: Dumindu Buddhika
implement ARRAY_APPEND built in function
[
https://issues.apache.org/jira/browse/PHOENIX-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14350001#comment-14350001
]
James Taylor commented on PHOENIX-1660:
---
[~aakashagrawal] - I added you as a
[
https://issues.apache.org/jira/browse/PHOENIX-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-1687:
--
Assignee: Aakarsh Agarwal
Implement missing math built-in POWER function
[
https://issues.apache.org/jira/browse/PHOENIX-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-1611:
--
Summary: Support ABS Function (was: Support Absolute Function )
Support ABS Function
[
https://issues.apache.org/jira/browse/PHOENIX-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-1611:
--
Summary: Support ABS function (was: Support ABS Function )
Support ABS function
[
https://issues.apache.org/jira/browse/PHOENIX-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14350004#comment-14350004
]
James Taylor commented on PHOENIX-1611:
---
[~Seonghwan] - are you still interested
[
https://issues.apache.org/jira/browse/PHOENIX-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-1611:
--
Issue Type: Sub-task (was: Improvement)
Parent: PHOENIX-1660
Support ABS Function
Hi Ted,
In morning today, I downloaded 4.1 from the link you provided. The problem
is that i was unable to find 4.0.0-incubating release artifacts. So, i
thought to use 4.1(thinking 4.1 will be a minor compatible upgrade to
4.0) as my client.
IMO, we should also have 4.0.0-incubating artifacts
[
https://issues.apache.org/jira/browse/PHOENIX-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-1702:
--
Fix Version/s: (was: 4.3.1)
(was: 4.2.3)
[
https://issues.apache.org/jira/browse/PHOENIX-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14350016#comment-14350016
]
James Taylor commented on PHOENIX-1702:
---
[~ndimiduk] - FYI, we typically set the
Mujtaba - do you know where our 4.0.0-incubating artifacts are?
On Thu, Mar 5, 2015 at 9:58 PM, anil gupta anilgupt...@gmail.com wrote:
Hi Ted,
In morning today, I downloaded 4.1 from the link you provided. The problem
is that i was unable to find 4.0.0-incubating release artifacts. So, i
[
https://issues.apache.org/jira/browse/PHOENIX-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349749#comment-14349749
]
Hudson commented on PHOENIX-1452:
-
SUCCESS: Integrated in Phoenix-master #606 (See
@James: Could you point me to a place where i can find tar file of
Phoenix-4.0.0-incubating release? All the links on this page are broken:
http://www.apache.org/dyn/closer.cgi/incubator/phoenix/
On Thu, Mar 5, 2015 at 5:04 PM, anil gupta anilgupt...@gmail.com wrote:
I have tried to disable the
Theoretically you can run Phoenix4.1 server jar on HDP2.1.5 but this
combination isn't tested. So you should not try it in a production env.
In order to workaround the coprocessor issue, you can try to rename the table
folder in hdfs, then restart region servers so meta region will
Github user maryannxue commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/39#discussion_r25924080
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/compile/QueryCompiler.java ---
@@ -147,21 +169,146 @@ public QueryCompiler(PhoenixStatement
Hi James,
Thank for your quick response. I will follow the steps and keep posting you.
Thanks,
Nisala
On Fri, Mar 6, 2015 at 9:25 AM, James Taylor jamestay...@apache.org wrote:
Hello Nisala,
Glad to hear you're interested. Please follow the steps outlined in
the comments on this sibling
Ani:
You can find Phoenix release artifacts here:
http://archive.apache.org/dist/phoenix/
e.g. for 4.1.0:
http://archive.apache.org/dist/phoenix/phoenix-4.1.0/bin/
Cheers
On Thu, Mar 5, 2015 at 5:26 PM, anil gupta anilgupt...@gmail.com wrote:
@James: Could you point me to a place where i can
Hi,
I am Nisala Niroshana Nanayakkara, an undergraduate from Department of
Computer Science and Engineering, University of Moratuwa .Currently I am
following internship program at WSO2(PVT) Ltd, Srilanka. I have
successfully completed 3 years of 4 year degree program with higher GPA.
I went
We copied Phoenix4.1 on our RS and restarted the cluster. It came UP.
Sigh! Copying jar fixed it!.. This was one of the most nasty situation i've
ever run into HBase.
After the restart, i truncated 'SYSTEM.CATALOG' and SYSTEM.SEQUENCE. I
also removed all the Phoenix Coprocessors from my table.
Github user maryannxue commented on a diff in the pull request:
https://github.com/apache/phoenix/pull/39#discussion_r25924146
--- Diff:
phoenix-core/src/main/java/org/apache/phoenix/compile/QueryCompiler.java ---
@@ -147,21 +169,146 @@ public QueryCompiler(PhoenixStatement
Hello Nisala,
Glad to hear you're interested. Please follow the steps outlined in
the comments on this sibling JIRA:
https://issues.apache.org/jira/browse/PHOENIX-1660?focusedCommentId=14327769page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14327769
Thanks,
James
On
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
Dumindu Buddhika created PHOENIX-1705:
-
Summary: implement ARRAY_APPEND built in function
Key: PHOENIX-1705
URL: https://issues.apache.org/jira/browse/PHOENIX-1705
Project: Phoenix
Issue
[
https://issues.apache.org/jira/browse/PHOENIX-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349968#comment-14349968
]
Serhiy Bilousov commented on PHOENIX-1665:
--
I thought unnest is postgresql's
[
https://issues.apache.org/jira/browse/PHOENIX-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14349979#comment-14349979
]
Jeongdae Kim commented on PHOENIX-1676:
---
copied from the comment written in
92 matches
Mail list logo
