Re: [PR] NIFI-12983: Qdrant vector store support [nifi]
Anush008 commented on code in PR #8590:
URL: https://github.com/apache/nifi/pull/8590#discussion_r1545992040
##
nifi-python-extensions/nifi-text-embeddings-module/src/main/python/vectorstores/QueryQdrant.py:
##
@@ -0,0 +1,192 @@
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements. See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+from langchain.vectorstores.qdrant import Qdrant
+from nifiapi.flowfiletransform import FlowFileTransform,
FlowFileTransformResult
+from nifiapi.properties import (
+PropertyDescriptor,
+StandardValidators,
+ExpressionLanguageScope,
+)
+import QueryUtils
+import json
+from EmbeddingUtils import (
+create_embedding_service,
+)
+
+from nifiapi.documentation import use_case
+
+from qdrant_client import QdrantClient
+
+import QdrantUtils
+
+
+@use_case(
+description="Semantically search for documents stored in Qdrant -
https://qdrant.tech/;,
+keywords=["qdrant", "embedding", "vector", "text", "vectorstore",
"search"],
+configuration="""
+Configure 'Collection Name' to the name of the Qdrant
collection to use.
+Configure 'Qdrant URL' to the fully qualified URL of the
Qdrant instance.
+Configure 'Qdrant API Key' to the API Key to use in order to
authenticate with Qdrant.
+Configure 'Prefer gRPC' to True if you want to use gRPC for
interfacing with Qdrant.
+Configure 'Use HTTPS' to True if you want to use TLS(HTTPS)
while interfacing with Qdrant.
+Configure 'Embedding Model' to indicate whether OpenAI
embeddings should be used or a HuggingFace embedding model should be used:
'Hugging Face Model' or 'OpenAI Model'
+Configure 'HuggingFace API Key' or 'OpenAI API Key', depending
on the chosen Embedding Model.
+Configure 'HuggingFace Model' or 'OpenAI Model' to the name of
the model to use.
+Configure 'Query' to the text of the query to send to Qdrant.
+Configure 'Number of Results' to the number of results to
return from Qdrant.
+Configure 'Metadata Filter' to apply an optional metadata
filter with the query. For example: { "author": "john.doe" }
+Configure 'Output Strategy' to indicate how the output should
be formatted: 'Row-Oriented', 'Text', or 'Column-Oriented'.
+Configure 'Results Field' to the name of the field to insert
the results, if the input FlowFile is JSON Formatted,.
+Configure 'Include Metadatas' to True if metadata should be
included in the output.
+Configure 'Include Distances' to True if distances should be
included in the output.
+""",
+)
+class QueryQdrant(FlowFileTransform):
+class Java:
+implements = ["org.apache.nifi.python.processor.FlowFileTransform"]
+
+class ProcessorDetails:
+version = "2.0.0-SNAPSHOT"
+description = "Queries Qdrant in order to gather a specified number of
documents that are most closely related to the given query."
+tags = [
+"qdrant",
+"vector",
+"vectordb",
+"vectorstore",
+"embeddings",
+"ai",
+"artificial intelligence",
+"ml",
+"machine learning",
+"text",
+"LLM",
+]
+
+QUERY = PropertyDescriptor(
+name="Query",
+description="The text of the query to send to Qdrant.",
+required=True,
+validators=[StandardValidators.NON_EMPTY_VALIDATOR],
+expression_language_scope=ExpressionLanguageScope.FLOWFILE_ATTRIBUTES,
+)
+NUMBER_OF_RESULTS = PropertyDescriptor(
+name="Number of Results",
+description="The number of results to return from Qdrant.",
+required=True,
+validators=[StandardValidators.POSITIVE_INTEGER_VALIDATOR],
+default_value="10",
+expression_language_scope=ExpressionLanguageScope.FLOWFILE_ATTRIBUTES,
+)
+FILTER = PropertyDescriptor(
+name="Metadata Filter",
+description='Optional metadata filter to apply with the query. For
example: { "author": "john.doe" }',
+required=False,
+
Re: [PR] NIFI-12983: Qdrant vector store support [nifi]
Anush008 commented on code in PR #8590:
URL: https://github.com/apache/nifi/pull/8590#discussion_r1545992040
##
nifi-python-extensions/nifi-text-embeddings-module/src/main/python/vectorstores/QueryQdrant.py:
##
@@ -0,0 +1,192 @@
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements. See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+from langchain.vectorstores.qdrant import Qdrant
+from nifiapi.flowfiletransform import FlowFileTransform,
FlowFileTransformResult
+from nifiapi.properties import (
+PropertyDescriptor,
+StandardValidators,
+ExpressionLanguageScope,
+)
+import QueryUtils
+import json
+from EmbeddingUtils import (
+create_embedding_service,
+)
+
+from nifiapi.documentation import use_case
+
+from qdrant_client import QdrantClient
+
+import QdrantUtils
+
+
+@use_case(
+description="Semantically search for documents stored in Qdrant -
https://qdrant.tech/;,
+keywords=["qdrant", "embedding", "vector", "text", "vectorstore",
"search"],
+configuration="""
+Configure 'Collection Name' to the name of the Qdrant
collection to use.
+Configure 'Qdrant URL' to the fully qualified URL of the
Qdrant instance.
+Configure 'Qdrant API Key' to the API Key to use in order to
authenticate with Qdrant.
+Configure 'Prefer gRPC' to True if you want to use gRPC for
interfacing with Qdrant.
+Configure 'Use HTTPS' to True if you want to use TLS(HTTPS)
while interfacing with Qdrant.
+Configure 'Embedding Model' to indicate whether OpenAI
embeddings should be used or a HuggingFace embedding model should be used:
'Hugging Face Model' or 'OpenAI Model'
+Configure 'HuggingFace API Key' or 'OpenAI API Key', depending
on the chosen Embedding Model.
+Configure 'HuggingFace Model' or 'OpenAI Model' to the name of
the model to use.
+Configure 'Query' to the text of the query to send to Qdrant.
+Configure 'Number of Results' to the number of results to
return from Qdrant.
+Configure 'Metadata Filter' to apply an optional metadata
filter with the query. For example: { "author": "john.doe" }
+Configure 'Output Strategy' to indicate how the output should
be formatted: 'Row-Oriented', 'Text', or 'Column-Oriented'.
+Configure 'Results Field' to the name of the field to insert
the results, if the input FlowFile is JSON Formatted,.
+Configure 'Include Metadatas' to True if metadata should be
included in the output.
+Configure 'Include Distances' to True if distances should be
included in the output.
+""",
+)
+class QueryQdrant(FlowFileTransform):
+class Java:
+implements = ["org.apache.nifi.python.processor.FlowFileTransform"]
+
+class ProcessorDetails:
+version = "2.0.0-SNAPSHOT"
+description = "Queries Qdrant in order to gather a specified number of
documents that are most closely related to the given query."
+tags = [
+"qdrant",
+"vector",
+"vectordb",
+"vectorstore",
+"embeddings",
+"ai",
+"artificial intelligence",
+"ml",
+"machine learning",
+"text",
+"LLM",
+]
+
+QUERY = PropertyDescriptor(
+name="Query",
+description="The text of the query to send to Qdrant.",
+required=True,
+validators=[StandardValidators.NON_EMPTY_VALIDATOR],
+expression_language_scope=ExpressionLanguageScope.FLOWFILE_ATTRIBUTES,
+)
+NUMBER_OF_RESULTS = PropertyDescriptor(
+name="Number of Results",
+description="The number of results to return from Qdrant.",
+required=True,
+validators=[StandardValidators.POSITIVE_INTEGER_VALIDATOR],
+default_value="10",
+expression_language_scope=ExpressionLanguageScope.FLOWFILE_ATTRIBUTES,
+)
+FILTER = PropertyDescriptor(
+name="Metadata Filter",
+description='Optional metadata filter to apply with the query. For
example: { "author": "john.doe" }',
+required=False,
+
[jira] [Created] (NIFI-12983) Add support for Qdrant vector store
Anush created NIFI-12983: Summary: Add support for Qdrant vector store Key: NIFI-12983 URL: https://issues.apache.org/jira/browse/NIFI-12983 Project: Apache NiFi Issue Type: Improvement Components: Extensions Reporter: Anush Qdrant - [https://github.com/qdrant/qdrant], is an open-source vector search engine and database, governed by the Apache-2.0 license. Qdrant ranks amongst the most performant and most used vector databases available today. - [https://qdrant.tech/benchmarks]/ - [https://ossinsight.io/collections/vector-search-engine]/ This is a proposal to add support for Qdrant via an extension in NiFi. Associated pull-request:https://github.com/apache/nifi/pull/8590 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-XXXXX Qdrant vector store support [nifi]
pvillard31 commented on code in PR #8590:
URL: https://github.com/apache/nifi/pull/8590#discussion_r1545989058
##
nifi-python-extensions/nifi-text-embeddings-module/src/main/python/vectorstores/QueryQdrant.py:
##
@@ -0,0 +1,192 @@
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements. See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+from langchain.vectorstores.qdrant import Qdrant
+from nifiapi.flowfiletransform import FlowFileTransform,
FlowFileTransformResult
+from nifiapi.properties import (
+PropertyDescriptor,
+StandardValidators,
+ExpressionLanguageScope,
+)
+import QueryUtils
+import json
+from EmbeddingUtils import (
+create_embedding_service,
+)
+
+from nifiapi.documentation import use_case
+
+from qdrant_client import QdrantClient
+
+import QdrantUtils
+
+
+@use_case(
+description="Semantically search for documents stored in Qdrant -
https://qdrant.tech/;,
+keywords=["qdrant", "embedding", "vector", "text", "vectorstore",
"search"],
+configuration="""
+Configure 'Collection Name' to the name of the Qdrant
collection to use.
+Configure 'Qdrant URL' to the fully qualified URL of the
Qdrant instance.
+Configure 'Qdrant API Key' to the API Key to use in order to
authenticate with Qdrant.
+Configure 'Prefer gRPC' to True if you want to use gRPC for
interfacing with Qdrant.
+Configure 'Use HTTPS' to True if you want to use TLS(HTTPS)
while interfacing with Qdrant.
+Configure 'Embedding Model' to indicate whether OpenAI
embeddings should be used or a HuggingFace embedding model should be used:
'Hugging Face Model' or 'OpenAI Model'
+Configure 'HuggingFace API Key' or 'OpenAI API Key', depending
on the chosen Embedding Model.
+Configure 'HuggingFace Model' or 'OpenAI Model' to the name of
the model to use.
+Configure 'Query' to the text of the query to send to Qdrant.
+Configure 'Number of Results' to the number of results to
return from Qdrant.
+Configure 'Metadata Filter' to apply an optional metadata
filter with the query. For example: { "author": "john.doe" }
+Configure 'Output Strategy' to indicate how the output should
be formatted: 'Row-Oriented', 'Text', or 'Column-Oriented'.
+Configure 'Results Field' to the name of the field to insert
the results, if the input FlowFile is JSON Formatted,.
+Configure 'Include Metadatas' to True if metadata should be
included in the output.
+Configure 'Include Distances' to True if distances should be
included in the output.
+""",
+)
+class QueryQdrant(FlowFileTransform):
+class Java:
+implements = ["org.apache.nifi.python.processor.FlowFileTransform"]
+
+class ProcessorDetails:
+version = "2.0.0-SNAPSHOT"
+description = "Queries Qdrant in order to gather a specified number of
documents that are most closely related to the given query."
+tags = [
+"qdrant",
+"vector",
+"vectordb",
+"vectorstore",
+"embeddings",
+"ai",
+"artificial intelligence",
+"ml",
+"machine learning",
+"text",
+"LLM",
+]
+
+QUERY = PropertyDescriptor(
+name="Query",
+description="The text of the query to send to Qdrant.",
+required=True,
+validators=[StandardValidators.NON_EMPTY_VALIDATOR],
+expression_language_scope=ExpressionLanguageScope.FLOWFILE_ATTRIBUTES,
+)
+NUMBER_OF_RESULTS = PropertyDescriptor(
+name="Number of Results",
+description="The number of results to return from Qdrant.",
+required=True,
+validators=[StandardValidators.POSITIVE_INTEGER_VALIDATOR],
+default_value="10",
+expression_language_scope=ExpressionLanguageScope.FLOWFILE_ATTRIBUTES,
+)
+FILTER = PropertyDescriptor(
+name="Metadata Filter",
+description='Optional metadata filter to apply with the query. For
example: { "author": "john.doe" }',
+required=False,
+
[PR] NIFI-XXXXX Qdrant vector store support [nifi]
Anush008 opened a new pull request, #8590: URL: https://github.com/apache/nifi/pull/8590 # Summary Jira ticket to be attached after account approval. [NIFI-0](https://issues.apache.org/jira/browse/NIFI-0) # Tracking ### Issue Tracking - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [ ] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [x] Pull Request based on current revision of the `main` branch - [x] Pull Request refers to a feature branch with one commit containing changes ### Build - [x] Build completed using `mvn clean install -P contrib-check` - [x] JDK 21 ### Licensing - [x] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [x] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [x] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (NIFI-12982) Extend test suite of MockProcessSession
[
https://issues.apache.org/jira/browse/NIFI-12982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
endzeit updated NIFI-12982:
---
Description:
As part of NIFI-12971 (or a subtask) most likely changes will be introduced to
both {{StandardProcessorTestRunner}} and {{MockProcessSession}}.
To reduce the risk of regressions introduced by those changes, the test suite
of {{MockProcessSession}} should be extended to account for more scenarios,
regarding both expected successful and failing interactions.
was:
As part of NIFI-12971 (or a subtask) most likely changes will be introduced to
both {{
StandardProcessorTestRunner}} and {{MockProcessSession}}.
To reduce the risk of regressions introduced by those changes, the test suite
of \{{MockProcessSession}} should be extended to account for more scenarios,
regarding both expected successful and failing interactions.
> Extend test suite of MockProcessSession
> ---
>
> Key: NIFI-12982
> URL: https://issues.apache.org/jira/browse/NIFI-12982
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: endzeit
>Assignee: endzeit
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> As part of NIFI-12971 (or a subtask) most likely changes will be introduced
> to both {{StandardProcessorTestRunner}} and {{MockProcessSession}}.
>
> To reduce the risk of regressions introduced by those changes, the test
> suite of {{MockProcessSession}} should be extended to account for more
> scenarios, regarding both expected successful and failing interactions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12982) Extend test suite of MockProcessSession
[
https://issues.apache.org/jira/browse/NIFI-12982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
endzeit updated NIFI-12982:
---
Description:
As part of NIFI-12971 (or a subtask thereof) most likely changes will be
introduced to both {{StandardProcessorTestRunner}} and {{MockProcessSession}}.
To reduce the risk of regressions introduced by those changes, the test suite
of {{MockProcessSession}} should be extended to account for more scenarios,
regarding both expected successful and failing interactions.
was:
As part of NIFI-12971 (or a subtask) most likely changes will be introduced to
both {{StandardProcessorTestRunner}} and {{MockProcessSession}}.
To reduce the risk of regressions introduced by those changes, the test suite
of {{MockProcessSession}} should be extended to account for more scenarios,
regarding both expected successful and failing interactions.
> Extend test suite of MockProcessSession
> ---
>
> Key: NIFI-12982
> URL: https://issues.apache.org/jira/browse/NIFI-12982
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: endzeit
>Assignee: endzeit
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> As part of NIFI-12971 (or a subtask thereof) most likely changes will be
> introduced to both {{StandardProcessorTestRunner}} and {{MockProcessSession}}.
>
> To reduce the risk of regressions introduced by those changes, the test
> suite of {{MockProcessSession}} should be extended to account for more
> scenarios, regarding both expected successful and failing interactions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12982) Extend test suite of MockProcessSession
[
https://issues.apache.org/jira/browse/NIFI-12982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
endzeit updated NIFI-12982:
---
Description:
As part of NIFI-12971 (or a subtask) most likely changes will be introduced to
both {{
StandardProcessorTestRunner}} and {{MockProcessSession}}.
To reduce the risk of regressions introduced by those changes, the test suite
of \{{MockProcessSession}} should be extended to account for more scenarios,
regarding both expected successful and failing interactions.
was:
As part of NIFI-12971 (or a subtask) most likely changes will be introduced to
both {{
StandardProcessorTestRunner}} and \{{MockProcessSession}}.
To reduce the risk of regressions introduced by those changes, the test suite
of \{{MockProcessSession}} should be extended to account for more scenarios,
regarding both expected successful and failing interactions.
> Extend test suite of MockProcessSession
> ---
>
> Key: NIFI-12982
> URL: https://issues.apache.org/jira/browse/NIFI-12982
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: endzeit
>Assignee: endzeit
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> As part of NIFI-12971 (or a subtask) most likely changes will be introduced
> to both {{
> StandardProcessorTestRunner}} and {{MockProcessSession}}.
>
> To reduce the risk of regressions introduced by those changes, the test
> suite of \{{MockProcessSession}} should be extended to account for more
> scenarios, regarding both expected successful and failing interactions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] NIFI-12982 Extend test suite of MockProcessSession [nifi]
EndzeitBegins opened a new pull request, #8589: URL: https://github.com/apache/nifi/pull/8589 # Summary [NIFI-12982](https://issues.apache.org/jira/browse/NIFI-12982) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [x] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [x] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [x] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [x] Pull Request based on current revision of the `main` branch - [x] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [x] Build completed using `mvn clean install -P contrib-check` - [x] JDK 21 ### Licensing - [x] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [x] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [x] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-12982) Extend test suite of MockProcessSession
endzeit created NIFI-12982:
--
Summary: Extend test suite of MockProcessSession
Key: NIFI-12982
URL: https://issues.apache.org/jira/browse/NIFI-12982
Project: Apache NiFi
Issue Type: Sub-task
Reporter: endzeit
Assignee: endzeit
As part of NIFI-12971 (or a subtask) most likely changes will be introduced to
both {{
StandardProcessorTestRunner}} and \{{MockProcessSession}}.
To reduce the risk of regressions introduced by those changes, the test suite
of \{{MockProcessSession}} should be extended to account for more scenarios,
regarding both expected successful and failing interactions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-12981) Remove Hive 3 Components
[ https://issues.apache.org/jira/browse/NIFI-12981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832605#comment-17832605 ] ASF subversion and git services commented on NIFI-12981: Commit 14cb3f00f80f335e3f9b0d88606b3b9a2ef82bd4 in nifi's branch refs/heads/main from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=14cb3f00f8 ] NIFI-12981 Removed Hive 3 Components - Moved nifi-hive-test-utils to nifi-iceberg-test-utils - Removed nifi-hive-bundle and include-hive3 profile Signed-off-by: Pierre Villard This closes #8588. > Remove Hive 3 Components > > > Key: NIFI-12981 > URL: https://issues.apache.org/jira/browse/NIFI-12981 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Following the release of Apache Hive 4.0.0, Apache NiFi components support > Hive 3 should be removed from the main branch. NiFi 2.0.0 Milestone 1 and > Milestone 2 bundles remain available in Maven Central. Future support for > Hive 4 can be considered separately. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12981) Remove Hive 3 Components
[ https://issues.apache.org/jira/browse/NIFI-12981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-12981: -- Fix Version/s: 2.0.0-M3 Resolution: Fixed Status: Resolved (was: Patch Available) > Remove Hive 3 Components > > > Key: NIFI-12981 > URL: https://issues.apache.org/jira/browse/NIFI-12981 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 2.0.0-M3 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Following the release of Apache Hive 4.0.0, Apache NiFi components support > Hive 3 should be removed from the main branch. NiFi 2.0.0 Milestone 1 and > Milestone 2 bundles remain available in Maven Central. Future support for > Hive 4 can be considered separately. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12981 Remove Hive 3 Components [nifi]
asfgit closed pull request #8588: NIFI-12981 Remove Hive 3 Components URL: https://github.com/apache/nifi/pull/8588 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12980 Deprecate Hive 3 Components for Removal [nifi]
pvillard31 closed pull request #8587: NIFI-12980 Deprecate Hive 3 Components for Removal URL: https://github.com/apache/nifi/pull/8587 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (NIFI-12980) Deprecate Hive 3 Components for Removal
[ https://issues.apache.org/jira/browse/NIFI-12980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-12980: -- Fix Version/s: 1.26.0 Resolution: Fixed Status: Resolved (was: Patch Available) > Deprecate Hive 3 Components for Removal > --- > > Key: NIFI-12980 > URL: https://issues.apache.org/jira/browse/NIFI-12980 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Fix For: 1.26.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Apache Hive has released version 4.0.0 incorporating a number changes from > the previous version. Following the NiFI 2.0 Release Goals of removing > support for previous major versions of various components, Hive 3 Processors > should be deprecated on the support branch for subsequent removal from the > main branch. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12980) Deprecate Hive 3 Components for Removal
[ https://issues.apache.org/jira/browse/NIFI-12980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17832602#comment-17832602 ] ASF subversion and git services commented on NIFI-12980: Commit af50fb594d4bf3b1327cf61cb83c9a3270935c84 in nifi's branch refs/heads/support/nifi-1.x from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=af50fb594d ] NIFI-12980 Deprecated Hive 3 Components for Removal Signed-off-by: Pierre Villard This closes #8587. > Deprecate Hive 3 Components for Removal > --- > > Key: NIFI-12980 > URL: https://issues.apache.org/jira/browse/NIFI-12980 > Project: Apache NiFi > Issue Type: Improvement >Reporter: David Handermann >Assignee: David Handermann >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Apache Hive has released version 4.0.0 incorporating a number changes from > the previous version. Following the NiFI 2.0 Release Goals of removing > support for previous major versions of various components, Hive 3 Processors > should be deprecated on the support branch for subsequent removal from the > main branch. -- This message was sent by Atlassian Jira (v8.20.10#820010)
