Return-Path: X-Original-To: apmail-oodt-commits-archive@www.apache.org Delivered-To: apmail-oodt-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 96672EBB0 for ; Fri, 14 Dec 2012 00:34:20 +0000 (UTC) Received: (qmail 26710 invoked by uid 500); 14 Dec 2012 00:34:20 -0000 Delivered-To: apmail-oodt-commits-archive@oodt.apache.org Received: (qmail 26677 invoked by uid 500); 14 Dec 2012 00:34:20 -0000 Mailing-List: contact commits-help@oodt.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@oodt.apache.org Delivered-To: mailing list commits@oodt.apache.org Received: (qmail 26669 invoked by uid 99); 14 Dec 2012 00:34:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Dec 2012 00:34:20 +0000 Date: Fri, 14 Dec 2012 00:34:20 +0000 (UTC) From: "Chris A. Mattmann (JIRA)" To: commits@oodt.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (OODT-158) QuerySets for XMLPS MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OODT-158?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:all-tabpanel ] Chris A. Mattmann updated OODT-158: ----------------------------------- Fix Version/s: (was: 0.5) 0.6 - push out to 0.6 =20 > QuerySets for XMLPS > ------------------- > > Key: OODT-158 > URL: https://issues.apache.org/jira/browse/OODT-158 > Project: OODT > Issue Type: Improvement > Components: xmlps > Reporter: Chris A. Mattmann > Assignee: Chris A. Mattmann > Labels: bakedin, query, queryset, xmlps > Fix For: 0.6 > > > [~davekale] and I have been discussing the notion of "query sets" for XML= PS. These would turn long, huge queryStrings for XMLPS, e.g.,: > {noformat} > http://host:8080/grid/prod?q=3DRETURN=3DID%20AND%20RETURN=3DUnitNumber%20= AND%20RETURN=3DAcctNum%20AND%20RETURN=3DHospitalAdmitDate%20AND%20RETURN=3D= AdmitDateTime%20AND%20RETURN=3DAdmitDate%20AND%20RETURN=3DAdmitTime%20AND%2= 0RETURN=3DService%20AND%20RETURN=3DAdmitCategory%20AND%20RETURN=3DZipCode%2= 0AND%20RETURN=3DZipRegion%20AND%20RETURN=3DOrigin%20AND%20RETURN=3DReferrin= gHospital%20AND%20RETURN=3DDoctor%20AND%20RETURN=3DReferringService%20AND%2= 0RETURN=3DDischargeCondition%20AND%20RETURN=3DDisposition%20AND%20RETURN=3D= Payment%20AND%20RETURN=3DPICULocation%20AND%20RETURN=3DDischargeDateTime%20= AND%20RETURN=3DDischargeDate%20AND%20RETURN=3DDischargeTime%20AND%20RETURN= =3DPlanned%20AND%20RETURN=3DPRISM%20AND%20RETURN=3DMortProb%20AND%20RETURN= =3DOperativeType%20AND%20RETURN=3DisScheduled%20AND%20RETURN=3DisTrauma%20A= ND%20RETURN=3DFEStudy%20AND%20RETURN=3DWeight%20AND%20RETURN=3DHeight%20AND= %20RETURN=3DHeadCircumference%20AND%20RETURN=3DAdmitPCPC%20AND%20RETURN=3DD= ischargePCPC%20AND%20RETURN=3DAdmitPOPC%20AND%20RETURN=3DDischargePOPC%20AN= D%20RETURN=3DToDoList%20AND%20RETURN=3DBed%20AND%20RETURN=3DResident%20AND%= 20RETURN=3DisVerified%20AND%20RETURN=3DVerifiedBy%20AND%20RETURN=3DOrganDon= or%20AND%20RETURN=3DOrganProcurementNotified%20AND%20RETURN=3DDeathReason%2= 0AND%20RETURN=3DDischargeNote%20AND%20RETURN=3DOriginText%20AND%20RETURN=3D= DispositionText%20AND%20RETURN=3DDeathNote%20AND%20RETURN=3DDeathFellow%20A= ND%20RETURN=3DDeathAttending%20AND%20RETURN=3DHospDCDate%20AND%20RETURN=3DH= ospDCStatus%20AND%20RETURN=3DADT%20AND%20RETURN=3DBillingSameIllness%20AND%= 20RETURN=3DBillingSameIllnessDate%20AND%20RETURN=3DBillingAccident%20AND%20= RETURN=3DBillingAccidentType%20AND%20RETURN=3DBillingEmergentService%20AND%= 20RETURN=3DBillingSimilarIllness%20AND%20RETURN=3DBillingSimilarIllnessDate= %20AND%20RETURN=3DBillingAccidentDate%20AND%20RETURN=3Dupsize_ts%20AND%20RE= TURN=3DFirstVital%20AND%20RETURN=3DLastVital%20AND%20RETURN=3Dinfluenza_lik= e_illness > {noformat} > into something like: > {noformat} > http://host:8080/grid/prod?q=3DRETURN%3DPICUDBQSET > {noformat} > which would then require some configuration say in XMLPS, something like: > {code:xml} > > ... > > > > ... > > > {code} > In other words, we're talking about baked-in, canned queries for XMLPS pr= od servers that are mainly used for dumping. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira