Bug 54153 - SampleSender should take into account SaveService configuration to remove data not persisted by SaveService
Summary: SampleSender should take into account SaveService configuration to remove dat...
Status: NEW
Alias: None
Product: JMeter
Classification: Unclassified
Component: Main (show other bugs)
Version: 2.8
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: JMeter issues mailing list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-15 21:28 UTC by Philippe Mouawad
Modified: 2012-11-16 17:15 UTC (History)
1 user (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philippe Mouawad 2012-11-15 21:28:48 UTC
Today SampleSender does not take into account SaveService configuration in remote sampling.
This leads SampleSender to send data to controller that is not persisted by SaveService. 
This should be changed by maybe sending SaveService Configuration summary of Controller to servers so that they can remove non persisted fields
Comment 1 Philippe Mouawad 2012-11-16 06:37:44 UTC
At start of test, we could send a simple bean 
representing what has been configured in CSVSaveService or SaveService,
And we could implement a new SampleSender using that config.
Comment 2 Sebb 2012-11-16 17:15:57 UTC
Since the entire test plan is sent to the server (some classes are modified slightly), I would expect the configuration to be already present on the server.

It's just a question of finding the correct place plug the code in.

Warning: a single sample may be processed by several different listeners, each of which may have different configuration setttings, so the original sample result must be preserved.

This means that a copy of the sample has to be created.
Might be sensible to provide a copy method that filters based on the SaveService configuration (rather than doing a full copy and adjusting it later).

It will of course be more work to create the copy, however it should allow the amount of transmitted data to be reduced.

Given that it may place an extra load on the server, I think the behaviour should be optional.