[GEODE-230] Remove deprecated AttributesFactory

• Type: Sub-task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: docs
• Assignee: Unassigned
• Reporter: Darrel Schneider
• Created: 19/Aug/15 22:08
• Updated: 05/Nov/19 15:58

Description

Should AttributesFactory be remove since it has been deprecated since 6.5.
In that release we started telling customers to use Cache.createRegionFactory or ClientCache.createClientRegionFactory.

However here are a couple of reasons why we might not want to get rid of AttributesFactory:

• The corresponding PartitionAttributesFactory is not deprecated.
• We have had customers request that it not be deprecated so that they have a way to create a RegionAttributes on a client, send it to the server in a function, and have the function create a region using the un-deprecated Cache.createRegionFactory(RegionAttributes).

We could argue that Cache.createRegionFactory(RegionAttributes) is not deprecated so that given an existing region you could get its RegionAttributes by calling Region.getAttributes. But it seems reasonable to want to be able to create a RegionAttributes (and its nested PartitionAttributes) without needing to create the region in the same jvm that is creating the attributes.

Issue Links

• is a parent of: GEODE-7160 Remove Usages of AttributesFactory in geode-wan module
• is a parent of: GEODE-7161 Remove Usages of AttributesFactory in geode-redis module
• is a parent of: GEODE-7162 Remove Usages of AttributesFactory in geode-lucene module
• is a parent of: GEODE-7407 Remove Usages of AttributesFactory from geode-assembly module