The patch for free-text entity search (to be in release 0.7) contains the renaming of ³pattern² parameter (to be added in release 0.6.1) to ³nameseq² in LIST API. In consideration of backward compatibility, can we include this renaming change in 0.6.1 as well? I¹ve filed a sub-task JIRA for this:
https://issues.apache.org/jira/browse/FALCON-1158 Rename the parameter "pattern" in LIST API to "nameseq" Thank you! Cheers, Ying On 4/13/15, 9:03 PM, "Ajay Yadav" <[email protected]> wrote: >I agree. We have significant improvements and fixes to do a release. It >will also give us chance to leverage/get early feedback on the new UI >(currently in alpha). > >On Tue, Apr 14, 2015 at 8:00 AM, Srikanth Sundarrajan ><[email protected]> >wrote: > >> Yes, We should prepare a release candidate and have it vetted. >> >> Regards >> Srikanth Sundarrajan >> >> ---------------------------------------- >> > Date: Tue, 14 Apr 2015 00:02:55 +0530 >> > Subject: Falcon 0.6.1 release >> > From: [email protected] >> > To: [email protected] >> > >> > Hi all, >> > We have been discussing for some time now that we should do a >>stability >> > release for Falcon (0.6.1). With FALCON-1146 >> > <https://issues.apache.org/jira/browse/FALCON-1146> and FALCON-1129 >> > <https://issues.apache.org/jira/browse/FALCON-1129> being merged, I >> believe >> > we can go ahead with this release as we have fixed a bunch of issues >>and >> > improved a lot on already available features. We would ideally want to >> call >> > a release in the next few days. >> > >> > Thoughts? >> > >> > Regards, >> > Suhas V >> > >> > -- >> > _____________________________________________________________ >> > The information contained in this communication is intended solely for >> the >> > use of the individual or entity to whom it is addressed and others >> > authorized to receive it. It may contain confidential or legally >> privileged >> > information. If you are not the intended recipient you are hereby >> notified >> > that any disclosure, copying, distribution or taking any action in >> reliance >> > on the contents of this information is strictly prohibited and may be >> > unlawful. If you have received this communication in error, please >>notify >> > us immediately by responding to this email and then delete it from >>your >> > system. The firm is neither liable for the proper and complete >> transmission >> > of the information contained in this communication nor for any delay >>in >> its >> > receipt. >> >>
