When defining a Spring batch step, often common configurations are added to almost every step. In order to not violate DRY (Don’t Repeat Yourself), a StepBuilder can be customized upstream with all the shared configurations.
for(String name: names) {
System.out.println(name);
}
// This is called a method reference
names.foreach(System.out::println);
When you want to query only on results from today in a Postgres database use the >= now()::date syntax.
To find a file from the command line:
brew tap heroku/brew && brew install heroku
heroku autocomplete
printf "$(heroku autocomplete:script bash)" >> ~/.bashrc; source ~/.bashrc
To use autocomplete type: Heroku and Tab,Tab
In order to view git history from the command line:
Often we have to loop through a list of items and convert it into a map, with the key being some sort of category and the value being a set of the associated items ie Map<Key, Set<Object>>. The old way of doing this looped through the list and before adding checked if the key was present. Using computeIfAbsent we can clean up this syntax considerably.
In Spring Batch, in order to get the job_execution_id of the last batch job instance for a given batch job name use this query:
