[jira] [Created] (NIFI-12503) Missing Documentation for nifi-api
Steven Matison created NIFI-12503: - Summary: Missing Documentation for nifi-api Key: NIFI-12503 URL: https://issues.apache.org/jira/browse/NIFI-12503 Project: Apache NiFi Issue Type: Improvement Reporter: Steven Matison Attachments: SAMSAL_0-1701894321710.png Community user has noticed that nifi-api docs are missing required request values. One such example is groupName on the api call for uploading process-groups: /process-groups/upload More dialouge and original conversation here: [https://community.cloudera.com/t5/Support-Questions/NIFI-API-REST-Upload-Json-definition-flow-file/m-p/380384#M244057] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (NIFI-11334) PutIceberg processor instance interference due same class loader usage
[ https://issues.apache.org/jira/browse/NIFI-11334 ] Steven Matison deleted comment on NIFI-11334: --- was (Author: JIRAUSER285820): [~mbathori] [~joewitt] I ran into this testing with 1.23.1.2.1.6.0-323. It is somewhat repeatable. 3 Process groups, 3 putIcebergs, Single Kerberos Controller service. > PutIceberg processor instance interference due same class loader usage > -- > > Key: NIFI-11334 > URL: https://issues.apache.org/jira/browse/NIFI-11334 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Mark Bathori >Assignee: Mark Bathori >Priority: Major > Fix For: 2.0.0, 1.23.0 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > If more than one PutIceberg processor instance is being used simultaneous > e.g. with different Kerberos services then the underlying contexts can > interfere with each other. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11334) PutIceberg processor instance interference due same class loader usage
[ https://issues.apache.org/jira/browse/NIFI-11334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17772199#comment-17772199 ] Steven Matison commented on NIFI-11334: --- [~mbathori] [~joewitt] I ran into this testing with 1.23.1.2.1.6.0-323. It is somewhat repeatable. 3 Process groups, 3 putIcebergs, Single Kerberos Controller service. > PutIceberg processor instance interference due same class loader usage > -- > > Key: NIFI-11334 > URL: https://issues.apache.org/jira/browse/NIFI-11334 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Mark Bathori >Assignee: Mark Bathori >Priority: Major > Fix For: 2.0.0, 1.23.0 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > If more than one PutIceberg processor instance is being used simultaneous > e.g. with different Kerberos services then the underlying contexts can > interfere with each other. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-6633) Allow user to copy a parameter context
[ https://issues.apache.org/jira/browse/NIFI-6633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17771549#comment-17771549 ] Steven Matison commented on NIFI-6633: -- I ran into this one today. We are working with duplicate flows (per user/team) in a single environment. When we deploy duplicate flows, the parameter context is shared across all instances. The second and following flow copies require making new parameter contexts. > Allow user to copy a parameter context > -- > > Key: NIFI-6633 > URL: https://issues.apache.org/jira/browse/NIFI-6633 > Project: Apache NiFi > Issue Type: New Feature > Components: Core UI >Reporter: Rob Fellows >Priority: Major > > It would be nice to be able to copy/duplicate an existing parameter context. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11608) PutBigQuery: Missing Flowfile Attribute Evaluation
[ https://issues.apache.org/jira/browse/NIFI-11608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17728036#comment-17728036 ] Steven Matison commented on NIFI-11608: --- [~jisaitua] working on this now! Thanks! > PutBigQuery: Missing Flowfile Attribute Evaluation > -- > > Key: NIFI-11608 > URL: https://issues.apache.org/jira/browse/NIFI-11608 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.21.0 >Reporter: Juan Ignacio Saitua >Assignee: Steven Matison >Priority: Major > Time Spent: 2.5h > Remaining Estimate: 0h > > While the documentation states that PutBigQuery should support expression > language for DATASET, TABLE_NAME, and SKIP_INVALID_ROWS, that's not really > happening. An examination of the code reveals that these expressions are not > evaluated in the current implementation ([see code > here](https://github.com/apache/nifi/blob/cfd62c9511e43d5010fbfbb12b98b40bdfdb3fc2/nifi-nar-bundles/nifi-gcp-bundle/nifi-gcp-processors/src/main/java/org/apache/nifi/processors/gcp/bigquery/PutBigQuery.java#L193)). > Notably, the issue does not exist in the PutBigQueryBatch processor. While > both processors extends the AbstractBigQueryProcessor class, only > PutBigQueryBatch utilizes the AbstractBigQueryProcessor.getTableId() method, > which correctly evaluates and retrieves the tableId. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11608) PutBigQuery: Missing Flowfile Attribute Evaluation
[ https://issues.apache.org/jira/browse/NIFI-11608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Matison updated NIFI-11608: -- Fix Version/s: 1.22.0 > PutBigQuery: Missing Flowfile Attribute Evaluation > -- > > Key: NIFI-11608 > URL: https://issues.apache.org/jira/browse/NIFI-11608 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.21.0 >Reporter: Juan Ignacio Saitua >Assignee: Steven Matison >Priority: Major > Fix For: 1.22.0 > > Time Spent: 2h 10m > Remaining Estimate: 0h > > While the documentation states that PutBigQuery should support expression > language for DATASET, TABLE_NAME, and SKIP_INVALID_ROWS, that's not really > happening. An examination of the code reveals that these expressions are not > evaluated in the current implementation ([see code > here](https://github.com/apache/nifi/blob/cfd62c9511e43d5010fbfbb12b98b40bdfdb3fc2/nifi-nar-bundles/nifi-gcp-bundle/nifi-gcp-processors/src/main/java/org/apache/nifi/processors/gcp/bigquery/PutBigQuery.java#L193)). > Notably, the issue does not exist in the PutBigQueryBatch processor. While > both processors extends the AbstractBigQueryProcessor class, only > PutBigQueryBatch utilizes the AbstractBigQueryProcessor.getTableId() method, > which correctly evaluates and retrieves the tableId. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11608) PutBigQuery: Missing Flowfile Attribute Evaluation
[ https://issues.apache.org/jira/browse/NIFI-11608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17727913#comment-17727913 ] Steven Matison commented on NIFI-11608: --- This came up in a community post so I decided to jump in. Solution worked on with [~exceptionfactory] . Thank you David for your guidance through debug and PR process. > PutBigQuery: Missing Flowfile Attribute Evaluation > -- > > Key: NIFI-11608 > URL: https://issues.apache.org/jira/browse/NIFI-11608 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.21.0 >Reporter: Juan Ignacio Saitua >Assignee: Steven Matison >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > While the documentation states that PutBigQuery should support expression > language for DATASET, TABLE_NAME, and SKIP_INVALID_ROWS, that's not really > happening. An examination of the code reveals that these expressions are not > evaluated in the current implementation ([see code > here](https://github.com/apache/nifi/blob/cfd62c9511e43d5010fbfbb12b98b40bdfdb3fc2/nifi-nar-bundles/nifi-gcp-bundle/nifi-gcp-processors/src/main/java/org/apache/nifi/processors/gcp/bigquery/PutBigQuery.java#L193)). > Notably, the issue does not exist in the PutBigQueryBatch processor. While > both processors extends the AbstractBigQueryProcessor class, only > PutBigQueryBatch utilizes the AbstractBigQueryProcessor.getTableId() method, > which correctly evaluates and retrieves the tableId. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-11608) PutBigQuery: Missing Flowfile Attribute Evaluation
[ https://issues.apache.org/jira/browse/NIFI-11608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Matison reassigned NIFI-11608: - Assignee: Steven Matison > PutBigQuery: Missing Flowfile Attribute Evaluation > -- > > Key: NIFI-11608 > URL: https://issues.apache.org/jira/browse/NIFI-11608 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.21.0 >Reporter: Juan Ignacio Saitua >Assignee: Steven Matison >Priority: Major > > While the documentation states that PutBigQuery should support expression > language for DATASET, TABLE_NAME, and SKIP_INVALID_ROWS, that's not really > happening. An examination of the code reveals that these expressions are not > evaluated in the current implementation ([see code > here](https://github.com/apache/nifi/blob/cfd62c9511e43d5010fbfbb12b98b40bdfdb3fc2/nifi-nar-bundles/nifi-gcp-bundle/nifi-gcp-processors/src/main/java/org/apache/nifi/processors/gcp/bigquery/PutBigQuery.java#L193)). > Notably, the issue does not exist in the PutBigQueryBatch processor. While > both processors extends the AbstractBigQueryProcessor class, only > PutBigQueryBatch utilizes the AbstractBigQueryProcessor.getTableId() method, > which correctly evaluates and retrieves the tableId. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-10120) Refactor CassandraSessionProvider to use the latest Cassandra driver
[ https://issues.apache.org/jira/browse/NIFI-10120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17697108#comment-17697108 ] Steven Matison commented on NIFI-10120: --- Passing code changes to [~mike.thomsen] PR of my single branch of changes: [https://github.com/apache/nifi/pull/7015] My larger branch of changes leading up to NIFI-10120-1 is: [https://github.com/apache/nifi/compare/main...steven-matison:nifi:nifi-10120] > Refactor CassandraSessionProvider to use the latest Cassandra driver > > > Key: NIFI-10120 > URL: https://issues.apache.org/jira/browse/NIFI-10120 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Mike Thomsen >Assignee: Steven Matison >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11132) NiFI API Docs Hard to Navigate
[ https://issues.apache.org/jira/browse/NIFI-11132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17683911#comment-17683911 ] Steven Matison commented on NIFI-11132: --- Docs also do not provide how to send the ID: *GET https:///nifi-api/flowfile-queues//flowfiles//content?clusterNodeId=* > NiFI API Docs Hard to Navigate > -- > > Key: NIFI-11132 > URL: https://issues.apache.org/jira/browse/NIFI-11132 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation Website >Reporter: Steven Matison >Assignee: Steven Matison >Priority: Minor > Attachments: Screen Shot 2023-02-02 at 9.45.35 AM.png, Screen Shot > 2023-02-02 at 9.45.43 AM.png > > > In nifi api docs, users are not able to understand the required values in a > given request. Specifically one such example is GET FLOWFILE, GET FLOWFILE > CONTENT. The first response has an entity. I found today it is 2 clicks > into the popup modal before the full entity is documented. Additionally, > users may not even know that parent entity and weird open json thing is even > a link/clickable > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-11132) NiFI API Docs Hard to Navigate
[ https://issues.apache.org/jira/browse/NIFI-11132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Matison reassigned NIFI-11132: - Assignee: Steven Matison > NiFI API Docs Hard to Navigate > -- > > Key: NIFI-11132 > URL: https://issues.apache.org/jira/browse/NIFI-11132 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation Website >Reporter: Steven Matison >Assignee: Steven Matison >Priority: Minor > Attachments: Screen Shot 2023-02-02 at 9.45.35 AM.png, Screen Shot > 2023-02-02 at 9.45.43 AM.png > > > In nifi api docs, users are not able to understand the required values in a > given request. Specifically one such example is GET FLOWFILE, GET FLOWFILE > CONTENT. The first response has an entity. I found today it is 2 clicks > into the popup modal before the full entity is documented. Additionally, > users may not even know that parent entity and weird open json thing is even > a link/clickable > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11132) NiFI API Docs Hard to Navigate
Steven Matison created NIFI-11132: - Summary: NiFI API Docs Hard to Navigate Key: NIFI-11132 URL: https://issues.apache.org/jira/browse/NIFI-11132 Project: Apache NiFi Issue Type: Improvement Components: Documentation Website Reporter: Steven Matison Attachments: Screen Shot 2023-02-02 at 9.45.35 AM.png, Screen Shot 2023-02-02 at 9.45.43 AM.png In nifi api docs, users are not able to understand the required values in a given request. Specifically one such example is GET FLOWFILE, GET FLOWFILE CONTENT. The first response has an entity. I found today it is 2 clicks into the popup modal before the full entity is documented. Additionally, users may not even know that parent entity and weird open json thing is even a link/clickable -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-10120) Refactor CassandraSessionProvider to use the latest Cassandra driver
[
https://issues.apache.org/jira/browse/NIFI-10120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17583613#comment-17583613
]
Steven Matison commented on NIFI-10120:
---
Options map now working for consistency level, socket options, and protocol
options. (/)
Options doc is here with allowed values:
[https://docs.datastax.com/en/drivers/java/4.7/com/datastax/oss/driver/api/core/config/TypedDriverOption.html]
Cleaning up some comments..
{code:java}
// the create function exists in following locations:
//
nifi-cassandra-processors/src/main/java/org/apache/nifi/processors/cassandra/AbstractCassandraProcessor.java
//
nifi-cassandra-processors/src/test/java/org/apache/nifi/processors/cassandra/AbstractCassandraProcessorTest.java
//
nifi-cassandra-processors/src/test/java/org/apache/nifi/processors/cassandra/PutCassandraQLTest.java
//
nifi-cassandra-bundle/nifi-cassandra-processors/src/test/java/org/apache/nifi/processors/cassandra/PutCassandraRecordTest.java
//
nifi-cassandra-bundle/nifi-cassandra-processors/src/test/java/org/apache/nifi/processors/cassandra/QueryCassandraTest.java
// new final 4.x function will need exist in all locations
{code}
latest updates here:
[https://github.com/steven-matison/nifi/commit/297e3e2f30639903d2a6d85c6361f0b547f71921]
> Refactor CassandraSessionProvider to use the latest Cassandra driver
>
>
> Key: NIFI-10120
> URL: https://issues.apache.org/jira/browse/NIFI-10120
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Mike Thomsen
>Assignee: Steven Matison
>Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-10120) Refactor CassandraSessionProvider to use the latest Cassandra driver
[
https://issues.apache.org/jira/browse/NIFI-10120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17582953#comment-17582953
]
Steven Matison commented on NIFI-10120:
---
I have consistencyLevel moved into Options Map and before that was working I
had some issues with Option and .ifPresent... However today I un
commented the 2 timeouts and now it builds:
[https://github.com/steven-matison/nifi/commit/bd9980f3421ae23a97a0a1aeea48e29eea13dbfe]
[{*}INFO{*}]
**
[{*}INFO{*}] *Reactor Summary for nifi-cassandra-bundle 1.17.0-SNAPSHOT:*
[{*}INFO{*}]
[{*}INFO{*}] nifi-cassandra-bundle .. *SUCCESS* [
1.890 s]
[{*}INFO{*}] nifi-cassandra-services-api *SUCCESS* [
4.191 s]
[{*}INFO{*}] nifi-cassandra-services *SUCCESS* [
12.776 s]
> Refactor CassandraSessionProvider to use the latest Cassandra driver
>
>
> Key: NIFI-10120
> URL: https://issues.apache.org/jira/browse/NIFI-10120
> Project: Apache NiFi
> Issue Type: Sub-task
>Reporter: Mike Thomsen
>Assignee: Steven Matison
>Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-10120) Refactor CassandraSessionProvider to use the latest Cassandra driver
[ https://issues.apache.org/jira/browse/NIFI-10120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17582949#comment-17582949 ] Steven Matison commented on NIFI-10120: --- Working on socket options within Options map. I think this is getting closer but I am confused by how to handle Optional [https://github.com/steven-matison/nifi/commit/792afed463c0a81e826b666cb552f9628f96f61b] > Refactor CassandraSessionProvider to use the latest Cassandra driver > > > Key: NIFI-10120 > URL: https://issues.apache.org/jira/browse/NIFI-10120 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Mike Thomsen >Assignee: Steven Matison >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-10120) Refactor CassandraSessionProvider to use the latest Cassandra driver
[ https://issues.apache.org/jira/browse/NIFI-10120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17565461#comment-17565461 ] Steven Matison commented on NIFI-10120: --- DriverConfigLoader [https://docs.datastax.com/en/drivers/java/4.14/com/datastax/oss/driver/api/core/config/DriverConfigLoader.html#fromMap-com.datastax.oss.driver.api.core.config.OptionsMap-] Need to evaluate Protocol & Socket Options as part of OptionsMap > Refactor CassandraSessionProvider to use the latest Cassandra driver > > > Key: NIFI-10120 > URL: https://issues.apache.org/jira/browse/NIFI-10120 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Mike Thomsen >Assignee: Steven Matison >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-6848) Migrate NiFi Site to ASF git build/deploy
[
https://issues.apache.org/jira/browse/NIFI-6848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17564979#comment-17564979
]
Steven Matison commented on NIFI-6848:
--
There is a PR for all of the bare minimum changes to roll current site in Hugo
Framework.
{quote}https://github.com/apache/nifi-site/pull/61{quote}
If you want to roll an example of the new hugo site, follow README on my repo
{quote}https://github.com/steven-matison/nifi-site
{quote}
> Migrate NiFi Site to ASF git build/deploy
> -
>
> Key: NIFI-6848
> URL: https://issues.apache.org/jira/browse/NIFI-6848
> Project: Apache NiFi
> Issue Type: Task
> Components: Documentation Website
>Reporter: Aldrin Piri
>Assignee: Andrew M. Lim
>Priority: Major
>
> Currently, NiFi's site is versioned in
> https://gitbox.apache.org/repos/asf?p=nifi-site.git but a scripted process
> via grunt, manually executed, is used to publish this site to the legacy CMS
> (svn) system. The CMS system is largely deprecated and targeted for EOL in
> the upcoming months. We should look to transition our repository/site over
> to the new approach outlined at https://s.apache.org/asfyaml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-10120) Refactor CassandraSessionProvider to use the latest Cassandra driver
Title: Message Title Steven Matison commented on NIFI-10120 Re: Refactor CassandraSessionProvider to use the latest Cassandra driver https://docs.datastax.com/en/drivers/java/4.1/ Add Comment This message was sent by Atlassian Jira (v8.20.10#820010-sha1:ace47f9)
[jira] [Commented] (NIFI-10120) Refactor CassandraSessionProvider to use the latest Cassandra driver
Title: Message Title Steven Matison commented on NIFI-10120 Re: Refactor CassandraSessionProvider to use the latest Cassandra driver Mike Thomsen the remaining tasks on this thread are: Consistency Level Protocol Options Socket Options Add Comment This message was sent by Atlassian Jira (v8.20.10#820010-sha1:ace47f9)
[jira] [Commented] (NIFI-10120) Refactor CassandraSessionProvider to use the latest Cassandra driver
[ https://issues.apache.org/jira/browse/NIFI-10120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17559358#comment-17559358 ] Steven Matison commented on NIFI-10120: --- [https://docs.datastax.com/en/developer/java-driver/4.14/manual/core/configuration/reference/] > Refactor CassandraSessionProvider to use the latest Cassandra driver > > > Key: NIFI-10120 > URL: https://issues.apache.org/jira/browse/NIFI-10120 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Mike Thomsen >Assignee: Steven Matison >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (NIFI-10120) Refactor CassandraSessionProvider to use the latest Cassandra driver
[ https://issues.apache.org/jira/browse/NIFI-10120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17558056#comment-17558056 ] Steven Matison commented on NIFI-10120: --- Created initial NIFI-10120 branch of my nifi fork: https://github.com/steven-matison/nifi/commit/77fb768c20c488fdefd3c801bd1a6b701320fd15 > Refactor CassandraSessionProvider to use the latest Cassandra driver > > > Key: NIFI-10120 > URL: https://issues.apache.org/jira/browse/NIFI-10120 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Mike Thomsen >Assignee: Steven Matison >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (NIFI-10120) Refactor CassandraSessionProvider to use the latest Cassandra driver
[ https://issues.apache.org/jira/browse/NIFI-10120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17556447#comment-17556447 ] Steven Matison commented on NIFI-10120: --- Reference to driver extras seems to be just for codec https://mvnrepository.com/artifact/com.datastax.oss/dsbulk-codecs-api > Refactor CassandraSessionProvider to use the latest Cassandra driver > > > Key: NIFI-10120 > URL: https://issues.apache.org/jira/browse/NIFI-10120 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Mike Thomsen >Assignee: Steven Matison >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (NIFI-10120) Refactor CassandraSessionProvider to use the latest Cassandra driver
[ https://issues.apache.org/jira/browse/NIFI-10120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17556398#comment-17556398 ] Steven Matison commented on NIFI-10120: --- [https://github.com/DataStax-Examples/java-cassandra-driver-from3x-to4x] > Refactor CassandraSessionProvider to use the latest Cassandra driver > > > Key: NIFI-10120 > URL: https://issues.apache.org/jira/browse/NIFI-10120 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Mike Thomsen >Assignee: Steven Matison >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Commented] (NIFI-10120) Refactor CassandraSessionProvider to use the latest Cassandra driver
[ https://issues.apache.org/jira/browse/NIFI-10120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17555079#comment-17555079 ] Steven Matison commented on NIFI-10120: --- [https://mvnrepository.com/artifact/com.datastax.oss/java-driver-core/4.14.0] [https://docs.datastax.com/en/developer/java-driver/4.14/upgrade_guide/] [https://docs.datastax.com/en/developer/java-driver/4.14/manual/core/] > Refactor CassandraSessionProvider to use the latest Cassandra driver > > > Key: NIFI-10120 > URL: https://issues.apache.org/jira/browse/NIFI-10120 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Mike Thomsen >Assignee: Steven Matison >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Assigned] (NIFI-9802) Initial work for NiFi Site migration: Implement new framework
[ https://issues.apache.org/jira/browse/NIFI-9802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Matison reassigned NIFI-9802: Assignee: (was: Steven Matison) > Initial work for NiFi Site migration: Implement new framework > - > > Key: NIFI-9802 > URL: https://issues.apache.org/jira/browse/NIFI-9802 > Project: Apache NiFi > Issue Type: Task > Components: Documentation Website >Reporter: Andrew M. Lim >Priority: Major > > As part of https://issues.apache.org/jira/browse/NIFI-6848, want to get the > current site working in a new framework with the required new git automation. > Then we can work on a facelift and improvements. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (NIFI-9802) Initial work for NiFi Site migration: Implement new framework
[ https://issues.apache.org/jira/browse/NIFI-9802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steven Matison reassigned NIFI-9802: Assignee: Steven Matison > Initial work for NiFi Site migration: Implement new framework > - > > Key: NIFI-9802 > URL: https://issues.apache.org/jira/browse/NIFI-9802 > Project: Apache NiFi > Issue Type: Task > Components: Documentation Website >Reporter: Andrew M. Lim >Assignee: Steven Matison >Priority: Major > > As part of https://issues.apache.org/jira/browse/NIFI-6848, want to get the > current site working in a new framework with the required new git automation. > Then we can work on a facelift and improvements. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (NIFI-6848) Migrate NiFi Site to ASF git build/deploy
[ https://issues.apache.org/jira/browse/NIFI-6848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17504924#comment-17504924 ] Steven Matison commented on NIFI-6848: -- We are just now getting started with discussing this in nifi community #apachenifiwebsite. > Migrate NiFi Site to ASF git build/deploy > - > > Key: NIFI-6848 > URL: https://issues.apache.org/jira/browse/NIFI-6848 > Project: Apache NiFi > Issue Type: Task > Components: Documentation Website >Reporter: Aldrin Piri >Assignee: Andrew M. Lim >Priority: Major > > Currently, NiFi's site is versioned in > https://gitbox.apache.org/repos/asf?p=nifi-site.git but a scripted process > via grunt, manually executed, is used to publish this site to the legacy CMS > (svn) system. The CMS system is largely deprecated and targeted for EOL in > the upcoming months. We should look to transition our repository/site over > to the new approach outlined at https://s.apache.org/asfyaml -- This message was sent by Atlassian Jira (v8.20.1#820001)
