[jira] [Commented] (NIFI-6379) Add SSL Context Service Property to GetSQS Processor
[ https://issues.apache.org/jira/browse/NIFI-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17827212#comment-17827212 ] Reynaldo Rea commented on NIFI-6379: The SSL Context Service will be added to PutSNS, DeleteSQS, GetSQS, and PutSQS > Add SSL Context Service Property to GetSQS Processor > > > Key: NIFI-6379 > URL: https://issues.apache.org/jira/browse/NIFI-6379 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.7.1, 1.9.2 > Environment: GetSQS Processor >Reporter: John Crooke >Assignee: Reynaldo Rea >Priority: Major > > The GetSQS processor does NOT let you choose an SSL Context Service, but > other AWS-related processors such as "FetchS3Object" do have the "SSL Context > Service" property. > > This improvement is to enable the choice of SSL Context Service for the > certificate presented and/or the truststore that will be used to trust the > SQS endpoint's certificate. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-6379) Add SSL Context Service Property to GetSQS Processor
[ https://issues.apache.org/jira/browse/NIFI-6379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reynaldo Rea reassigned NIFI-6379: -- Assignee: Reynaldo Rea > Add SSL Context Service Property to GetSQS Processor > > > Key: NIFI-6379 > URL: https://issues.apache.org/jira/browse/NIFI-6379 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.7.1, 1.9.2 > Environment: GetSQS Processor >Reporter: John Crooke >Assignee: Reynaldo Rea >Priority: Major > > The GetSQS processor does NOT let you choose an SSL Context Service, but > other AWS-related processors such as "FetchS3Object" do have the "SSL Context > Service" property. > > This improvement is to enable the choice of SSL Context Service for the > certificate presented and/or the truststore that will be used to trust the > SQS endpoint's certificate. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-12674) Modify ValidateCSV to make schema optional
[ https://issues.apache.org/jira/browse/NIFI-12674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reynaldo Rea reassigned NIFI-12674: --- Assignee: Reynaldo Rea > Modify ValidateCSV to make schema optional > -- > > Key: NIFI-12674 > URL: https://issues.apache.org/jira/browse/NIFI-12674 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Reynaldo Rea >Assignee: Reynaldo Rea >Priority: Minor > > The schema for ValidateCSV should be optional. Whenever a schema is not > supplied, the processor should only validate the structural consistency of > the CSV using the header. > In addition, the processor will be given the ability to validate against a > given attribute. The value for the given attribute will be treated as CSV > text and validation will be done to that. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12674) Modify ValidateCSV to make schema optional
[ https://issues.apache.org/jira/browse/NIFI-12674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reynaldo Rea updated NIFI-12674: Description: The schema for ValidateCSV should be optional. Whenever a schema is not supplied, the processor should only validate the structural consistency of the CSV using the header. In addition, the processor will be given the ability to validate against a given attribute. The value for the given attribute will be treated as CSV text and validation will be done to that. was: The schema for ValidateCSV should be optional. Whenever a schema is not supplied, the processor should only validate the structural consistency of the CSV. In addition, if a schema is not provided, the processor should attempt to derive it from the header row. The processor should also be able to validate against the flowfile content or a specified flowfile attribute. > Modify ValidateCSV to make schema optional > -- > > Key: NIFI-12674 > URL: https://issues.apache.org/jira/browse/NIFI-12674 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Reynaldo Rea >Priority: Minor > > The schema for ValidateCSV should be optional. Whenever a schema is not > supplied, the processor should only validate the structural consistency of > the CSV using the header. > In addition, the processor will be given the ability to validate against a > given attribute. The value for the given attribute will be treated as CSV > text and validation will be done to that. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12674) Modify ValidateCSV to make schema optional
Reynaldo Rea created NIFI-12674: --- Summary: Modify ValidateCSV to make schema optional Key: NIFI-12674 URL: https://issues.apache.org/jira/browse/NIFI-12674 Project: Apache NiFi Issue Type: Improvement Components: Extensions Reporter: Reynaldo Rea The schema for ValidateCSV should be optional. Whenever a schema is not supplied, the processor should only validate the structural consistency of the CSV. In addition, if a schema is not provided, the processor should attempt to derive it from the header row. The processor should also be able to validate against the flowfile content or a specified flowfile attribute. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-12210) Implement recovery mode for WriteAheadFlowFileRepository
[ https://issues.apache.org/jira/browse/NIFI-12210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reynaldo Rea reassigned NIFI-12210: --- Assignee: Reynaldo Rea > Implement recovery mode for WriteAheadFlowFileRepository > > > Key: NIFI-12210 > URL: https://issues.apache.org/jira/browse/NIFI-12210 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Reporter: Reynaldo Rea >Assignee: Reynaldo Rea >Priority: Major > > The RocksDBFlowFileRepository has a "Recovery Mode" feature which limits the > number of FlowFiles that are loaded into the system and processed before more > FlowFiles are loaded in. This is useful when Nifi fails to start on a system > with insufficient memory. > The same feature should be added to the WriteAheadFlowFileRepository as the > RocksDBFlowFileRepository is depricated. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12210) Implement recovery mode for WriteAheadFlowFileRepository
Reynaldo Rea created NIFI-12210: --- Summary: Implement recovery mode for WriteAheadFlowFileRepository Key: NIFI-12210 URL: https://issues.apache.org/jira/browse/NIFI-12210 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Reporter: Reynaldo Rea The RocksDBFlowFileRepository has a "Recovery Mode" feature which limits the number of FlowFiles that are loaded into the system and processed before more FlowFiles are loaded in. This is useful when Nifi fails to start on a system with insufficient memory. The same feature should be added to the WriteAheadFlowFileRepository as the RocksDBFlowFileRepository is depricated. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-3785) Allow user to move Controller Service
[ https://issues.apache.org/jira/browse/NIFI-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reynaldo Rea updated NIFI-3785: --- Status: Patch Available (was: Open) > Allow user to move Controller Service > - > > Key: NIFI-3785 > URL: https://issues.apache.org/jira/browse/NIFI-3785 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Mark Payne >Assignee: Reynaldo Rea >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Currently, there is no way to move a Controller Service from one Process > Group to another. I would like to be able to move a Controller Service from > its Process Group to the "parent" Process Group in order to broaden its scope. > The ability to move the Controller Service to a child group in order to > narrow its scope would be convenient as well but may be difficult to provide > an intuitive user experience around. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-8606) Add Stop & Configure button to Controller Service Details dialog
[ https://issues.apache.org/jira/browse/NIFI-8606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reynaldo Rea updated NIFI-8606: --- Status: Patch Available (was: In Progress) > Add Stop & Configure button to Controller Service Details dialog > > > Key: NIFI-8606 > URL: https://issues.apache.org/jira/browse/NIFI-8606 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Affects Versions: 1.13.2 >Reporter: Mark Bean >Assignee: Reynaldo Rea >Priority: Minor > > This ticket is similar to NIFI-5986 which added the 'stop and configure' > option to a "Configure Processor" details dialog, i.e configure a processor. > The same feature should be available when in the "Controller Service > Details" dialog of a controller service. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-3785) Allow user to move Controller Service
[ https://issues.apache.org/jira/browse/NIFI-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reynaldo Rea reassigned NIFI-3785: -- Assignee: Reynaldo Rea > Allow user to move Controller Service > - > > Key: NIFI-3785 > URL: https://issues.apache.org/jira/browse/NIFI-3785 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Mark Payne >Assignee: Reynaldo Rea >Priority: Major > > Currently, there is no way to move a Controller Service from one Process > Group to another. I would like to be able to move a Controller Service from > its Process Group to the "parent" Process Group in order to broaden its scope. > The ability to move the Controller Service to a child group in order to > narrow its scope would be convenient as well but may be difficult to provide > an intuitive user experience around. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-8606) Add Stop & Configure button to Controller Service Details dialog
[ https://issues.apache.org/jira/browse/NIFI-8606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reynaldo Rea reassigned NIFI-8606: -- Assignee: Reynaldo Rea > Add Stop & Configure button to Controller Service Details dialog > > > Key: NIFI-8606 > URL: https://issues.apache.org/jira/browse/NIFI-8606 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Affects Versions: 1.13.2 >Reporter: Mark Bean >Assignee: Reynaldo Rea >Priority: Minor > > This ticket is similar to NIFI-5986 which added the 'stop and configure' > option to a "Configure Processor" details dialog, i.e configure a processor. > The same feature should be available when in the "Controller Service > Details" dialog of a controller service. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-10904) Changing Font Color for Dropdown Menu When Selecting Controller Services
[ https://issues.apache.org/jira/browse/NIFI-10904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reynaldo Rea reassigned NIFI-10904: --- Assignee: Reynaldo Rea (was: Anson Yu) > Changing Font Color for Dropdown Menu When Selecting Controller Services > > > Key: NIFI-10904 > URL: https://issues.apache.org/jira/browse/NIFI-10904 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Anson Yu >Assignee: Reynaldo Rea >Priority: Trivial > Attachments: GrayOut.PNG > > > When I was adding a controller service to a processor (such as > ConvertRecords) via the Properties tab in it's configurations, I noticed the > color of the base options in the dropdown containing "Reference parameter..." > & "Create new service..." used a grey color that gave the impression of it > being unavailable on first glance, even though were selectable options. I > think it would be better if the default color was something else. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11303) Create direct go-to option from Provenance lineage
[ https://issues.apache.org/jira/browse/NIFI-11303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reynaldo Rea updated NIFI-11303: Status: Patch Available (was: In Progress) > Create direct go-to option from Provenance lineage > -- > > Key: NIFI-11303 > URL: https://issues.apache.org/jira/browse/NIFI-11303 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.19.1 >Reporter: Mark Bean >Assignee: Reynaldo Rea >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The process to navigate from a Provenance event in the lineage diagram to the > component which generated the event is a little cumbersome. It requires > right-clicking on the event, choose 'View details', locating the Component > Id, returning to the main graph, entering the Component Id in the Search bar > and finally selecting the component. > It would be useful and more direct to have a "go to" link option available on > the context menu when right-clicking on the event. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-11303) Create direct go-to option from Provenance lineage
[ https://issues.apache.org/jira/browse/NIFI-11303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Reynaldo Rea reassigned NIFI-11303: --- Assignee: Reynaldo Rea > Create direct go-to option from Provenance lineage > -- > > Key: NIFI-11303 > URL: https://issues.apache.org/jira/browse/NIFI-11303 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.19.1 >Reporter: Mark Bean >Assignee: Reynaldo Rea >Priority: Major > > The process to navigate from a Provenance event in the lineage diagram to the > component which generated the event is a little cumbersome. It requires > right-clicking on the event, choose 'View details', locating the Component > Id, returning to the main graph, entering the Component Id in the Search bar > and finally selecting the component. > It would be useful and more direct to have a "go to" link option available on > the context menu when right-clicking on the event. -- This message was sent by Atlassian Jira (v8.20.10#820010)
