Istvan Toth created PHOENIX-7142:
Summary: Bump version to 2.1
Key: PHOENIX-7142
URL: https://issues.apache.org/jira/browse/PHOENIX-7142
Project: Phoenix
Issue Type: Task
Components
[
https://issues.apache.org/jira/browse/PHOENIX-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth reassigned PHOENIX-7142:
Assignee: Istvan Toth
> Bump version to 2.1
> ---
>
> Ke
[
https://issues.apache.org/jira/browse/PHOENIX-7142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-7142:
-
Summary: Bump phoenix-thirdparty version to 2.1 (was: Bump version to 2.1)
> Bump phoenix-thir
Hi!
We are currently including the Omid coprocessors in Phoenix-server.
I think that this is problematic.
In order to use Omid, users have to install and configure the TSO server on
the cluster.
The Omid install instructions (correctly) include the steps to install the
Omid coprocessors to HBas
We'd have to figure out how those interact with the (unshaded) Omid
libraries in Phoenix-server.
On Wed, Dec 6, 2023 at 10:13 AM Istvan Toth wrote:
> Hi!
>
> We are currently including the Omid coprocessors in Phoenix-server.
>
> I think that this is problematic.
>
> In order to use Omid, users
[
https://issues.apache.org/jira/browse/PHOENIX-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth reassigned PHOENIX-7141:
Assignee: Istvan Toth
> hbase-server shading problems
> -
>
The shaded omid-hbase-coprocessor-1.1.1-SNAPSHOT.jar includes parts of Omid
that the coprocessors depend on.
We could shade the omid classes inside phoenix-server, that way they
wouldn't interfere, but IIRC that would break Yaml parsing.
So there doesn't seem to be a clear path forward with this.
[
https://issues.apache.org/jira/browse/PHOENIX-7140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-7140:
-
Affects Version/s: 5.1.4
> Update Apache Parent and Maven Plugin Versions in Core
> ---
[
https://issues.apache.org/jira/browse/PHOENIX-7138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth updated PHOENIX-7138:
-
Affects Version/s: 5.1.3
> Different versions are used for netty 4.1 artifacts
> --
[
https://issues.apache.org/jira/browse/PHOENIX-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranganath Govardhanagiri updated PHOENIX-7098:
--
Attachment: JsonSupportDocumentation.pdf
> Document JSON functionalit
[
https://issues.apache.org/jira/browse/PHOENIX-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranganath Govardhanagiri updated PHOENIX-7098:
--
Attachment: (was: JsonSupportDocumentation.pdf)
> Document JSON f
[
https://issues.apache.org/jira/browse/PHOENIX-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranganath Govardhanagiri updated PHOENIX-7098:
--
Attachment: JsonSupport.pdf
> Document JSON functionality on the Phoe
[
https://issues.apache.org/jira/browse/PHOENIX-7140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Istvan Toth reassigned PHOENIX-7140:
Assignee: Nihal Jain
> Update Apache Parent and Maven Plugin Versions in Core
>
[
https://issues.apache.org/jira/browse/PHOENIX-7113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rushabh Shah reassigned PHOENIX-7113:
-
Assignee: Rushabh Shah
> Create a feature flag for invoking MDEI#invalidateServerMetad
[
https://issues.apache.org/jira/browse/PHOENIX-7041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob Isaac resolved PHOENIX-7041.
--
Resolution: Fixed
> Populate ROW_KEY_PREFIX column when creating views
>
[
https://issues.apache.org/jira/browse/PHOENIX-7040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob Isaac resolved PHOENIX-7040.
--
Resolution: Fixed
> Support TTL for views using the new column TTL in SYSTEM.CATALOG
> --
Thank you Rajeshbabu! That would be great, I will be happy to help whenever
needed.
On Mon, Dec 4, 2023 at 10:37 AM rajeshb...@apache.org <
chrajeshbab...@gmail.com> wrote:
> OMID-240 is committed. We can proceed with Omid release process.
> Also, we need to start phoenix-thirdparty release as
Hi, Istvan
In terms of usage, the Omid coprocessor should be bound to the omid codebase
instead of Phoenix core. Do I understand that?
On 2023/12/06 09:13:30 Istvan Toth wrote:
> Hi!
>
> We are currently including the Omid coprocessors in Phoenix-server.
>
> I think that this is problematic.
And then
Is it possible to remove tephra component(eg. Processor, Context, Provider...)
from the phoenix codebase starting with 5.2? Because omid is production ready
earlier than tephra, and tephra maintenance is diminishing, we may no longer
need the tephra.
On 2023/12/06 09:13:30 Istvan Toth
Hello all
What minimum configuration does phoenix require to run all unit tests over?
On 2023/12/07 01:41:16 Viraj Jasani wrote:
> Thank you Rajeshbabu! That would be great, I will be happy to help whenever
> needed.
>
>
> On Mon, Dec 4, 2023 at 10:37 AM rajeshb...@apache.org <
> chrajeshbab...@
[
https://issues.apache.org/jira/browse/PHOENIX-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranganath Govardhanagiri updated PHOENIX-7098:
--
Attachment: JSON Support in Features dropdown menu.png
> Document JSO
[
https://issues.apache.org/jira/browse/PHOENIX-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranganath Govardhanagiri updated PHOENIX-7098:
--
Attachment: Json Support Documentation.png
> Document JSON functional
[
https://issues.apache.org/jira/browse/PHOENIX-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranganath Govardhanagiri updated PHOENIX-7098:
--
Attachment: (was: JSON Support in Features dropdown menu.png)
> D
[
https://issues.apache.org/jira/browse/PHOENIX-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranganath Govardhanagiri updated PHOENIX-7098:
--
Attachment: (was: Json Support Documentation.png)
> Document JSON
[
https://issues.apache.org/jira/browse/PHOENIX-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranganath Govardhanagiri updated PHOENIX-7098:
--
Attachment: JSON Support in Features dropdown menu.png
> Document JSO
[
https://issues.apache.org/jira/browse/PHOENIX-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranganath Govardhanagiri updated PHOENIX-7098:
--
Attachment: Json Support Documentation.png
> Document JSON functional
[
https://issues.apache.org/jira/browse/PHOENIX-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranganath Govardhanagiri updated PHOENIX-7098:
--
Attachment: Json Datatype.png
> Document JSON functionality on the Ph
[
https://issues.apache.org/jira/browse/PHOENIX-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranganath Govardhanagiri updated PHOENIX-7098:
--
Attachment: Json Datatype info.png
> Document JSON functionality on t
[
https://issues.apache.org/jira/browse/PHOENIX-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranganath Govardhanagiri updated PHOENIX-7098:
--
Attachment: Json Support at the bottom.png
> Document JSON functional
[
https://issues.apache.org/jira/browse/PHOENIX-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranganath Govardhanagiri updated PHOENIX-7098:
--
Attachment: Json Functions Index.png
> Document JSON functionality on
[
https://issues.apache.org/jira/browse/PHOENIX-7098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ranganath Govardhanagiri updated PHOENIX-7098:
--
Attachment: Json Functions description.png
> Document JSON functional
31 matches
Mail list logo
