-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 1/31/12 11:07 AM, Bram de Kruijff wrote: > Hi all, > > 2012/1/30 Marcel Offermans <[email protected]>: >> >> Some of us (including me) see a tenant as a logical entity that >> (possibly) spans multiple nodes. So one can say "Tenant X is >> deployed to nodes A, B, C". This allows applications (eg. Amdatu >> Big Data) to use the tenant.pid as an identifying key when >> creating a keyspace for Tenant X. This strategy is something we >> will discourage in 1.0 but that is besides the point for now. >> >> >> After a voice conference on Skype, Bram, Jan Willem and I just >> agreed that the tenant.pid is globally unique and only of >> interest to the Amdatu Platform and therefore cannot be used as >> an identifying key of a storage mechanism of an application (see >> the footnote below, or click >> http://www.amdatu.org/confluence/display/Amdatu/Amdatu+Core+Tenant+Design >> if you don't want to scroll down (the yellow box is our summary >> of this discussion)). Applications should use their own >> configuration to configure the name of (in this case) a >> keyspace. > > I'm just gonna go on record here. I send my reply on this thread > after that call and said: > >> On Jan 30, 2012, at 12:51 , Bram de Kruijff wrote: >> >> Although the discussion about the exact meaning op tenant.pid not >> yet finalized entirely it is very important to realize what >> interpretation is being used by whom when they reply. So I >> propose to explicitly mention whether you are talking about local >> or distributed events. > > IMHO it is not finalized and there more I think about it I tend to > disagree. I did agree to the fact stated by Jan-Willem that > applications should not use it as on identifier but rather prefer > their own configuration space. > > My concerns from two are two angels: > > 1) Why the tenant.pid should be globally unique? > > [snip] > > 2) Why the tenant.pid should NOT be globally unique? > > [snip] > > Bottomline, I do not believe we need a logical globally unique > identifier. At least you have not shown me a concrete use case for > it that can not be easily solved in another way. We may need a > (generated) system identifier but we should not hijack and remove > a higher level concept.
We do agree on these two things: 1) the tenant.pid should have *no* meaning whatsoever; 2) the tenant.pid should be specified upfront. If we would say, as developers of a platform, that the tenant.pid should be globally unique, it always gives you the advantage that this property will be unique in *any* form of application that is built on top of Amdatu. Additionally, making the tenant.pid really non-informative by making it, for example, a GUID ensures that this property really stays meaningless. If a user of the Amdatu platform decides otherwise, he should also deal with any problems that might occur. At least the platform shouldn't be bothered by that... Regards, - -- Met vriendelijke groeten | Kind regards Jan Willem Janssen | Software Architect +31 631 765 814 /My world is:/ Luminis Technologies B.V. IJsselburcht 3 6825 BS Arnhem +31 88 586 46 30 http://www.luminis-technologies.com http://www.luminis.eu KvK (CoC) 09 16 28 93 BTW (VAT) NL8169.78.566.B.01 -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJPJ8TmAAoJEKF/mP2eHDc46DgP/0633KAlHZF4lfsfxvpdS+zz XJ8LJM4l1xaiyYa6OREBQrNHPYyIWTQrHN13FbcELUqZvuFT5FaA941PcdsoO0Y9 4WDLfFY4yfDVITLuQWNE0Snv8s8vs/XZcRXrJBWQEsdjCs8mjuH5VLb0fxqMgNam xhL1VAvEWECNPSTqP8fjqdYdAjB9lppMQzMFOsTMunmoISRVTG0JQTOWVtkGF8cy Ct651SKj4f+gNDHMGFOJGHAppMmG+DlSicynRJH/V4tFqEKnJF61+7SO1izSHlaO f67BlHSbrd2LcbcIPhu/pybrwFC/X+yeVZzMpazgpyexvrcPPeaSt7p7bAS1adcs g+Lxu/ME9fFuemTb+DkCIYF6+ln/tw003uaxD9Gz/iKR6NCzCycyziyL61S3Sy41 lb9uDzFiiDXA8yDKDIlUI3zyYiL6yXTkYhivE2JmAhf8f1ThbyhZPfwC9aD4zt1R s2Xf5PTeuwCDofglkTQtLkxsLHm1Sw7uV3gpLMP0hGFEogyQ4vvr6mQac6oPJ+uP 2PIGvD2WHPEHRuC6UVSIh4HgoOMuHbvNEGnx6SSvBluhaCLJX/yv8uOL6g0Sn+AE tESItcRLchq/ZEUcqVasQXOyJbtb0z3xq2X4p/H4L95Y9pCCx/lETLBe1o0lbY03 D65rwN8StCEcFhpCJ21g =3UMY -----END PGP SIGNATURE----- _______________________________________________ Amdatu-developers mailing list [email protected] http://lists.amdatu.org/mailman/listinfo/amdatu-developers
