Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@kafka.apache.org
Subject: Re: [DISCUSS]KIP-216: IQ should throw different exceptions for
 different errors
To: dev@kafka.apache.org
References: <CAMdhPwRt-F0V0dkWrOkfYa50+i3Cqiss_GvHYp7rytAbhKQw6A@mail.gmail.com>
 <CAHwHRrV504Pk=8v=M9cPH7wv_DZiUarsoBE9rVPoSD=47dqPDQ@mail.gmail.com>
 <49cf37a0-6e03-9571-7d0f-ec2edad572b0@confluent.io>
 <CAMdhPwRuvNXPhPpvu9DPRkv-muhDVoGdsA4V7u0utFVwr0Yp0g@mail.gmail.com>
From: "Matthias J. Sax" <matthias@confluent.io>
Organization: Confluent Inc
Message-ID: <dd0402aa-7950-e6ef-c988-ff7af616eb6b@confluent.io>
Date: Mon, 4 Dec 2017 16:05:55 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0)
 Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <CAMdhPwRuvNXPhPpvu9DPRkv-muhDVoGdsA4V7u0utFVwr0Yp0g@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature";
 boundary="rv2JKD2247MjuEaOHvKsPxi1DKliV55J5"
archived-at: Tue, 05 Dec 2017 00:06:03 -0000

--rv2JKD2247MjuEaOHvKsPxi1DKliV55J5
Content-Type: multipart/mixed; boundary="I19sjnP0bnRhHakSEDCcesh3hCILVNjPl";
 protected-headers="v1"
From: "Matthias J. Sax" <matthias@confluent.io>
To: dev@kafka.apache.org
Message-ID: <dd0402aa-7950-e6ef-c988-ff7af616eb6b@confluent.io>
Subject: Re: [DISCUSS]KIP-216: IQ should throw different exceptions for
 different errors
References: <CAMdhPwRt-F0V0dkWrOkfYa50+i3Cqiss_GvHYp7rytAbhKQw6A@mail.gmail.com>
 <CAHwHRrV504Pk=8v=M9cPH7wv_DZiUarsoBE9rVPoSD=47dqPDQ@mail.gmail.com>
 <49cf37a0-6e03-9571-7d0f-ec2edad572b0@confluent.io>
 <CAMdhPwRuvNXPhPpvu9DPRkv-muhDVoGdsA4V7u0utFVwr0Yp0g@mail.gmail.com>
In-Reply-To: <CAMdhPwRuvNXPhPpvu9DPRkv-muhDVoGdsA4V7u0utFVwr0Yp0g@mail.gmail.com>

--I19sjnP0bnRhHakSEDCcesh3hCILVNjPl
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Vito,

is there any update with regard to this KIP?


-Matthias

On 11/5/17 6:11 PM, vito jeng wrote:
> Thanks, Guozhang and Matthias. Your comments very useful for me.
>=20
> I'll update KIP and keep going on.
>=20
>=20
>=20
> ---
> Vito
>=20
> On Sun, Nov 5, 2017 at 12:30 AM, Matthias J. Sax <matthias@confluent.io=
>
> wrote:
>=20
>> Thanks for the KIP Vito!
>>
>> I agree with what Guozhang said. The original idea of the Jira was, to=

>> give different exceptions for different "recovery" strategies to the u=
ser.
>>
>> For example, if a store is currently recreated, a user just need to wa=
it
>> and can query the store later. On the other hand, if a store go migrat=
ed
>> to another instance, a user needs to rediscover the store instead of a=

>> "plain retry".
>>
>> Fatal errors might be a third category.
>>
>> Not sure if there is something else?
>>
>> Anyway, the KIP should contain a section that talks about this ideas a=
nd
>> reasoning.
>>
>>
>> -Matthias
>>
>>
>> On 11/3/17 11:26 PM, Guozhang Wang wrote:
>>> Thanks for writing up the KIP.
>>>
>>> Vito, Matthias: one thing that I wanted to figure out first is what
>>> categories of errors we want to notify the users, if we only wants to=

>>> distinguish fatal v.s. retriable then probably we should rename the
>>> proposed StateStoreMigratedException / StateStoreClosedException clas=
ses.
>>> And then from there we should list what are the possible internal
>>> exceptions ever thrown in those APIs in the call trace, and which
>>> exceptions should be wrapped to what others, and which ones should be=

>>> handled without re-throwing, and which ones should not be wrapped at =
all
>>> but directly thrown to user's face.
>>>
>>> Guozhang
>>>
>>>
>>> On Wed, Nov 1, 2017 at 11:09 PM, vito jeng <vito@is-land.com.tw> wrot=
e:
>>>
>>>> Hi,
>>>>
>>>> I'd like to start discuss KIP-216:
>>>>
>>>> https://cwiki.apache.org/confluence/display/KAFKA/KIP-
>>>> 216%3A+IQ+should+throw+different+exceptions+for+different+errors
>>>>
>>>> Please have a look.
>>>> Thanks!
>>>>
>>>> ---
>>>> Vito
>>>>
>>>
>>>
>>>
>>
>>
>=20


--I19sjnP0bnRhHakSEDCcesh3hCILVNjPl--

--rv2JKD2247MjuEaOHvKsPxi1DKliV55J5
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQJKBAEBCgA0FiEEFpAnjJ4fbvgzKNUmjQjbao0qTDYFAlol4uMWHG1hdHRoaWFz
QGNvbmZsdWVudC5pbwAKCRCNCNtqjSpMNieOD/9kToksiXrfgvIdPt+V8wIVaFL3
S5wBVCQnITLf1npbTjEq6mhqT8KunVSB45czVgIjyphwksiL8jyG958Cg62d/CWx
2U4FsKzdlTcO8cE62e+jxPxjxtkq6j2yOl22B/75v9iOeB7vEVUAI5PicUxL2gSc
zJHrGoZKlXF9LVDP3IPMGrujZn1xUaCBWAt/MBrT1B3NzohWlkqI0PvrFx5nkdMd
aRsTNQGr9JJAhe2Lk4AG8/kACdMDdfNw9o5SK26vKXm8Cz/vS2iaDtBn3tVQNNzh
A0bXySV/WOuiKpDBcXVchM3bpaB1nhCERrmv/PBbW974m1AIzC5sIN+b86tHI6+D
gl/vuJpximMdqyhGccvq2TPpti6aLNzCIlrl4vQERoTrVA3PmxaS2lIAOiBrOLCJ
rtY1CIgwFelnZbuG1SvglxBCMH6+X1qFAUBKeUlHBNIQNX9kkJFWENjnEyZZj53t
UZGvzP+MPlk1Mhsln0QUSUIWj+3ZrobeLhr7DnE9Qa47qMd20FcpQNHumneKdE5g
JnnhAdboe7ykLsgAfdXEivPIeRjLWibEjHKZ4rl5oeB9iaolxUKTUnJrNV8ScMI3
+l/0ntnet5Ek41k4VxG/5UdvoCla1YDUbNZLpMaGzOD5LM3U8SAo6d6drjdrMcF8
juwlGlR3UxZ1zFZAxQ==
=EKzk
-----END PGP SIGNATURE-----

--rv2JKD2247MjuEaOHvKsPxi1DKliV55J5--