[ 
https://issues.apache.org/jira/browse/SOLR-9759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15862916#comment-15862916
 ] 

Gus Heck edited comment on SOLR-9759 at 2/12/17 7:01 PM:
---------------------------------------------------------

The size of my request was primarily because I don't know of a way to create 
parameterized subroutines (or perhaps reuse "named streams"). I had 4 basic 
operations that needed to be joined to 2 different data types (thus had to be 
duplicated), and within each of the 4 operations (now 8) there were 2 
complement operations... all from the same source, but again had to be 
duplicated. meaning there were 24 sources, and with some top and selects thrown 
in at various levels, I wound up with 128 nodes in the explain graph. Made for 
a pretty picture, but it was very un-DRY.


was (Author: gus_heck):
The size of my request was primarily because I don't know of a way to 
parameterized subroutines (or perhaps reuse "named streams"). I had 4 basic 
operations that needed to be joined to 2 different data types (thus had to be 
duplicated), and within each of the 4 operations (now 8) there were 2 
complement operations... all from the same source, but again had to be 
duplicated. meaning there were 24 sources, and with some top and selects thrown 
in at various levels, I wound up with 128 nodes in the explain graph. Made for 
a pretty picture, but it was very un-DRY.

> Admin UI should post streaming expressions
> ------------------------------------------
>
>                 Key: SOLR-9759
>                 URL: https://issues.apache.org/jira/browse/SOLR-9759
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: UI
>    Affects Versions: 6.2.1
>            Reporter: Gus Heck
>
> Haven't had the chance to test this in 6.3, but in 6.2.1 I just ran into 
> request entity too large, when I pasted an expression into the admin ui to 
> begin debugging it... 
> Furthermore, the UI gives no indication of any error at all, leading one to 
> sit, waiting for the response. Firefox JavaScript console shows a 413 
> response and this:
> {code}
> 11:01:11.095 Error: JSON.parse: unexpected character at line 1 column 1 of 
> the JSON data
> $scope.doStream/<@http://localhost:8984/solr/js/angular/controllers/stream.js:48:24
> v/</e[k]/n<@http://localhost:8984/solr/libs/angular-resource.min.js:33:133
> processQueue@http://localhost:8984/solr/libs/angular.js:13193:27
> scheduleProcessQueue/<@http://localhost:8984/solr/libs/angular.js:13209:27
> $RootScopeProvider/this.$get</Scope.prototype.$eval@http://localhost:8984/solr/libs/angular.js:14406:16
> $RootScopeProvider/this.$get</Scope.prototype.$digest@http://localhost:8984/solr/libs/angular.js:14222:15
> $RootScopeProvider/this.$get</Scope.prototype.$apply@http://localhost:8984/solr/libs/angular.js:14511:13
> done@http://localhost:8984/solr/libs/angular.js:9669:36
> completeRequest@http://localhost:8984/solr/libs/angular.js:9859:7
> requestLoaded@http://localhost:8984/solr/libs/angular.js:9800:9
> 1angular.js:11617:18
> consoleLog/<()angular.js:11617
> $ExceptionHandlerProvider/this.$get</<()angular.js:8567
> processQueue()angular.js:13201
> scheduleProcessQueue/<()angular.js:13209
> $RootScopeProvider/this.$get</Scope.prototype.$eval()angular.js:14406
> $RootScopeProvider/this.$get</Scope.prototype.$digest()angular.js:14222
> $RootScopeProvider/this.$get</Scope.prototype.$apply()angular.js:14511
> done()angular.js:9669
> completeRequest()angular.js:9859
> requestLoaded()angular.js:9800
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to