Thanks Josh for looking into this!

On Fri, Apr 5, 2019 at 12:52 PM Josh Elser <els...@apache.org> wrote:

> I can't do this right now, but I've asked Infra to give me the karma I
> need to remove this person.
>
> If a moderator of user@phoenix is watching this, they can use the tool
> on Whimsy[1] to remove this subscriber.
>
> - Josh
>
> [1] https://whimsy.apache.org/committers/moderationhelper.cgi
>
> On 4/5/19 3:47 PM, Josh Elser wrote:
> > Not just you. I have an email filter set up for folks like this :)
> >
> > A moderator should be able to force a removal. Trying it now to see if
> > I'm a moderator (I don't think I am, but might be able to add myself as
> > one).
> >
> > On 4/4/19 7:15 PM, William Shen wrote:
> >> I kept getting this every time I send to the users list. Can we force
> >> remove the subscriber (martin.pernollet-...@sgcib.com
> >> <mailto:martin.pernollet-...@sgcib.com>) ? Or is this only happening
> >> to me?
> >>
> >> Thanks
> >>
> >> - Will
> >>
> >> ---------- Forwarded message ---------
> >> From: <postmas...@sgcib.com <mailto:postmas...@sgcib.com>>
> >> Date: Thu, Apr 4, 2019 at 12:17 PM
> >> Subject: DELIVERY FAILURE: Error transferring to
> >> QCMBSJ601.HERMES.SI.SOCGEN; Maximum hop count exceeded. Message
> >> probably in a routing loop.
> >> To: <wills...@marinsoftware.com <mailto:wills...@marinsoftware.com>>
> >>
> >>
> >> Your message
> >>
> >>    Subject: Using Hint with PhoenixRDD
> >>
> >> was not delivered to:
> >>
> >> martin.pernollet-...@sgcib.com <mailto:martin.pernollet-...@sgcib.com>
> >>
> >> because:
> >>
> >>    Error transferring to QCMBSJ601.HERMES.SI.SOCGEN; Maximum hop count
> >> exceeded.  Message probably in a routing loop.
> >>
> >>
> >>
> >>
> >> ---------- Forwarded message ----------
> >> From: wills...@marinsoftware.com <mailto:wills...@marinsoftware.com>
> >> To: user@phoenix.apache.org <mailto:user@phoenix.apache.org>
> >> Cc:
> >> Bcc:
> >> Date: Thu, 4 Apr 2019 12:16:48 -0700
> >> Subject: Using Hint with PhoenixRDD
> >> Hi all,
> >>
> >> Do we have any way of passing in hints when querying Phoenix using
> >> PhoenixRDD in Spark? I reviewed the implementation of PhoenixRDD
> >> and PhoenixRecordWritable, but was not able to find an obvious way to
> >> do so. Is it supported?
> >>
> >> Thanks in advance!
> >>
> >> - Will
> >>
> >>
> *************************************************************************
> >> This message and any attachments (the “message”) are confidential,
> >> intended solely for the addressee(s), and may contain legally
> >> privileged information.
> >> Any unauthorised use or dissemination is prohibited.
> >> If you are not the intended recipient please notify us immediately by
> >> telephoning or e-mailing the sender.
> >> You should not copy this e-mail or use it for any purpose nor disclose
> >> its contents to any other person.
> >> E-mails are susceptible to alteration. Neither SOCIETE GENERALE nor
> >> any of its subsidiaries or affiliates shall be liable for the message
> >> if altered, changed or falsified.
> >> You agree to receive all communications by email or through dedicated
> >> websites.
> >> Please visit https://cib.societegenerale.com/en/market-regulation/ for
> >> important information on MiFID, SFTR and with respect to derivative
> >> products.
> >>
> >> Ce message et toutes les pieces jointes sont confidentiels et
> >> susceptibles de contenir des informations couvertes par le secret
> >> professionnel.
> >> Ce message est etabli a l’attention exclusive de ses destinataires.
> >> Toute utilisation ou diffusion non autorisee est interdite.
> >> Tout message electronique est susceptible d'alteration.
> >> SOCIETE GENERALE et ses filiales declinent toute responsabilite en cas
> >> d’alteration, modification ou falsification de ce message.
> >> Vous acceptez de recevoir nos communications par email ou via des
> >> sites web dedies.
> >> Veuillez consulter le site
> >> https://cib.societegenerale.com/en/market-regulation/ pour des
> >> informations importantes sur MiFID, SFTR et sur les produits derives.
> >>
> *************************************************************************
> >>
>

Reply via email to