Community Edition 3.8.0 Release Candidate 0

Signed-off-by: Richard Chapman <rchapman@hpccsystems.com>
Unlock access to File monitor singleton

Added corresponding unlock for file monitoring singleton lock. Related to gh-2057 fix (#2170).

Fixes gh-2371

Signed-off-by: Sridhar Meda <sridhar.meda@lexisnexis.com>
Merge pull request #2373 from smeda/issue2371_1

Unlock File/Directory monitoring singleton

Reviewed-By: Richard Chapman <rchapman@hpccsystems.com>
ECLPlayground:  Fixed issue when hosted within an iFrame.

ECL Playground fails to load when it is hosted within a frame.  In IDE
this shows a popup window.  In regular IE it was a silent error.

Fixed an issue with result viewer inside a frame (not resizing on
initial load).

Fixed an issue parsing Key=Value params from URL (again related to fames
+ inner).

Fixes gh-2357
Fixes gh-2366

Signed-off-by: Gordon Smith <gordon.smith@lexisnexis.com>
Merge pull request #2378 from GordonSmith/Issue_2366

ECLPlayground: Fixed issue when hosted within an iFrame.

Reviewed-By: Richard Chapman <rchapman@hpccsystems.com>
Merge remote-tracking branch 'origin/candidate-3.8.x' into candidate-3.8.0

Signed-off-by: Richard Chapman <rchapman@hpccsystems.com>
Community Edition 3.8.0 Release Candidate 1

Signed-off-by: Richard Chapman <rchapman@hpccsystems.com>
#2391 Refactor project name to HPCC JDBC Driver

refactor directory structure.
refactor file names and java classes to accurately reflect function.
CMake changes to reflect directory and file refactoring.
New build flag is USE_HPCCJDBC

Signed-off-by: Rodrigo Pastrana <Rodrigo.Pastrana@lexisnexis.com>
ECLPlayground:  Updated samples.

Fixes gh_2283

Signed-off-by: Gordon Smith <gordon.smith@lexisnexis.com>
Merge pull request #2410 from GordonSmith/Issue_2283

ECLPlayground: Updated samples.

Reviewed-By: Richard Chapman <rchapman@hpccsystems.com>
Fix problem with memory allocator with few allocations

If a fixed size heaplet oscillated between having 0 and 1 entries
allocated within it, a situation could arise where the page was
continually being allocated and freed.  This change ensures the
last page is only freed when memory is critical.

Each attempt to allocate a page also checks if there are any pages
that can be freed up in any heaplet.  If one of the other heaplets
had large numbers of entries it could take a long time to check if that
heaplet had any pages that could be freed.   This should be addressed
separately.  However, the two combined caused a spike in cpu usage for
certain graphs.

Fixes #2402

Signed-off-by: Gavin Halliday <gavin.halliday@lexisnexis.com>
Merge pull request #2413 from ghalliday/lastpagefix

Fix problem with memory allocator with few allocations

Reviewed-By: Jake Smith <jake.smith@lexisnexis.com>
Reviewed-By: Richard Chapman <rchapman@hpccsystems.com>
Conditional crc checking memory allocator

Reinstate THOR_ROWCRC functionality

Signed-off-by: Jake Smith <jake.smith@lexisnexis.com>
Remove configmgr multiSlave references

Remove references to multiSlave attribute in ConfigMgr code. Xsl references have not been removed as comments mention backward compatibility.

Fixes gh-1742

Signed-off-by: Sridhar Meda <sridhar.meda@lexisnexis.com>
Merge remote-tracking branch 'origin/candidate-3.8.0' into candidate-3.8.x

Signed-off-by: Richard Chapman <rchapman@hpccsystems.com>
Fix bug in number of rows if transform has skip

DATASET(count, <transform-with-skip>) should have a row count range of
0..<count>, not just <count>

Signed-off-by: Gavin Halliday <gavin.halliday@lexisnexis.com>
Fix a couple of issues with the previous change

The last element in a huge heap was not being freed.  It should be,
since it is never reused anyway.

The regression tests were failing because of the new delay in releasing
the last page.

(Moved the flags field from the derived classes to base class)

Signed-off-by: Gavin Halliday <gavin.halliday@lexisnexis.com>
Potential aggregate merge issues if 0 recs on node

A node with no records was being treated as a default aggregate row, i.e.
result of clearAggregate()
This had consequences if the merging function was impacted by default
values.
The example where this was seen (in the ML library), was multiplying by a
field value in the aggregate row, the default value was 0.0, so the end
result was 0.0 if any node had 0 rows to aggregate.

Signed-off-by: Jake Smith <jake.smith@lexisnexis.com>
gh-2429 Remove hardcoded ip reference for roxie.

Was causing "Graph not Found" error when loading roxie graphs.

Signed-off-by: Jo Prichard <jo.prichard@lexisnexis.com>
Remove unecessary record size calls

No need to calc. size per aggregate processRow, do once when done

Signed-off-by: Jake Smith <jake.smith@lexisnexis.com>