Thanks for the quick responses Josh and Rajeshbabu!
Yes, this would mean that to actually use Omid/Tephra, you need to install
them separately, and launch their daemons from their respective install
locations.
(and they need to be the specific versions bundled into the phoenix jars)
The scope of
[
https://issues.apache.org/jira/browse/PHOENIX-6120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gokcen Iskender updated PHOENIX-6120:
-
Attachment: PHOENIX-6120.master.002.patch
> Covered columns of indexes that have SINGLE
[
https://issues.apache.org/jira/browse/PHOENIX-6129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kulkarni updated PHOENIX-6129:
--
Summary: Remove unnecessary HBase admin API calls when writing and deleting
mutex cel
[
https://issues.apache.org/jira/browse/PHOENIX-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kulkarni updated PHOENIX-6127:
--
Summary: Prevent unnecessary HBase admin API calls in
ViewUtil.getSystemTableForChild
Chinmay Kulkarni created PHOENIX-6129:
-
Summary: Remove unnecessary HBase Admin API calls when writing and
deleting mutex cells
Key: PHOENIX-6129
URL: https://issues.apache.org/jira/browse/PHOENIX-6129
Chinmay Kulkarni created PHOENIX-6128:
-
Summary: Remove unused getAdmin() call inside CQSI.init()
Key: PHOENIX-6128
URL: https://issues.apache.org/jira/browse/PHOENIX-6128
Project: Phoenix
Chinmay Kulkarni created PHOENIX-6127:
-
Summary: Prevent unnecessary HBase Admin API calls in
ViewUtil.getSystemTableForChildLinks() and act lazily instead
Key: PHOENIX-6127
URL: https://issues.apache.org/jira
[
https://issues.apache.org/jira/browse/PHOENIX-6126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kulkarni updated PHOENIX-6126:
--
Priority: Minor (was: Major)
> All createViewAddChildLink requests will go to the sa
Chinmay Kulkarni created PHOENIX-6126:
-
Summary: All createViewAddChildLink requests will go to the same
region of SYSTEM.CHILD_LINK
Key: PHOENIX-6126
URL: https://issues.apache.org/jira/browse/PHOENIX-6126
Chinmay Kulkarni created PHOENIX-6125:
-
Summary: Make sure SYSTEM.TASK does not split
Key: PHOENIX-6125
URL: https://issues.apache.org/jira/browse/PHOENIX-6125
Project: Phoenix
Issue Type
Chinmay Kulkarni created PHOENIX-6124:
-
Summary: Block adding/dropping a column on a parent view for
clients <4.15 and for clients that have
phoenix.allow.system.catalog.rollback=true
Key: PHOENIX-6124
URL: h
Chinmay Kulkarni created PHOENIX-6123:
-
Summary: Old clients cannot query a view if the parent has an index
Key: PHOENIX-6123
URL: https://issues.apache.org/jira/browse/PHOENIX-6123
Project: Phoeni
[
https://issues.apache.org/jira/browse/PHOENIX-4195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chinmay Kulkarni updated PHOENIX-4195:
--
Fix Version/s: 4.16.0
> PHOENIX-4195 Deleting view rows with extended PKs through the
+1 for the change as the Omid and Tephra transaction services don't have
any dependency on Phoenix and they should also directly serve HBase level
cross row/table transactions as well.
On Fri, Sep 11, 2020 at 9:27 PM Josh Elser wrote:
> Sounds reasonable to me.
>
> We have the same kind of th
Sounds reasonable to me.
We have the same kind of thing going since phoenix-queryserver was moved
out to its own repository. Maybe we can come up with some conventions as
to how we "overlay" things so that Omid, PQS, and Tephra can all have
some semblance of familiarity?
I think that would m
Hi!
We are currently shipping startup scripts and [some of] the JARs necessary
to start the server components of Omid and Tephra in the Phoenix
distribution.
The JARs for OMID are manually enumerated to be added to the distribution,
and have to be updated whenever the Omid dependencies change (an
[
https://issues.apache.org/jira/browse/PHOENIX-6122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Penzes updated PHOENIX-6122:
--
Labels: jquery (was: )
> Upgrade jQuery to 3.5.1
> ---
>
>
[
https://issues.apache.org/jira/browse/PHOENIX-6122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Penzes updated PHOENIX-6122:
--
Component/s: core
> Upgrade jQuery to 3.5.1
> ---
>
> Key
[
https://issues.apache.org/jira/browse/PHOENIX-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth resolved PHOENIX-6042.
--
Resolution: Duplicate
There's no point tracking this and PHOENIX-6043 separately, I'm going t
[
https://issues.apache.org/jira/browse/PHOENIX-6043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth resolved PHOENIX-6043.
--
Resolution: Duplicate
There's no point tracking this and PHOENIX-6042 separately, I'm going t
[
https://issues.apache.org/jira/browse/PHOENIX-6109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth resolved PHOENIX-6109.
--
Resolution: Won't Fix
This is obsoleted by the switch to using proper YETUS for precommit tes
Tamas Penzes created PHOENIX-6122:
-
Summary: Upgrade jQuery to 3.5.1
Key: PHOENIX-6122
URL: https://issues.apache.org/jira/browse/PHOENIX-6122
Project: Phoenix
Issue Type: Bug
Affects Ver
Istvan Toth created PHOENIX-6121:
Summary: hbase-compat-2.3 jar missing from assembly root
Key: PHOENIX-6121
URL: https://issues.apache.org/jira/browse/PHOENIX-6121
Project: Phoenix
Issue Typ
23 matches
Mail list logo
