TheGreatRandall opened a new pull request, #6755:
URL: https://github.com/apache/nifi/pull/6755

   <!-- 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. -->
   
   # Summary
   
   [NIFI-10944](https://issues.apache.org/jira/browse/NIFI-10944)
   Following the problem in the issue NIFI-10944. I set several printfs to see 
why the assertion can not been passed. When I print out the value of 
"firstRecord.getGroup("mymap",0)", it gave me {"b" : 2, "a" : 1}. However, when 
the data been initialized at setUp() function in the same class, the data was 
stored to the record should be {"a" : 1,  "b" : 2}. I also set the breakpoint 
before and after the data been read to record1 by following code:
   ```
           DatumReader<GenericRecord> datumReader = new 
GenericDatumReader<>(schema);
           DataFileReader<GenericRecord> dataFileReader = new 
DataFileReader<>(tmpAvro, datumReader);
           GenericRecord record1 = null;
           while (dataFileReader.hasNext()) {
               record1 = dataFileReader.next(record1);
               records.add(record1);
           }
   ```
   Before this code, the map value was {"a" : 1,  "b" : 2}, and after the code 
the map value become {"b" : 2, "a" : 1}. Sadly, the read code implement some 
third party package which I can not read the source code. Since the original 
assertion is trying to determine if the data in firstRecord the same as the 
data we input. So I make two maps which  one of them extracted the value in 
firstRecord and store the input value in the other to see if they are equal.
   
   By changing this, the bug has been fixed and it's not flaky anymore and can 
pass the NonDex's check.
   
   # 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-00000`
   - [X] Pull Request commit message starts with Apache NiFi Jira issue number, 
as such `NIFI-00000`
   
   ### 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
   
   - [ ] Build completed using `mvn clean install -P contrib-check`
     - [X] JDK 8
     - [ ] JDK 11
     - [ ] JDK 17
   
   ### Licensing
   
   - [ ] 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)
   - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` 
files
   
   ### Documentation
   
   - [ ] 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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to