objx | Go package for dealing with maps , slices , JSON | Map library

My question how to pass parameter from MasterJob to SubJob using JobStep approach?

The JobParametersExtractor is what you are looking for. It allows you to extract parameters from the main job and pass them to the subjob. You can find an example here.

EDIT: Adding suggestions based on comments

I have a list of X obj in the DB. X obj has among other fields, id, type(of work), name, state and blob which contains the csv file attached to it. The blob field containing the csv file depends on the type field so it's not one pattern csv file. I need to process each X obj and save the content of the csv file in the DB and generate a csv result file containing the original data plus a comment field in the result csv file and update X obj state with the result csv field attached to X obj and other fields.

As you can see, the process is already complex for a single X object. So trying to process all X objects in the same job of jobs is too complex IMHO. So much complexity in software comes from trying to make one thing do two things..

If there is better way to deal with this then I'm all yours!

Since you are open for suggestions, I will recommend two options:

Option 1:

If it were up to me, I would create a job instance per X obj. This way, I can 1) parallelize things and 2) in case of failure, restart only the failed job. These two characteristics (Scalability and Restartability) are almost impossible with the job of jobs approach. Even if you have a lot of X objects, this is not a problem. You can use one of the scaling techniques provided by Spring Batch to process things in parallel.

Option 2:

If you really can't or don't want to use different job instances, you can use a single job with a chunk-oriented step that iterates over X objects list. The processing logic seems independent from one record to another, so this step should be easily scalable with multiple threads.

Pass the object by reference into a write function instead:

I hope the following snippet can be of help, please do not hesitate to ask if there is any doubt.

Your impression is right. You can either

• compute the distance in local coordinates as the difference between event.x/y and event.subject.x/y

• retrieve the screen distance with event.clickDistance() as a getter

These two work in different coordinate systems.

• The client coordinate system is that of the browser viewport. They are just read from the native DOM mousemove event.
• The user coordinate system is the one of the thing being dragged, using the same coordinates as those used when writing SVG markup. They are computed from the client coordinates with a transform matrix the SVG API provides. The source code is here.

What you did was the in-between way that normally is not needed: by applying the scaleX/Y transform, you computed the coordinates in the system of the SVG viewBox, i. e. the coordinate system that is found when the viewBox is applied to the outermost element. That can be the client coordinate system, but only if the attribute is not set, or the width and height values of the element match the contents of the viewBox.

In almost every practical use case, the two will differ. The "Scalable" in SVG is just about that distinction. Leaving out the viewBox like you did deprives you of the possibility to easily scale your grafic as a whole.

You could map the arrays with new objects.

Since you didn't mention it above: did you instrument a Go application? The Elastic APM Go "Agent" is a package which you use to instrument your application source code. It is not an independent process, but runs within your application.

So, first (if you haven't already) instrument your application. See https://www.elastic.co/guide/en/apm/agent/go/current/getting-started.html#instrumenting-source

Here's an example web server using Echo, and the apmechov4 instrumentation module: