I also deleted the watch that postmas...@opentext.net apparently auto-created on this issue… cascading shitstorm.
-- Steve www.lucidworks.com > On Jan 17, 2017, at 7:14 PM, Steve Rowe (JIRA) <j...@apache.org> wrote: > > > [ > https://issues.apache.org/jira/browse/SOLR-8029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Steve Rowe updated SOLR-8029: > ----------------------------- > Comment: was deleted > > (was: Delivery has failed to these recipients or groups: > > postmas...@opentext.net<mailto:postmas...@opentext.net> > The e-mail address you entered couldn't be found. Please check the > recipient's e-mail address and try to resend the message. If the problem > continues, please contact your helpdesk. > > > > > > > > Diagnostic information for administrators: > > Generating server: opentext.net > > postmas...@opentext.net > #550 5.1.1 RESOLVER.ADR.RecipNotFound; not found ## > > Original message headers: > > Received: from wldmzsvc06.dmz.opentext.com (10.2.170.17) by > otwlxg10.opentext.net (10.2.103.151) with Microsoft SMTP Server id > 14.3.319.2; Tue, 17 Jan 2017 19:11:37 -0500 > Received: from mx0a-00102601.pphosted.com (mx0b-00102601.pphosted.com > [67.231.152.222]) by wldmzsvc06.dmz.opentext.com (8.14.4/8.14.4) with > ESMTP > id v0I0Bbed007477 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 > verify=NO) > for <postmas...@opentext.net>; Tue, 17 Jan 2017 19:11:37 -0500 > Received: from pps.filterd (m0044805.ppops.net [127.0.0.1]) by > mx0b-00102601.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v0I0BRcD024693 > for <postmas...@opentext.net>; Tue, 17 Jan 2017 19:11:37 -0500 > Received: from spamd1-us-west.apache.org (pnap-us-west-generic-nat.apache.org > [209.188.14.142]) by mx0b-00102601.pphosted.com with ESMTP id > 27ygp0w04b-1 > for <postmas...@opentext.net>; Tue, 17 Jan 2017 19:11:37 -0500 > Received: from localhost (localhost [127.0.0.1]) by > spamd1-us-west.apache.org > (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 81437C174C > for > <postmas...@opentext.net>; Wed, 18 Jan 2017 00:11:36 +0000 (UTC) > X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org > X-Spam-Flag: NO > X-Spam-Score: -0.185 > X-Spam-Level: > X-Spam-Status: No, score=-0.185 tagged_above=-999 required=6.31 > tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999, > URIBL_BLOCKED=0.001, URI_HEX=1.313, URI_NOVOWEL=0.5] > autolearn=disabled > Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost > (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with > ESMTP > id abTI3UGlWbgg for <postmas...@opentext.net>; Wed, 18 Jan 2017 00:11:34 > +0000 (UTC) > Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org > [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at > mx1-lw-us.apache.org) with ESMTP id 4DA5D60E3B for <postmas...@opentext.net>; > Wed, 18 Jan 2017 00:11:33 +0000 (UTC) > Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by > mailrelay1-us-west.apache.org (ASF Mail Server at > mailrelay1-us-west.apache.org) with ESMTP id 4897CEAACD for > <postmas...@opentext.net>; Wed, 18 Jan 2017 00:11:30 +0000 (UTC) > Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by > jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP > id CB9C6252A7 for <postmas...@opentext.net>; Wed, 18 Jan 2017 00:11:28 +0000 > (UTC) > Date: Wed, 18 Jan 2017 00:11:28 +0000 > From: "Steve Rowe (JIRA)" <j...@apache.org> > To: <postmas...@opentext.net> > Message-ID: <jira.12863036.1441888832000.34491.1484698288...@atlassian.jira> > In-Reply-To: <jira.12863036.1441888832...@atlassian.jira> > References: <jira.12863036.1441888832...@atlassian.jira> > <jira.12863036.1441888832...@jira-lw-us.apache.org> > Subject: [jira] [Issue Comment Deleted] (SOLR-8029) Modernize and > standardize Solr APIs > Content-Type: text/plain; charset="utf-8" > X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 > X-CLX-Shades: None > X-CLX-Response: 1TFkXGBsTEQpMehcaEQpZTRdkRURPEQpZSRcacRoQGncGGxMTcRMdEBp3Bhg > aBhoRClleF2hjZhEKSUYXRVpPRF5PUl51QkVZXk9OEQpDThdtbGBIWEttfUsTRnpke3xkbW4dW0 > 5oc2B9G1JnQGtJcxEKWFwXHwQaBBMcB0kZHBgeExtOBRsaBBsbGgQeEgQSHBAbHhofGhEKXlkXe > l5sTn8RCk1cFxgfHREKTFoXaWhpTU1dEQpMRhdsa2sRCkNaFxgaEwQbEhIEGx4EGx4YEQpCXhcb > EQpCRhdmRFl7SHJ5QHJMTBEKQkUXbwVgZlldaEBLH0YRCkJOF2FAQhNDU2tFZlJGEQpCTBdsBUZ > +HRwYfU5vSBEKQmwXaW5ITHtJaVpOfk4RCkJAF24fGkVhckxBWlhpEQpCWBd6ZHJLZ3seen1lcx > EKTV4XGxEKWlgXGREKcGcXbUZSQFp9Ym9+BWMQGhEKcGgXYR5BeRp4Rx5cTnAQGhEKcGgXYUxfb > EJeYwVcBXsQGhEKcGgXbUAYTFNFYGJeTRoQGhEKcGgXZUlLX25sYRldQnkQGhEKcGgXbx1PeBli > W3xtWk8QGhEKcH8XaR5ee2BleUNiSAUQGxkcEQpwXxdge2kaS0hQYRhOeRAcGhEKcH0XY1lMX30 > fYhNkeFsQGhEKcGcXentSGmRrSHxOTGEQGhEKcGcXYHNOZAEYWRxcZR4QGhEKcGcXZVh+EhNHXm > dQRn0QGhEKcH0XZm5vTnxufUFARk0QHhIRCnB/F3p7fxxuX1JzfhNFEB4cEQpwXxdhbxtZSRlFe > XlvHxAeEhEKcH0XZGRsX1tyeHNLbEEQHhIRCnBsF2dhR21rSEISYnloEBoRCnBDF2NecxNnAUZs > elBsEB0aEQptfhcbEQpYTRdLESA= > Content-Transfer-Encoding: Quoted-printable > MIME-Version: 1.0 > X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, > definitions=2017-01-17_17:,, > signatures=0 > X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 > priorityscore=0 malwarescore=0 > suspectscore=1 phishscore=0 bulkscore=0 spamscore=0 clxscore=219 > lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 > reason=mlx scancount=1 engine=8.0.1-1612050000 definitions=main-1701180001 > Return-Path: j...@apache.org > > ) > >> Modernize and standardize Solr APIs >> ----------------------------------- >> >> Key: SOLR-8029 >> URL: https://issues.apache.org/jira/browse/SOLR-8029 >> Project: Solr >> Issue Type: Improvement >> Affects Versions: 6.0 >> Reporter: Noble Paul >> Assignee: Noble Paul >> Labels: API, EaseOfUse >> Fix For: 6.0 >> >> Attachments: SOLR-8029.patch, SOLR-8029.patch, SOLR-8029.patch, >> SOLR-8029.patch >> >> >> Solr APIs have organically evolved and they are sometimes inconsistent with >> each other or not in sync with the widely followed conventions of HTTP >> protocol. Trying to make incremental changes to make them modern is like >> applying band-aid. So, we have done a complete rethink of what the APIs >> should be. The most notable aspects of the API are as follows: >> The new set of APIs will be placed under a new path {{/solr2}}. The legacy >> APIs will continue to work under the {{/solr}} path as they used to and they >> will be eventually deprecated. >> There are 4 types of requests in the new API >> * {{/v2/<collection-name>/*}} : Hit a collection directly or manage >> collections/shards/replicas >> * {{/v2/<core>/*}} : Hit a core directly or manage cores >> * {{/v2/cluster/*}} : Operations on cluster not pertaining to any collection >> or core. e.g: security, overseer ops etc >> This will be released as part of a major release. Check the link given below >> for the full specification. Your comments are welcome >> [Solr API version 2 Specification | http://bit.ly/1JYsBMQ] > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
