Submitted patches

Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14  ...
Show: all, applied, pending, rejected
Patch Description Author Branch Submit Time Action Status Test Status
 ticket:1335 - transient structs interact more flexibly and correctly with unary and binary ops Summary: External changes: queries such as {c.0, c.2, c.1, c.9} from a collection with a struct of 10 types will now distribute most binary and unary ops band-wise. Internal changes: Reduced overly-assertive type checking in & implemented a checkType method in which permits transient structured tiles. Test Plan: test_select Reviewers: dmisev Differential Revision:   master   2017-06-28 10:16:11     APPLIED   SUCCESS 
 ticket:1557 - addition of stddev / var condensers Summary: Added var_pop, var_samp, stddev_pop, stddev_samp operations implemented according to the SQL standard. Test Plan: Queries 'select var_pop(c) from nulltest as c' etc... Reviewers: dmisev, bbell Reviewed By: dmisev Differential Revision:   master   2017-06-27 13:35:02     APPLIED   SUCCESS 
 ticket:502 - Migrate from legacy database to new database internally in new Petascope when it starts (new Petascope part 3) Summary: Instead of providing the external services to execute the migration from legacy petascopedb to new cisdb manually as before, now it will check if it should run the migration when the web application starts. Also, when migrating, all requests connect to server will return information message about the migration. Test Plan: Tested manually when new Petascope starts. Reviewers: vmerticariu, dmisev Differential Revision:   release_9.5   2017-06-27 10:31:07     APPLIED   SUCCESS 
 ticket:1566 added support for python statements in wcst_import   master   2017-06-26 12:30:12     APPLIED   SUCCESS 
 ticket:1587 - WCST_Import error when a CRS axisDirection has the same name for both X, Y Summary: For example: http://localhost:8080/def/crs/EPSG/0/3031 it has 2 X,Y axes (East, North) but same name in axisDirection for them. So, offset vectors for X, Y axes will be the same and Petascope considers it is only 1 axis and throws exception due to difference in dimensionality from the axis subsets and axes in the GML file. Test Plan: Run the test in test_all_wcst_import for this case. Reviewers: dmisev, vmerticariu Differential Revision:   master   2017-06-22 08:49:10     APPLIED   SUCCESS 
 ticket:1565 - WCST_Import Send UpdateWcsLayer request to WMS handler instead of InsertWcsLayer request when layer already existed (new Petascope Part 1) Summary: WCS_Import did not check if a WMS layer with same name as coverage Id already existed in service endpoint so it always sends the request to import a WMS layer with parameter InsertWCSLayer. It should send a request with UpdateWCSLayer when a WMS layer already imported and update this layer with new metadata from update coverage. Test Plan: Run test wcst_import for the test with duplicate wms_layer name. Reviewers: vmerticariu, dmisev Differential Revision:   release_9.5   2017-06-21 14:33:37     APPLIED   SUCCESS 
 ticket:502 - Use Liquibase as database schema versions control in new Petascope (new Petascope part 2) Summary: Using Liquibase to control the database schema versions file internally in new Petascope. Liquibase will help to generated the diff between the current database version and development database version in XML file and provide the commands to solve in difficult cases. Also, the XML file could be applied for common databases, also it is still not good with embedded database like H2, HSQL when upgrading to new schema versions in some cases, but in general, no open source tool can be better than Liquibase. Flywaydb is database dependent, no difference from legacy (i.e: Hibernate can support 10 commont relational databases, Flywaydb will need 10 diff files for each database as each database has different SQL syntax for create/delete/update tables, columns, keys,...) while Liquibase uses abstract XML commands and generate to target database internally, so write one and run in multiple databases. Test Plan: Build petascope and install then run system test services. Reviewers: vmerticariu, dmisev Differential Revision:   release_9.5   2017-06-21 11:02:46     APPLIED   SUCCESS 
 ticket:1585 - Raswct sends raw POST WCPS request to Petascope Summary: The problem is from raswct as it should send a WCPS with raw POST request to Petascope as the older one in Earthlook client (​ The new change in raswct, it uses a new javascript method to send an ajax request with incorrect POST payload as KVP. Test Plan: The changed method was tested with ​ Reviewers: vmerticariu, dmisev Differential Revision:   master   2017-06-21 11:00:40     APPLIED   SUCCESS 
 ticket:1574 - WCS-Client error with library when displaying a lot of coverages with GetCapabilities Summary: WCS-Client with the library code-pretty trying to parse the result from GetCapabilities in XML and put it in a text box with colorful text. However, in case of PlanetServer-2 with very large XML result from GetCapabilities, this library cannot handle and Browser will freeze. It should only load a part of the content when it is too large to display in Browser. Test Plan: Tested with PlanetServer-2, takes 5 seconds to load 4500 coverages in web-client. The maxium length is calculated with the need to display the whole DescribeCoverage result which is important. Reviewers: vmerticariu, dmisev Differential Revision:   master   2017-06-21 07:01:27     APPLIED   SUCCESS 
 ticket:893 - Addition of 'is null' and 'is not null' operations Summary: Addition of 'is null' and 'is not null' operations. Grammar has been extended to accept 'is null' and 'is not null'. Then they are implemented as unary operations for some BaseTypes. Test Plan: 'select (1L is null)' , 'select (1L is not null)' Reviewers: dmisev, vmerticariu Reviewed By: dmisev Differential Revision:   master   2017-06-20 16:29:59     APPLIED   SUCCESS 

Submit a new patch

Select your locally generated patch file below for upload. Note that the patch can only be accepted if you agree to the Rasdaman Contribution Agreement by ticking the checkbox.

See How to submit patches for a step-by-step guide, in particular regarding the patch subject format. In order to ensure quick processing and to avoid rejection, you may want to make sure your patch adheres to the rasdaman code guide.

Select the code branch below to which you want to commit (help); if you are not sure what this means just leave the default (master).

I agree to the Rasdaman Contribution Agreement.