[
https://issues.apache.org/jira/browse/BLUR-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron McCurry closed BLUR-319.
------------------------------
Resolution: Fixed
Fix Version/s: 0.2.2
0.3.0
https://git-wip-us.apache.org/repos/asf?p=incubator-blur.git;a=commit;h=df2bb8904377dba56da4538ad63be26838b73170
https://git-wip-us.apache.org/repos/asf?p=incubator-blur.git;a=commit;h=640542f7f0d924a888f5ead72279b1086ebb0723
> Custom TypeDef's can get Blur into a state where one cannot make new tables.
> ----------------------------------------------------------------------------
>
> Key: BLUR-319
> URL: https://issues.apache.org/jira/browse/BLUR-319
> Project: Apache Blur
> Issue Type: Bug
> Components: Blur
> Affects Versions: 0.2.2
> Reporter: Garrett Barton
> Fix For: 0.3.0, 0.2.2
>
>
> So start with a cluster wide custom TypeDef in the blur-site and no tables in
> blur.
> Create a new table A with the custom TypeDef in the col defs. Works.
> Create a new table B with the cusom TypeDef defined again in the td, and a
> column trying to use it. Fails. (as it should)
> Create a new table C with the custom TypeDef used in the cols. Fails!?
> Any table created from now on will fail complaining about the custom type def
> already being registered.
> Aaron mumbled something about the BlurConfig in the TableContext not being
> immutable and it should be.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
