daryl | gopher slack bot | Chat library

When handling compiler errors, they should be addressed from the top down and include warnings. The first warning we see is:

When you iterate over your list by for item in transactions_clean: you get items for each list, so indexing them like item[1] would just give you string characters. If the order is always like customer -> sale -> thread_sold, you can do something like this:

If you set autodetect_column_names to true then the filter interprets the first line that it sees as the column names. If pipeline.workers is set to more than one then it is a race to see which thread sets the column names first. Since different workers are processing different lines this means it may not use the first line. You must set pipeline.workers to 1.

In addition to that, the java execution engine (enabled by default) does not always preserve the order of events. There is a setting pipeline.ordered in logstash.yml that controls that. In 7.9 that keeps event order iff pipeline.workers is set to 1.

You do not say which version you are running. For anything from 7.0 (when java_execution became the default) to 7.6 the fix is to disable the java engine using either pipeline.java_execution: false in logstash.yml or --java_execution false on the command line. For any 7.x release from 7.7 onwards, make sure pipeline.ordered is set to auto or true (auto is the default in 7.x). In future releases (8.x perhaps) pipeline.ordered will default to false.

In terms of efficiency, the most efficient solution would be iterating over the input String, S once and, writing the solution into a stream. Now let's compare it with your implementation.

• S.split("\n"); requires full iteration over S pulse you create additional memory of the size of S
• al.add(rows[i]); you convert the String array to List, I don't see any need for that, but I don't think it affects the performance much.
• al.get(i).contains(",NULL,") that iterate over the entire String, and you got three such conditions, so you iterate over S three times here(in the worst case since if the first or condition is true the others will not be checked).
• finalString += al.get(i) + "\n"; Here you are reconstructing the solution without the filtered rows. The problem with += on Strings is that it each time creates a new instance of the String. This makes your implementation O(N^2) instead of O(N). Switch to a StringBuilder and you will return into the O(N) space. With modern ADE like IntelliJ, you will get a warning and it will update your code automatically.
• finalString.substring(0, finalString.length() - 1); Again in here you are creating a new instance of the String so it costs you S

To implement a simple-efficient solution I would do the following

• Split S by \n as you did
• Iterate over the String array and filter out the rows with Null
• Then use a StringBuilder to combine the results

For the filtering I would do something like:

That's the normal behavior of the useEffect hook.
You can add your own logic determening when it should or should not call a function at page load, like by checking if the array is empty or not.

You can try to achieve by implementing custom sort and custom filter for table.

Custom Sort (documentation):

Two steps:

1. Create a new key with a value copied from an existing key
2. Delete the key you just copied the value from

Working Example:

You are creating a new item object and returning that object so it is not keeping the older keys. I have modified your code logic.

Assuming the first name never has a space in it, you can use string.split

You can then use Array.prototype.shift to get the first element and join the rest back together.

For my example I changed the first name to have a last name with 2 words as a demonstration